ASR9k Commands Reference
ASR9k Commands Reference
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of
the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com
go trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any
other company. (1721R)
© 2016 Cisco Systems, Inc. All rights reserved.
CONTENTS
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
iii
Contents
bfd (BGP) 44
bgp as-path-loopcheck 50
bgp attribute-download 51
bgp auto-policy-soft-reset disable 53
bgp bestpath as-path ignore 54
bgp bestpath compare-routerid 56
bgp bestpath cost-community ignore 58
bgp bestpath med always 59
bgp bestpath med confed 61
bgp bestpath med missing-as-worst 63
bgp bestpath origin-as allow invalid 65
bgp bestpath origin-as use validity 66
bgp bestpath aigp ignore 67
bgp bestpath as-path multipath-relax 68
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
iv
Contents
bgp redistribute-internal 98
bgp router-id 100
bgp scan-time 101
bgp update-delay 102
bgp write-limit 103
bmp-activate 105
bmp server 106
capability additional-paths receive 109
capability additional-paths send 111
capability orf prefix 113
capability suppress 4-byte-as 115
clear bgp 118
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
v
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
vi
Contents
next-hop-self 212
next-hop-unchanged 215
nexthop resolution prefix-length minimum 217
nexthop route-policy 218
nexthop trigger-delay 220
nsr (BGP) 222
nsr disable (BGP) 224
orf 226
password (BGP) 228
password (rpki-server) 230
password-disable 231
permanent-network 233
precedence 234
preference (rpki-server) 236
purge-time (rpki-server) 237
rd 238
receive-buffer-size 240
redistribute (BGP) 242
refresh-time (rpki-server) 246
response-time (rpki-server) 247
remote-as (BGP) 248
remove-private-as 251
retain local-label 254
retain route-target 255
route-policy (BGP) 257
route-reflector-client 259
optimal-route-reflection 261
router bgp 263
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
vii
Contents
send-extended-community-ebgp 274
session-group 276
session-open-mode 278
set flow-tag 280
show bgp 281
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
viii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
ix
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
x
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xi
Contents
CHAPTER 4 IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software 651
address-family (IS-IS) 654
address-family multicast topology (IS-IS) 656
adjacency-check disable 658
adjacency stagger 660
attached-bit receive ignore 662
attached-bit send 663
circuit-type 665
clear isis process 667
clear isis route 668
clear isis statistics 670
csnp-interval 672
default-information originate (IS-IS) 674
disable (IS-IS) 676
distance (IS-IS) 677
fast-reroute per-link (IS-IS) 679
fast-reroute per-prefix (IS-IS) 681
fast-reroute per-link priority-limit (IS-IS) 683
fast-reroute per-prefix load-sharing disable (IS-IS) 685
fast-reroute per-prefix tiebreaker (IS-IS) 686
hello-interval (IS-IS) 688
hello-multiplier 690
hello-padding 692
hello-password 694
hello-password keychain 696
hello-password accept 698
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xiii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xiv
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xv
Contents
log-neighbor-changes 888
log-neighbor-warnings 889
maximum-paths (EIGRP) 890
maximum-prefix (EIGRP) 891
metric (EIGRP) 893
metric maximum-hops 895
metric rib-scale 896
metric weights 897
neighbor (EIGRP) 900
neighbor maximum-prefix 902
next-hop-self disable 905
nsf disable (EIGRP) 906
passive-interface (EIGRP) 908
redistribute (EIGRP) 909
redistribute maximum-prefix 912
remote-neighbor (unicast) 914
route-policy (EIGRP) 916
router eigrp 917
router-id (EIGRP) 919
show eigrp accounting 920
show eigrp interfaces 922
show eigrp neighbors 926
show eigrp topology 929
show eigrp traffic 932
show protocols (EIGRP) 934
site-of-origin (EIGRP) 937
split-horizon disable (EIGRP) 939
stub (EIGRP) 940
summary-address (EIGRP) 942
timers active-time 944
timers nsf route-hold (EIGRP) 945
variance 946
vrf (EIGRP) 947
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xvi
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xvii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xviii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xix
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xx
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxi
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxiii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxiv
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxv
Contents
is-best-path 1573
is-backup-path 1574
is-multi-path 1575
local-preference 1576
med 1577
next-hop in 1578
orf prefix in 1580
origin is 1582
ospf-area 1584
ospf-area-set 1586
pass 1588
path-type is 1590
policy-global 1591
prefix-set 1593
prepend as-path 1596
protocol 1598
rd in 1600
rd-set 1601
replace as-path 1603
remove as-path private-as 1605
rib-has-route 1606
route-has-label 1608
route-policy (RPL) 1609
route-type is 1611
rpl editor 1613
rpl maximum 1614
rpl set-exit-as-abort 1616
set administrative-distance 1617
set aigp-metric 1618
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxvi
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxvii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxviii
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxix
Contents
storage-location 1813
track-external-routes 1815
track-summary-routes 1816
other-xtr-probe 1852
proxy-etr 1854
proxy-itr 1856
remote-rloc-probe 1858
router lisp 1859
show lisp decapsulation filter 1861
show lisp session 1862
show lisp site rloc members 1863
show lisp site 1864
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxx
Contents
solicit-map-request 1866
use-petr 1868
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxxi
Contents
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxxii
Preface
The Routing Command Reference for Cisco ASR 9000 Series Routers preface contains these sections:
• Changes to This Document , on page xxxiii
• Communications, Services, and Additional Information, on page xxxiii
Date Summary
November 2016 Initial release of this document.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxxiii
Preface
Communications, Services, and Additional Information
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
xxxiv
BGP Commands
This chapter describes the commands used to configure and monitor Border Gateway Protocol (BGP) on
Cisco ASR 9000 Series Aggregation Services Routers using Cisco IOS XR software. The commands in this
module configure IP Version 4 (IPv4), IP Version 6 (IPv6), Virtual Private Network Version 4 (VPNv4)
routing sessions.
For detailed information about BGP concepts, configuration tasks, and examples, see the Implementing BGP
chapter in the Routing Configuration Guide for Cisco ASR 9000 Series Routers.
Note Running the show bgp command immediately after configuring a large and complex route policy may result
in timeout of the system database shown through an error message (SYSDB-SYSDB-6-TIMEOUT_EDM). It is
recommended that the show command be run after the new route policy takes effect.
• accept-own, on page 7
• additional-paths install backup, on page 8
• additional-paths receive, on page 10
• additional-paths selection, on page 12
• additional-paths send, on page 14
• address-family (BGP), on page 16
• advertise, on page 20
• advertise best-external, on page 22
• advertise permanent-network, on page 24
• advertisement-interval, on page 25
• af-group, on page 27
• aggregate-address, on page 29
• aigp, on page 31
• aigp send-cost-community, on page 33
• allocate-label, on page 35
• allow vpn default-originate, on page 37
• allowas-in, on page 38
• as-format, on page 39
• as-override, on page 40
• as-path-loopcheck out disable, on page 42
• attribute-filter group, on page 43
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1
BGP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
2
BGP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
3
BGP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
4
BGP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
5
BGP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
6
BGP Commands
accept-own
accept-own
To enable handling of self-originated VPN routes containing ACCEPT_OWN community attribute, use the
accept-own command in neighbor VPNv4 or VPNv6 address family configuration mode. To disable this
functionality, either use the no form of this command or use the command with inheritance-disable keyword.
accept-own [inheritance-disable]
no accept-own
Syntax Description inheritance-disable Disables handling of self-originated VPN routes containing ACCEPT_OWN
community attribute and prevents inheritance of Accept Own from a parent
configuration.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#neighbor 10.2.3.4
RP/0/RSP0/CPU0:router(config-bgp-nbr)#address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)#accept-own
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
7
BGP Commands
additional-paths install backup
Note Effective with Release 4.0.0, the additional-paths install backup command was deprecated and replaced by
the additional-paths selection command. See the additional-paths selection, on page 12 command for more
information.
To install a backup path into the forwarding table and provide prefix independent convergence (PIC) in case
of a PE-CE link failure, use the additional-paths install backup command in an appropriate address family
configuration mode. To prevent installing the backup path, use the no form of this command. To disable
prefix independent convergence, use the disable keyword.
Syntax Description disable Disables installing backup path into the forwarding table.
Release 4.0.0 This command was deprecated replaced by the additional-paths selection command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to enable installing a backup path into the forwarding table in
VPNv4 address family mode:
RP/0/RSP0/CPU0:router#configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
8
BGP Commands
additional-paths install backup
retain local-label, on page 254 Retains the local label until the network is converged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
9
BGP Commands
additional-paths receive
additional-paths receive
To configure receive capability of multiple paths for a prefix to the capable peers, use the additional-paths
receive command in address-family configuration mode. To disable receive capability, use the no form of
this command. To disable add-path receive capability for all neighbors belonging to a particular VRF
address-family, use the disable option.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the additional-paths receive command to allow add-path receive capability to be negotiated for a
specified address family. When the additional-paths receive command is configured, the receive capability
is automatically enabled for all internal BGP neighbors for a specified address family. When this command
is either not configured or explicitly disabled, none of the neighbors are allowed to negotiate receive capability
for the address family.
After enabling the receive capability, the session needs to be reset for the configuration to take into effect.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
10
BGP Commands
additional-paths receive
This example shows how to enable additional paths receive capability under VPNv4 unicast address
family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:routerconfig)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# additional-paths receive
This example shows how to disable additional paths receive capability for all neighbors belonging
to a particular VRF address-family (vrf1):
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config-bgp)#vrf vrf1
RP/0/RSP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)#additional-paths receive disable
capability additional-paths receive, on page 109 Advertises additional paths receive capability.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
11
BGP Commands
additional-paths selection
additional-paths selection
To configure additional paths selection mode for a prefix, use the additional-paths selection command in
address-family configuration mode. To disable the additional-paths selection mode for a prefix, use the no
form of this command. To disable the additional-paths selection mode for a particular VRF address-family,
use the disable option.
Syntax Description route-policy route-policy-name Specifies the name of a route policy used for additional paths selection.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
To configure additional paths selection mode for some or all prefixes, use the additional-paths selection
command by specifying a route-policy.
Use the additional-path selection command with an appropriate route-policy to calculate backup paths and
to enable Prefix Independent Convergence (PIC) functionality. Refer BGP Prefix Independent Convergence
Unipath Primary/Backup section in Routing Configuration Guide for Cisco ASR 9000 Series Routers for
details on the PIC functionality.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
12
BGP Commands
additional-paths selection
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# additional-paths selection route-policy ap1
This example shows how to disable add-path selection for a particular VRF address-family (vrf1):
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config-bgp)#vrf vrf1
RP/0/RSP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)#additional-paths selection disable
This example shows how to enable add-path selection for a particular VRF address-family (vrf2):
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config-bgp)#vrf vrf2
RP/0/RSP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)#additional-paths selection route-policy ap2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
13
BGP Commands
additional-paths send
additional-paths send
To configure send capability of multiple paths for a prefix to the capable peers, use the additional-paths send
command in address-family configuration mode. To disable the send capability, use the no form of this
command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the additional-paths send command to allow add-path send capability to be negotiated for a specified
address family. When the additional-paths send command is configured, the send capability is automatically
enabled for all internal BGP neighbors for the specified address family. When the command is either not
configured or explicitly disabled, none of the neighbors are allowed to negotiate send capability for the address
family.
After enabling the send capability, the session needs to be reset for the configuration to take into effect.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
14
BGP Commands
additional-paths send
This example shows how to enable additional paths send capability under VPNv4 4 unicast address
family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:routerconfig)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# additional-paths send
This example shows how to enable add-path selection for a particular VRF address-family (vrf1):
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config-bgp)#vrf vrf1
RP/0/RSP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)#additional-paths send disable
capability additional-paths receive, on page 109 Advertises additional paths receive capability.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
15
BGP Commands
address-family (BGP)
address-family (BGP)
To enter various address family configuration modes while configuring Border Gateway Protocol (BGP), use
the address-family command in an appropriate configuration mode. To disable support for an address family,
use the no form of this command.
address-family {ipv4 {labeled-unicast | flowspec | multicast | mvpn | unicast} | ipv6 {flowspec | mvpn
| unicast} | l2vpn vpls-vpws | vpnv4 {flowspec | multicast | unicast} | vpnv6 {unicast | flowspec} | link-state
link-state}
no address-family
Syntax Description ipv4 unicast Specifies IP Version 4 (IPv4) unicast address prefixes.
ipv4 labeled-unicast Specifies IPv4 labeled-unicast address prefixes. This option is available in IPv4
neighbor configuration mode and VRF neighbor configuration mode.
vpnv4 unicast Specifies VPN Version 4 (VPNv4) unicast address prefixes. This option is not available
in VRF or VRF neighbor configuration mode.
Command Default An address family must be explicitly configured in the router configuration mode for the address family to
be active in BGP. Similarly, an address family must be configured under the neighbor for the BGP session to
be established for that address family. An address family must be configured in router configuration mode
before it can be configured under a neighbor.
Neighbor configuration
Flowspec configuration
VRF configuration
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
16
BGP Commands
address-family (BGP)
Release 4.2.0 The mvpn SAFI was introduced under IPv4 and IPv6.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the address-family command to enter various address family configuration modes while configuring
BGP routing sessions. When you enter the address-family command from router configuration mode, you
enable the address family and enter global address family configuration mode.
The IPv4 unicast address family must be configured in router configuration mode before configuring the IPv4
labeled-unicast address family for a neighbor in neighbor configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
17
BGP Commands
address-family (BGP)
When you enter the address-family command from neighbor configuration mode, you activate the address
family on the neighbor and enter neighbor address family configuration mode. IPv4 neighbor sessions support
IPv4 unicast, , labeled-unicast, and VPNv4 unicast address families. IPv6 neighbor sessions support IPv6
unicast address families.
Outbound Route Filter (ORF) capability is not supported with address-family l2vpn vpls-vpws
bgp read,
write
Examples The following example shows how to place the router in global address family configuration mode
for the IPv4 address family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#
The following example shows how to activate IPv4 multicast for neighbor 10.0.0.1 and place the
router in neighbor address family configuration mode for the IPv4 multicast address family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router# router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 multicast
RP/0/RSP0/CPU0:router(config-bgp-af)# exit
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.0.0.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# remote-as 1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)#
The following example shows how to place the router in global address family configuration mode
for the IPv4 tunnel address family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 12
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 tunnel
RP/0/RSP0/CPU0:router(config-bgp-af)#
The following example shows how to place the router in global address family link-state configuration
mode:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
18
BGP Commands
address-family (BGP)
The following example shows how to exchange link-state information with a BGP neighbor:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.0.0.2
RP/0/RSP0/CPU0:router(config-bgp-nbr)# remote-as 1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family link-state link-state
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)#
The following example shows how to place the router in flowspec sub-address family configuration
mode for the IPv4 address family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 flowspec
RP/0/RSP0/CPU0:router(config-bgp-af)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
19
BGP Commands
advertise
advertise
To configure advertisement of local or re-originated VPNv4 or VPNv6 unicast routes or disable advertisement
of L2VPN prefixes from a BGP router to its configured BGP neighbor, use the advertise command in BGP
neighbor address family configuration mode. To undo this command configuration, use the no form of this
command.
advertise {{vpnv4 | vpnv6} unicast {re-originated | local stitching-rt} | l2vpn evpn disable}
no advertise {{vpnv4 | vpnv6} unicast {re-originated | local stitching-rt} | l2vpn evpn disable}
local stitching-rt Specifies advertisement of local VPNv4 or VPNv6 unicast routes with stitching route
target identifier.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
The following example shows how to configure a BGP router to advertise local VPNv4 unicast routes
assigned with stitching route target identifier to the specified BGP neighbor 1.1.1.1.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
20
BGP Commands
advertise
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 1.1.1.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family l2vpn evpn
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# advertise vpnv4 unicast re-originated stitching-rt
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
21
BGP Commands
advertise best-external
advertise best-external
To advertise the best–external path to the iBGP and route-reflector peers, when a locally selected bestpath is
from an internal peer, use the advertise best-external command in an appropriate address family configuration
mode. To prevent advertising the best–external path, use the no form of this command. To disable advertising
the best–external path, use the disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Unlabelled best-external is not supported as it may create routing loop.
bgp read,
write
Examples The following example shows how to enable advertising the best–external path VPNv4 unicast
address family mode:
RP/0/RSP0/CPU0:router# configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
22
BGP Commands
advertise best-external
additional-paths install backup, on page Installs a backup path into the forwarding table and provides
8 prefix independent convergence (PIC) in case of a PE-CE link
failure.
retain local-label, on page 254 Retains the local label until the network is converged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
23
BGP Commands
advertise permanent-network
advertise permanent-network
To identify the peers to whom the permanent paths must be advertised, use the advertise permanent-network
command in the neighbor address family configuration mode. To stop advertising the permanent p, use the
no form of this command. The permanent paths will always be advertised to peers having advertise
permanent-network configuration, even if a different best-path is available. The permanent path is not advertised
to peers that are not configured to receive permanent path.
The permanent path supports only prefixes in IPv4 unicast and IPv6 unicast address-families under the default
Virtual Routing and Forwarding (VRF).
advertise permanent-network
no advertise permanent-network
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.1.1.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# remote-as 4713
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# advertise permanent-network
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
24
BGP Commands
advertisement-interval
advertisement-interval
To set the minimum interval between the sending of Border Gateway Protocol (BGP) routing updates, use
the advertisement-interval command in an appropriate configuration mode. To remove the
advertisement-interval command from the configuration file and restore the system to its default interval
values, use the no form of this command.
advertisement-interval seconds
no advertisement-interval [seconds]
Syntax Description seconds Minimum interval between sending BGP routing updates (in seconds). Range is 0 to 600.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If this command configures a neighbor group or session group, all neighbors using the group inherit the
configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Examples The following example shows how to set the minimum time between sending BGP routing updates
to 10 seconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
25
BGP Commands
advertisement-interval
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
26
BGP Commands
af-group
af-group
To create an address family group for Border Gateway Protocol (BGP) neighbors and enter address family
group configuration mode, use the af-group command in router configuration mode. To remove an address
family group, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the af-group command to group address family-specific neighbor commands within an IPv4 or IPv6
address family. Neighbors that have address family configuration are able to use the address family group.
Further, neighbors inherit the configuration parameters of the entire address family group.
You cannot define two address family groups with the same name in different address families.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
27
BGP Commands
af-group
Examples The following example shows how to create address family group group1 and enter address family
group configuration mode for IPv4 unicast. Group1 contains the next-hop-self feature, which is
inherited by neighbors that use address family group1.
neighbor (BGP), on page 203 Enters neighbor configuration mode for configuring BGP routing sessions.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
use, on page 524 Inherits configuration from a neighbor group, session group, or address family
group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
28
BGP Commands
aggregate-address
aggregate-address
To create an aggregate entry in a Border Gateway Protocol (BGP) routing table, use the aggregate-address
command in an appropriate configuration mode. To remove the aggregate-address command from the
configuration file and restore the system to its default condition, use the no form of this command.
route-policy route-policy-name (Optional) Specifies the name of a route policy used to set the attributes
of the aggregate route.
Command Default When you do not specify this command, no aggregate entry is created in the BGP routing table.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You can implement aggregate routing in BGP either by redistributing an aggregate route into BGP using the
network command or the aggregate-address command.
Use the aggregate-address command without optional arguments to create an aggregate entry in the BGP
routing table if any more-specific BGP routes are available that fall in the specified range. The aggregate route
is advertised as coming from your autonomous system and has the atomic aggregate attribute set to show that
information might be missing. (By default, the atomic aggregate attribute is set unless you specify the as-set
keyword.)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
29
BGP Commands
aggregate-address
Use of the as-set keyword creates an aggregate entry using the same rules that the command follows without
this keyword. However, the advertised path for this route is an AS_SET, a set of all autonomous systems
contained in all paths that are being summarized.
Do not use this form of the aggregate-address command when aggregating many paths because this route
must be continually withdrawn and updated as autonomous system path reachability information for the
summarized routes changes.
Use the as-confed-set keyword to create an AS_CONFED_SET in the autonomous system path of the
aggregate from any confederation segments in the paths being summarized. This keyword takes effect only
if the as-set keyword is also specified.
Use of the summary-only keyword creates an aggregate entry (for example, 10.0.0.0/8) but suppresses
advertisements of more-specific routes to all neighbors. If you want to suppress only advertisements to certain
neighbors, use the route-policy (BGP) command in neighbor address family configuration mode with
caution. If a more-specific route leaks out, all BGP speakers (the local router) prefer that route over the
less-specific aggregate you generate (using longest-match routing).
Use the route-policy keyword to specify a routing policy for the aggregate entry. The route-policy keyword
is used to select which more-specific information to base the aggregate entry on and which more-specific
information to suppress. You can also use the keyword to modify the attributes of the aggregate entry.
bgp read,
write
Examples The following example shows how to create an aggregate address. The path advertised for this route
is an autonomous system set consisting of all elements contained in all paths that are being
summarized.
network (BGP), on page 208 Specifies the list of networks for the BGP routing process.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor
route-policy (RPL) Defines a route policy and enters route-policy configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
30
BGP Commands
aigp
aigp
To enable sending and receiving of accumulated interior gateway protocol (AiGP) attribute per eBGP neighbor,
use the aigpcommand in appropriate configuration mode. To disable this functionality, either use the disable
keyword or use the no form of this command.
aigp [disable]
no aigp
Command Default Send or recive of AiGP attribute is disabled for eBGP neighbors
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples The following example shows how to enable AiGP send and receive capability under neighbor
address family (IPv4 unicast):
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.2.3.4
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
31
BGP Commands
aigp
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# aigp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
32
BGP Commands
aigp send-cost-community
aigp send-cost-community
To send Accumulated Interior Gateway Protocol (AiGP) value in cost community, use the aigp
send-cost-community command in appropriate configuration mode. To disable sending AiGP value in cost
community, either use the no form of this command or the disable keyword.
Syntax Description cost-comm-id Specifies the Cost community ID. The range is
0 to 255.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cost community point of insertion can be configured either to be pre-bestpath or after igp cost. The transitive
keyword is not required for iBGP sessions. However, the transitive keyword is required for eBGP sessions
to convert AiGP metric into cost-community and advertise to the eBGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
33
BGP Commands
aigp send-cost-community
Examples The following example shows how to enable sending AiGP value in cost community ID 254 under
neighbor address family (IPv4 unicast):
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.2.3.4
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# aigp send-cost-community 254
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
34
BGP Commands
allocate-label
allocate-label
To allocate Multiprotocol Label Switching (MPLS) labels for specific IPv4 unicast or IPv6 unicast or VPN
routing and forwarding (VRF) IPv4 unicast routes so that the BGP router can send labels with BGP routes to
a neighboring router configured for labeledunicast sessions, use the allocate-label command in the appropriate
configuration mode. To restore the system to its default condition, use the no form of this command.
route-policy route-policy-name Uses a route policy to select prefixes for label allocation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the allocate-label command with a route policy to trigger BGP to allocate labels for all or a filtered set
of global IPv4 routes (as dictated by the route policy). The command enables autonomous system border
routers (ASBRs) that have labeled IPv4 unicast sessions to exchange Multiprotocol Label Switching (MPLS)
labels with the IPv4 routes to the other autonomous system (AS) in Layer 3 Virtual Private Network (L3VPN)
inter-AS deployments.
Note The allocate-label all command is functionally equivalent to the allocate-label route-policy
route-policy-name command when the route policy is a pass-all policy.
See MPLS Configuration Guide for Cisco ASR 9000 Series Routersfor information on using the allocate-label
command for L3VPN inter-AS deployments and carrier-supporting-carrier IPv4 BGP label distribution.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
35
BGP Commands
allocate-label
Examples The following example shows how to enable allocating labels for IPv4 routes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
36
BGP Commands
allow vpn default-originate
Command Default The router cannot advertise a default route to its BGP VPN neighbors.
Usage Guidelines This command only enables the router to advertise itself as the next-hop router for a default route to its BGP
VPN neighbors. To actually forward the default route to a BGP VPN neighbor, you need to run the
default-originate command under the BGP neighbor Address-Family configuration mode.
Example
The following example configuration shows how to enable a BGP router to advertise a default route
to its BGP VPN neighbors.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# vrf foo
RP/0/RSP0/CPU0:router(config-bgp-vrf)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-vrf-af)# allow vpn default-originate
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
37
BGP Commands
allowas-in
allowas-in
To allow an AS path with the provider edge (PE) autonomous system number (ASN) a specified number of
times, use the allowas-in command in an appropriate configuration mode. To restore the system to its default
condition, use the no form of this command.
allowas-in [as-occurrence-number]
no allowas-in [as-occurrence-number]
Syntax Description as-occurrence-number (Optional) Number of times a PE ASN is allowed. Range is 1 to 10.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Hub and spoke VPN networks require looping back of routing information to the hub PE through the hub
customer edge (CE). See MPLS Configuration Guide for Cisco ASR 9000 Series Routers for information on
hub and spoke VPN networks. This looping back, in addition to the presence of the PE ASN, causes the
looped-back information to be dropped by the hub PE.
The allowas-in command prevents the looped-back information from being dropped by replacing the neighbor
autonomous system number (ASN) with the PE ASN in the AS path. This allows the VPN customer to see a
specified number of occurrences of the PE ASN in the AS path.
bgp read,
write
Examples The following example shows how to allow five occurrences of the PE ASN:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
38
BGP Commands
as-format
as-format
To configure the router's Autonomous system number (ASN) notation to asdot format, use the as-format
command in global configuration mode. To restore the system to its default condition, use the no form of
this command.
as-format asdot
no
Syntax Description asdot Specifies the Autonomous system number (ASN) notation to asdot format.
Command Default The default value, if the as-format command is not configured, is asplain.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to configure the ASN notation to the asdot format:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
39
BGP Commands
as-override
as-override
To configure a provider edge (PE) router to override the autonomous system number (ASN) of a site with the
ASN of a provider, use the as-override command which works for both VRF and non-VRF neighbor address
family configuration mode. To restore the system to its default condition, use the no form of this command.
as-override [inheritance-disable]
no as-override [inheritance-disable]
Syntax Description inheritance-disable (Optional) Prevents the as-override command from being inherited from a parent
group.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-override command in conjunction with the site-of-origin (SoO) feature, identifying the site where
a route originated, and preventing routing loops between routers within a VPN.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
40
BGP Commands
as-override
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
41
BGP Commands
as-path-loopcheck out disable
Command Default AS PATH loop checking for outbound updates is enabled if there is only one neighbor and disabled if there
are multiple neighbors in the update group.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Configure the as-path-loopcheck out disable command to disable the default behavior of PE router not
announcing BGP routes to the CE router if the routes contain an AS number matching the AS number of the
receiving CE router.
This example shows how to configure as-path-loopcheck out disable under IPv6 unicast address
family:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#as-path-loopcheck out disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
42
BGP Commands
attribute-filter group
attribute-filter group
To configure attribute-filter group command mode, use the attribute-filter group command in an appropriate
configuration mode. To disable attribute-filter group command mode, use the no form of this command.
Neighbor configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the attribute-filter group command in neighbor configuration mode to configure a specific attribute
filter group for a BGP neighbor.
This example shows how to configure the attribute-filter group command mode:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#attribute-filter group ag_discard_med
RP/0/RSP0/CPU0:router(config-bgp-attrfg)#
This example shows how to configure the attribute filter group for a BGP neighbor:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#neighbor 10.0.1.101
RP/0/RSP0/CPU0:router(config-bgp-nbr)#remote-as 6461
RP/0/RSP0/CPU0:router(config-bgp-nbr)#update in filtering
RP/0/RSP0/CPU0:router(config-nbr-upd-filter)#attribute-filter group ag_discard_med
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
43
BGP Commands
bfd (BGP)
bfd (BGP)
To specify a bidirectional forwarding detection (BFD) multiplier and minimum-interval arguments per
neighbor, use the bfd command in neighbor address family independent configuration mode. To return to the
system defaults, use the no form of this command.
Previous to this enhancement, BFD could be configured only in global scope in BGP. This change makes
available two new command-line arguments under neighbor address family independent configuration:
Syntax Description multiplier value Specifies the BFD session's multiplier value for the neighbor.
minimum-interval value Specifies the BFD session's minimum-interval value for the neighbor.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If the minimum interval is changed using the bfd minimum-intervalcommand, the new parameter updates
all affected BFD sessions under the command mode in which the minimum interval was changed.
If the multiplier is changed using the bfd multiplier command, the new parameter is used to update only the
BFD sessions associated with the affected neighbor gets affected.
The assumption is that when BFD fast-detect is enabled under neighbor address family independent
configuration, the values for the multiplier and minimum-interval values are always derived from the
per-neighbor values if they are configured; otherwise, they are to be taken from the global BGP configuration
mode. In the event that this has not been explicitly stated, then these values are taken to be the default values.
Also, the bfd arguments can be configured under neighbor-group and session-group and the inheritance
adheres to the standard way of BGP configuration inheritance.
Accordingly, there are four cases in which bfd-fast detect is enabled.
This is shown in table below where the BFD value is either multiplier or minimum-interval. Local indicates
per NBR value, global is the BGP global value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
44
BGP Commands
bfd (BGP)
Examples The following example shows how to specify the BFD session's multiplier value for the neighbor:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 65000
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)#neighbor 3.3.3.2
RP/0/RSP0/CPU0:router(config-bgp-nbr)# bfd minimum-interval 311
RP/0/RSP0/CPU0:router(config-bgp-nbr)# bfd multiplier 7
RP/0/RSP0/CPU0:router(config-bgp-nbr)# neighbor 5.5.5.2
RP/0/RSP0/CPU0:router(config-bgp-nbr)# bfd minimum-interval 318
RP/0/RSP0/CPU0:router(config-bgp-nbr)# bfd multiplier 4
RP/0/RSP0/CPU0:router(config-bgp-nbr)# vrf one
RP/0/RSP0/CPU0:router(config-bgp-vrf)# neighbor 3.12.1.2
RP/0/RSP0/CPU0:router(config-bgp-vrf-nbr)# bfd minimum-interval 119
RP/0/RSP0/CPU0:router(config-bgp-vrf-nbr)# bfd multiplier 10
RP/0/RSP0/CPU0:router(config-bgp-vrf-nbr)# commit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
45
BGP Commands
bfd (BGP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
46
BGP Commands
bfd (BGP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
47
BGP Commands
bfd (BGP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
48
BGP Commands
bfd (BGP)
reset)
Time since last notification sent to neighbor: 00:07:04
Error Code: administrative reset
Notification data sent:
None
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
49
BGP Commands
bgp as-path-loopcheck
bgp as-path-loopcheck
To enable loop checking in the autonomous system path of the prefixes advertised by internal Border Gateway
Protocol (iBGP) peers, use the bgp as-path-loopcheck command in an appropriate configuration mode. To
restore the system to its default condition, use the no form of this command.
bgp as-path-loopcheck
no bgp as-path-loopcheck
Command Default When you do not specify this command, loop checking is performed only for external peers.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to configure an autonomous system path for loop checking iBGP
peers:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
50
BGP Commands
bgp attribute-download
bgp attribute-download
To enable Border Gateway Protocol (BGP) attribute download, use the bgp attribute-download command
in an appropriate configuration mode. To disable BGP attribute download, use the no form of this command.
bgp attribute-download
no bgp attribute-download
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When BGP attribute download is enabled using the bgp attribute-download command, BGP reinstalls all
routes whose attributes are not currently in the RIB. Likewise, if the user disables BGP attribute download
using the no form of the command, BGP reinstalls previously installed routes with a null key, and removes
the attributes from the RIB.
Use the bgp attribute-download command to enable the Netflow BGP data export function. When attribute
download is enabled, BGP downloads the attribute information for prefixes (community, extended community,
and as-path) to the Routing Information Base (RIB) and Forwarding Information Base (FIB). This enables
FIB to associate the prefixes with attributes and send the Netflow statistics along with the associated attributes.
bgp read,
write
Examples The following example shows the BGP routes before and after BGP attribute download is enabled
and shows how to enable BGP attribute download on BGP router 50:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
51
BGP Commands
bgp attribute-download
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
52
BGP Commands
bgp auto-policy-soft-reset disable
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note If the inbound policy changes, it is not always possible to perform a soft reset. This is the case if the neighbor
does not support route refresh and soft-reconfiguration inbound is not configured for the neighbor. In such
instances, a message is logged in the system log indicating that a manual hard reset is needed.
bgp read,
write
Examples The following example shows how to disable an automatic soft reset of BGP peers when their
configured route policy is modified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
53
BGP Commands
bgp bestpath as-path ignore
Command Default The autonomous system path length is used (not ignored) when a best path is selected.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp bestpath as-path ignore command to ignore the length of autonomous system paths when the
software selects a preferred path. When the best path is selected, if this command is specified, all steps are
performed as usual except comparison of the autonomous path length between candidate paths.
bgp read,
write
Examples The following example shows how to configure the software to ignore the autonomous system length
when performing best-path selection:
bgp bestpath compare-routerid, on page Compares identical routes received from eBGP peers during the
56 best-path selection process and selects the route with the lowest
router ID.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
54
BGP Commands
bgp bestpath as-path ignore
Command Description
bgp bestpath med always, on page 59 Allows the comparison of the Multi Exit Discriminator (MED)
for paths from neighbors in different autonomous systems.
bgp bestpath med confed, on page 61 Enables MED comparison among paths learned from
confederation peers.
bgp bestpath med missing-as-worst, on Enables the software to consider a missing MED attribute in a
page 63 path as having a value of infinity.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
55
BGP Commands
bgp bestpath compare-routerid
Command Default The software does not select a new best path if it is the same as the current best path (according to the BGP
selection algorithm) except for the router ID.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp bestpath compare-routerid command to affect how the software selects the best path, in the
case where there are two paths of equal cost according to the BGP selection algorithm. This command is used
to force the software to select the path with the lower router ID as the best path. If this command is not used,
the software continues to use whichever path is currently the best path, regardless of which has the lower
router ID.
bgp read,
write
Examples The following example shows how to configure the BGP speaker in autonomous system 500 to
compare the router IDs of similar paths:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
56
BGP Commands
bgp bestpath compare-routerid
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
57
BGP Commands
bgp bestpath cost-community ignore
Command Default The behavior of this command is enabled by default until the cost community attribute is manually configured.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp bestpath cost-community ignore command to disable the evaluation of the cost community
attribute to help isolate problems and troubleshoot issues that relate to BGP path selection. This command
can also be used to delay the activation of cost community attribute evaluation so that cost community filtering
can be deployed in a large network at the same time.
bgp read,
write
Examples The following example shows how to configure a router to not evaluate the cost community attribute
during the best-path selection process:
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
58
BGP Commands
bgp bestpath med always
Command Default The software does not compare MEDs for paths from neighbors in different autonomous systems.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The MED is one of the parameters that is considered by the software when selecting the best path among
many alternative paths. The software chooses the path with the lowest MED.
By default, during the best-path selection process, the software makes a MED comparison only among paths
from the same autonomous system. This command changes the default behavior of the software by allowing
comparison of MEDs among paths regardless of the autonomous system from which the paths are received.
When the bgp bestpath med always command is not enabled and distributed BGP is configured, speakers
calculate partial best paths only (executes the best-path steps up to the MED comparison) and send them to
BGP Routing Information Base (bRIB). bRIB calculates the final best path (executes all the steps in the
best-path calculation). When the bgp bestpath med always command is enabled and distributed BGP is
configured, speakers can compare the MED across all ASs, allowing the speaker to calculate a single best
path to send it to bRIB. bRIB is the ultimate process that calculates the final best path, but when the bgp
bestpath med always command is enabled, the speakers send a single best path instead of potentially sending
multiple, partial best paths
bgp read,
write
Examples The following example shows how to configure the Border Gateway Protocol (BGP) speaker in
autonomous system 100 to compare MEDs among alternative paths, regardless of the autonomous
system from which the paths are received:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
59
BGP Commands
bgp bestpath med always
bgp bestpath med confed, on page 61 Enables MED comparison among paths learned from
confederation peers.
bgp bestpath med missing-as-worst, on Specifies that the software consider a missing MED attribute in
page 63 a path as having a value of infinity, making the path without a
MED value the least desirable path.
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
60
BGP Commands
bgp bestpath med confed
Command Default The software does not compare the MED of paths containing only confederation segments, or paths containing
confederation segments followed by an AS_SET, with the MED of any other paths.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, the MED of the following paths is not compared with the MED of any other path:
• Paths with an empty autonomous system path
• Paths beginning with an AS_SET
• Paths containing only confederation segments
• Paths containing confederation segments followed by an AS_SET
Use the bgp bestpath med confed command to affect how the following types of paths are treated in the
BGP best-path algorithm:
• Paths containing only confederation segments
• Paths containing confederation segments followed by an AS_SET
The MED for paths that start with an AS_SEQUENCE or that start with confederation segments followed by
an AS_SEQUENCE only is compared with the MED of other paths that share the same first autonomous
system number in the autonomous system sequence (the neighbor autonomous system number). This behavior
is not affected by the bgp bestpath med confed command.
As an example, suppose that autonomous systems 65000, 65001, 65002, and 65004 are part of a confederation,
but autonomous system 1 is not. Suppose that for a particular route, the following paths exist:
• Path 1: 65000 65004, med = 2, IGP metric = 20
• Path 2: 65001 65004, med = 3, IGP metric = 10
• Path 3: 65002 1, med = 1, IGP metric = 30
If the bgp bestpath med confed command is enabled, the software selects path 1 as the best path because
it:
• Has a lower MED than path 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
61
BGP Commands
bgp bestpath med confed
bgp read,
write
Examples The following command shows how to enable Border Gateway Protocol (BGP) software to compare
MED values for paths learned from confederation peers:
bgp bestpath med always, on page 59 Enables MED comparison among paths from neighbors in different
autonomous systems.
bgp bestpath med missing-as-worst, on Specifies that the software consider a missing MED attribute in
page 63 a path as having a value of infinity, making the path without a
MED value the least desirable path.
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
62
BGP Commands
bgp bestpath med missing-as-worst
Command Default The software assigns a value of 0 to the missing MED, causing the path with the missing MED attribute to
be considered as the best possible MED.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to direct the Border Gateway Protocol (BGP) software to consider
a missing MED attribute in a path as having a value of infinity, making this path the least desirable
path:
bgp bestpath med always, on page 59 Enables MED comparison among paths from neighbors in different
autonomous systems.
bgp bestpath med confed, on page 61 Enables MED comparison among paths learned from confederation
peers.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
63
BGP Commands
bgp bestpath med missing-as-worst
Command Description
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
64
BGP Commands
bgp bestpath origin-as allow invalid
Command Default By default, prefixes marked with an 'invalid' origin-as are not considered for BGP best path computation when
the router is performing origin-as validation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Configuring the bgp bestpath origin-as allow invalid command allows paths marked with an 'invalid' origin-as
to be considered for best path computation. This can be limited to an address family by configuring it at the
address-family submode.
This configuration takes effect only when the bgp bestpath origin-as use validity configuration is enabled.
Examples The following example shows how to permit all invalid paths to be considered for BGP best-path
selection:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 50000
RP/0/RSP0/CPU0:router(config-bgp)#bgp bestpath origin-as allow invalid
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
65
BGP Commands
bgp bestpath origin-as use validity
Command Default By default, the best path computation does not take RPKI states into account.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
There are three RPKI states - valid, invalid, and not found. When the bgp bestpath origin-as use validity
command is configured, only paths marked with 'valid' or 'not found' are considered as best path candidates.
When the bgp bestpath origin-as allow invalid command is configured, paths marked as 'invalid' are also
considered but preference is given to routes marked 'valid' over those marked 'invalid'.
Examples The following example shows how to enable the validity states of BGP paths to affect the path's
preference when performing best-path selection:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 50000
RP/0/RSP0/CPU0:router(config-bgp)#bgp bestpath origin-as use validity
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
66
BGP Commands
bgp bestpath aigp ignore
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, BGP always prefers a path with the AIGP metric. When there are two paths, one with the AIGP
metric and the other without, then executing the bgp bestpath aigp ignore command results in BGP performing
best path computation as if neither paths has the AIGP metric.
bgp read,
write
Examples The following example shows how to configure the software to ignore the accumulated interior
gateway protocol (AIGP) metric when performing best-path selection:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 50000
RP/0/RSP0/CPU0:router(config-bgp)#bgp bestpath aigp ignore
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
67
BGP Commands
bgp bestpath as-path multipath-relax
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When BGP multi-pathing is enabled, BGP load-balances user traffic within a single autonomous system (AS).
The criteria are that all attributes must match (weight, AS path, etc). However when a device is multi-homed
to multiple autonomous systems, BGP cannot load balance traffic between them by default. In order to enable
load-balancing of traffic among the multi-homed autonomous systems, the bgp bestpath as-path
multipath-relax command needs to be enabled. The criteria required for this is that the AS-path length should
be equal.
Before you use this command, ensure that BGP is enabled
Examples This example shows how to configure multipath load sharing on paths from different autonomous
systems in router mode:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 120
RP/0/RSP0/CPU0:router(config-bgp)#bgp bestpath as-path multipath-relax
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
68
BGP Commands
bgp client-to-client reflection disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, the clients of a route reflector are not required to be fully meshed and the routes from a client are
reflected to other clients. However, if the clients are fully meshed, route reflection is not required.
Examples In this example, the three neighbors are fully meshed, so client-to-client reflection is disabled:
bgp cluster-id, on page 71 Configures the cluster ID if the BGP cluster has more than one route
reflector.
route-reflector-client, on page 259 Configures the router as a BGP route reflector and configures the specified
neighbor as its client.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
69
BGP Commands
bgp client-to-client reflection disable
Command Description
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
70
BGP Commands
bgp cluster-id
bgp cluster-id
To configure the cluster ID if the Border Gateway Protocol (BGP) cluster has more than one route reflector,
use the bgp cluster-id command in an appropriate configuration mode. To remove the cluster ID, use the no
form of this command.
Syntax Description cluster-id Cluster ID of this router acting as a route reflector; maximum of 4 bytes. Cluster ID can be entered
either as an IP address or value. Range is 1 to 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Together, a route reflector and its clients form a cluster. A cluster of clients usually has a single route reflector.
In such instances, the cluster is identified by the software as the router ID of the route reflector. To increase
redundancy and avoid a single point of failure in the network, a cluster might have more than one route
reflector. If it does, all route reflectors in the cluster must be configured with the same 4-byte cluster ID so
that a route reflector can recognize updates from route reflectors in the same cluster.
bgp read,
write
Examples The following example shows how to configure the local router as one of the route reflectors serving
the cluster. Neighbor 192.168.70.24 is assigned to the default cluster with cluster-id 1.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
71
BGP Commands
bgp cluster-id
route-reflector-client, on page 259 Configures the router as a BGP route reflector and configures the specified
neighbor as its client.
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
72
BGP Commands
bgp confederation identifier
Syntax Description as-number Autonomous system (AS) number that internally includes multiple autonomous systems.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
One way to reduce the internal BGP (iBGP) mesh is to divide an autonomous system into multiple autonomous
systems and group them into a single confederation. Each autonomous system is fully meshed within itself,
and has a few connections to another autonomous system in the same confederation. Although the peers in
different autonomous systems have external BGP (eBGP) sessions, they exchange routing information as if
they are iBGP peers. Specifically, the confederation maintains the next hop and local preference information,
and that allows you to retain a single Interior Gateway Protocol (IGP) for all autonomous systems. To the
outside world, the confederation looks like a single autonomous system.
Use the bgp confederation identifier command to specify the autonomous system number for the
confederation. This autonomous system number is used when BGP sessions are established with external
peers in autonomous systems that are not part of the confederation.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
73
BGP Commands
bgp confederation identifier
Examples The following example shows how to divide the autonomous system into autonomous systems 4001,
4002, 4003, 4004, 4005, 4006, and 4007 with the confederation identifier 5. Neighbor 10.2.3.4 is a
router inside the confederation. Neighbor 172.20.16.6 is outside the routing domain confederation.
To the outside world, there appears to be a single autonomous system with the number 5.
bgp confederation peers, on page 75 Configures the autonomous systems that belong to the confederation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
74
BGP Commands
bgp confederation peers
Syntax Description as-number Autonomous system (AS) numbers for Border Gateway Protocol (BGP) peers that belong to
the confederation.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The autonomous systems specified in this command are visible internally to a confederation. Each autonomous
system is fully meshed within itself. The bgp confederation identifier, on page 73 command specifies the
confederation to which the autonomous systems belong.
To specify multiple autonomous systems, enter BGP confederation peer configuration mode then enter one
autonomous-system-number for each command line.
bgp read,
write
Examples The following example shows that autonomous systems 1090 and 1093 belong to a single
confederation:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
75
BGP Commands
bgp confederation peers
The following example shows that autonomous systems 1095, 1096, 1097, and 1098 belong to a
single confederation:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
76
BGP Commands
bgp dampening
bgp dampening
To enable Border Gateway Protocol (BGP) route dampening or change various BGP route dampening factors,
use the bgp dampening command in an appropriate configuration mode. To disable route dampening and
reset default values, use the no form of this command.
Syntax Description half-life (Optional) Time (in minutes) after which a penalty is decreased. Once the route
has been assigned a penalty, the penalty is decreased by half after the half-life period
(which is 15 minutes by default). Penalty reduction happens every 5 seconds. Range
of the half-life period is from 1 to 45 minutes.
reuse (Optional) Value for route reuse if the flapping route penalty decreases and falls
below the reuse value. When this happens, the route is unsuppressed. The process
of unsuppressing routes occurs at 10-second increments. Range is 1 to 20000.
suppress (Optional) Maximum penalty value. Suppress a route when its penalty exceeds the
value specified. When this happens, the route is suppressed. Range is 1 to 20000.
max-suppress-time (Optional) Maximum time (in minutes) a route can be suppressed. Range is 1 to
255. If the half-life value is allowed to default, the maximum suppress time defaults
to 60 minutes.
route-policy (Optional) Specifies the route policy to use to set dampening parameters.
route-policy-name
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
77
BGP Commands
bgp dampening
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp dampening command without arguments to enable BGP route dampening with the default
parameters. The parameters can be changed by setting them on the command line or specifying them with a
routing policy.
bgp read,
write
Examples The following example shows how to set the half-life value to 30 minutes, the reuse value to 1500,
the suppress value to 10000, and the max-suppress-time to 120 minutes:
clear bgp dampening, on page 121 Clears BGP route dampening information and unsuppresses the
suppressed routes.
route-policy (RPL) Defines a route policy and enters route-policy configuration mode.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
78
BGP Commands
bgp default local-preference
Syntax Description value Local preference value. Range is 0 to 4294967295. Higher values are preferable.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Generally, the default value of 100 allows you to easily define a particular path as less preferable than paths
with no local preference attribute. The preference is sent to all networking devices in the local autonomous
system.
bgp read,
write
Examples The following example shows how to raise the default local preference value from the default of 100
to 200:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
79
BGP Commands
bgp enforce-first-as disable
Command Default By default, the software requires the first autonomous system (in the AS path) of a route received from an
eBGP peer to be the same as the remote autonomous system configured.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, the software ignores any update received from an eBGP neighbor that does not have the autonomous
system configured for that neighbor at the beginning of the AS path. When configured, the command applies
to all eBGP peers of the router.
bgp read,
write
Examples The following example shows a configuration in which incoming updates from eBGP neighbors are
not checked to ensure the first AS number in the AS path is the same as the configured AS number
for the neighbor:
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
80
BGP Commands
bgp fast-external-fallover disable
Command Default BGP sessions of any directly adjacent external peers are immediately reset if the link used to reach them goes
down.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, BGP sessions of any directly adjacent external peers are immediately reset, which allows the
network to recover faster when links go down between BGP peers.
bgp read,
write
Examples The following example shows how to disable the automatic resetting of BGP sessions:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
81
BGP Commands
bgp graceful-restart
bgp graceful-restart
To enable graceful restart support, use the bgp graceful-restart command in an appropriate configuration
mode. To disable this function, use the no form of this command.
bgp graceful-restart
no bgp graceful-restart
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp graceful-restart command to enable graceful restart functionality on the router, and also to
advertise graceful restart to neighboring routers.
Note The bgp graceful-restart command with no options must be used to enable graceful restart before using
the bgp graceful-restart purge-time , bgp graceful-restart restart-time , bgp graceful-restart
stalepath-time , or bgp graceful-restart graceful-reset commands.
When graceful restart is enabled, the BGP graceful restart capability is negotiated with neighbors in the BGP
OPEN message when the session is established. If the neighbor also advertises support for graceful restart,
then graceful restart is activated for that neighbor session. If the neighbor does not advertise support for
graceful restart, then graceful restart is not activated for that neighbor session even though it is enabled locally.
If you enter the bgp graceful-restart command after some BGP sessions are established, you must restart
those sessions before graceful restart takes effect. Use the clear bgp command to restart sessions.
bgp read,
write
RP/0/RSP0/CPU0:router(config)#router bgp 3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
82
BGP Commands
bgp graceful-restart
RP/0/RSP0/CPU0:router(config-bgp)#bgp graceful-restart
bgp graceful-restart graceful-reset, on page 84 Enables a graceful reset if configuration changes force a
peer reset.
bgp graceful-restart purge-time, on page 85 Defines the maximum time before stale routes are purged.
bgp graceful-restart restart-time, on page 86 Defines the maximum time advertised to neighbors
bgp graceful-restart stalepath-time, on page 87 Defines the maximum time to wait for the End-of-RIB
message from a neighbor that has been restarted before
deleting learned routes.
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
83
BGP Commands
bgp graceful-restart graceful-reset
Command Default Graceful restart is not invoked when a configuration change forces a peer reset.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
BGP graceful restart must be enabled using the bgp graceful-restart command before enabling graceful
reset using the bgp graceful-restart graceful-reset command.
bgp read,
write
RP/0/RSP0/CPU0:router(config)#router bgp 3
RP/0/RSP0/CPU0:router(config-bgp)# bgp graceful-restart graceful-reset
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
84
BGP Commands
bgp graceful-restart purge-time
Syntax Description seconds Maximum time before stale routes are purged. Time in seconds. Range is 0 to 6000.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
BGP graceful restart must be enabled using the bgp graceful-restart command before setting the purge
time using the bgp graceful-restart purge-time command.
bgp read,
write
Examples The following example shows how to change the BGP purge time to 800 seconds:
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
85
BGP Commands
bgp graceful-restart restart-time
Syntax Description seconds Maximum time advertised to neighbors. Time in seconds. Range is 1 to 4095.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
BGP graceful restart must be enabled using the bgp graceful-restart command before setting the restart
timer using the bgp graceful-restart restart-time command.
bgp read,
write
Examples The following example shows how to change the BGP graceful restart time to 400 seconds:
RP/0/RSP0/CPU0:router(config)#router bgp 3
RP/0/RSP0/CPU0:router(config-bgp)# bgp graceful-restart restart-time 400
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
86
BGP Commands
bgp graceful-restart stalepath-time
Syntax Description seconds Maximum wait time. Time in seconds. Range is 1 to 4095.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
BGP graceful restart must be enabled using the bgp graceful-restart command before setting the stalepath
time using the bgp graceful-restart stalepath-time command.
If the stalepath time is exceeded before an End-of-RIB message is received from a neighbor, paths learned
from the neighbor are purged from the BGP routing table.
bgp read,
write
Examples The following example shows how to change the stalepath time to 750 seconds:
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
87
BGP Commands
bgp graceful-restart stalepath-time
Command Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
88
BGP Commands
bgp import-delay
bgp import-delay
To enable delay for Border Gateway Protocol (BGP) batch import processing, use the bgp import-delay
command in an appropriate configuration mode. To disable delay in batch import processing, use the no form
of this command.
Syntax Description seconds Specifies batch import processing delay in seconds. Range is 0 to 10 seconds.
milliseconds Specifies batch import processing delay in milliseconds. Range is 0 to 999 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set delay in batch import processing as two seconds and zero milliseconds:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#bgp import-delay 2 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
89
BGP Commands
bgp label-delay
bgp label-delay
To enable delay for Border Gateway Protocol (BGP) batch label processing, use the bgp label-delay command
in an appropriate configuration mode. To disable delay in batch import processing, use the no form of this
command.
Syntax Description seconds Specifies batch label processing delay in seconds. Range is 0 to 10 seconds.
milliseconds Specifies batch label processing delay in milliseconds. Range is 0 to 999 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set delay in batch import processing as two seconds and zero milliseconds:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#address-family ipv4 unicast
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
90
BGP Commands
bgp label-delay
RP/0/RSP0/CPU0:router(config-bgp-af)#bgp label-delay 2 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
91
BGP Commands
bgp log neighbor changes disable
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Logging of BGP neighbor status changes (up or down) and resets is used for troubleshooting network
connectivity problems and measuring network stability. Unexpected neighbor resets might indicate high error
rates or high packet loss in the network, and should be investigated.
Status change message logging does not substantially affect performance, unlike, for example, enabling
per-BGP update debugging. If the UNIX syslog facility is enabled, messages are sent by the software to the
UNIX host running the syslog daemon so that the messages can be stored and archived on disk. If the UNIX
syslog facility is not enabled, the status change messages are kept in the internal buffer of the router, and are
not stored to disk.
The neighbor status change messages are not tracked if the bgp log neighbor changes disable command is
disabled, except for the last reset reason, which is always available as output of the show bgp neighbors
command.
Up and down messages for BGP neighbors are logged by the software by default. Use the bgp log neighbor
changes disable command to stop logging BGP neighbor changes.
bgp read,
write
Examples The following example shows how to prevent the logging of neighbor changes for BGP:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
92
BGP Commands
bgp log neighbor changes disable
show bgp neighbors, on page 366 Displays information about the TCP and BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
93
BGP Commands
bgp maximum neighbor
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Any attempt to configure the neighbor limit below 1 or above 15000 fails. Similarly, attempting to configure
the limit below the number of neighbors currently configured fails. For example, if there are 3250 neighbors
configured, you cannot set the limit below 3250.
bgp write
Examples The following example shows how to change the default maximum neighbor limit and set it to 1200:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
94
BGP Commands
bgp multipath as-path
Syntax Description ignore Ignores as-path related check for multipath selection.
Usage Guidelines When multiple connected routers start ignoring as-path onwards while computing multipath, it causes routing
loops. Therefore, you should not configure the bgp multipath as-path ignore onwards command on routers
that can form a loop.
Examples This example shows how to ignore as-path while computing multipath.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# bgp multipath as-path ignore onwards
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
95
BGP Commands
bgp nexthop resolution allow-default
Command Default This applies to IPv4 and IPv6. The default route is 0.0.0.0/0 for IPv4 and ::/0 for IPv6.
The following example shows how to configure BGP with nexthop resolution allow-default :
RP/0/0/CPU0:R1(config)#router bgp 65000
RP/0/0/CPU0:R1(config-bgp)#nexthop resolution allow-default
"NEXTHOP configuration changed" is seen as the last reset reason with the show bgp neighbor
command when the nexthop resolution allow-default command is applied or removed:
RP/0/0/CPU0:R1#show bgp neighbor 10.0.0.2
...
Last reset 00:01:59, due to NEXTHOP configuration changed
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
96
BGP Commands
bgp policy propagation input flow-tag
Syntax Description bgp policy propagation input Enables flow-tag policy propagation on the specified interfaces.
flow-tag
destination The packets are matched based on an incoming destination IP address
and redirected to a specific VRF.
source The packets are matched based on an incoming source IP address and
redirect it to a specific VRF.
Interface configuration
Usage Guidelines Use this command to apply the flow-tag to a specified interface. The packets are matched based on an incoming
source, destination IP address or action (such as redirect, drop, PBTS) and redirected to a specific VRF.
Note You will not be able to enable both QPPB and flow tag feature simultaneously on an interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
97
BGP Commands
bgp redistribute-internal
bgp redistribute-internal
To allow the redistribution of internal Border Gateway Protocol (iBGP) routes into an Interior Gateway
Protocol (IGP), such as Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First
(OSPF), use the bgp redistribute-internal command in an appropriate configuration mode. To disable the
redistribution of iBGP routes into IGPs, use the no form of this command.
bgp redistribute-internal
no bgp redistribute-internal
Command Default By default, iBGP routes are not redistributed into IGPs.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use of the bgp redistribute-internal command requires the clear route * command to be issued to reinstall
all BGP routes into the IP routing table.
Note Redistributing iBGP routes into IGPs may cause routing loops to form within an autonomous system. Use
this command with caution.
bgp read,
write
Examples The following example shows how to redistribute iBGP routes into OSPF:
RP/0/RSP0/CPU0:router(config)#router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# bgp redistribute-internal
RP/0/RSP0/CPU0:router(config-bgp)# exit
RP/0/RSP0/CPU0:router(config)# router ospf area1
RP/0/RSP0/CPU0:router(config-router)# redistribute bgp 1
RP/0/RSP0/CPU0:router(config-router)# end
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
98
BGP Commands
bgp redistribute-internal
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
99
BGP Commands
bgp router-id
bgp router-id
To configure a fixed router ID for a Border Gateway Protocol (BGP)-speaking router, use the bgp router-id
command in an appropriate configuration mode. To disable a fixed router ID, use the no form of this command.
Syntax Description ip-address IP Version 4 (IPv4) address to use as the router ID. Normally, this should be an IPv4 address
assigned to the router.
Command Default If no router ID is configured in BGP, BGP attempts to use the global router ID if one is configured and
available. Otherwise, BGP uses the highest IP address configured on a loopback interface.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you do not use the bgp router-id command to configure a router ID, an IP address is not configured on
any loopback interface, and no global router ID is configured, BGP neighbors remain down.
For more details on router IDs, see the Routing Configuration Guide for Cisco ASR 9000 Series Routers
bgp read,
write
Examples The following example shows how to configure the local router with the router ID of 192.168.70.24:
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
100
BGP Commands
bgp scan-time
bgp scan-time
To configure scanning intervals of Border Gateway Protocol (BGP)-speaking networking devices, use the
bgp scan-time command in an appropriate configuration mode. To restore the scanning interval to its default
value, use the no form of this command.
Syntax Description seconds Scanning interval (in seconds) of BGP routing information. Range is 5 to 3600 seconds.
Release 4.0.0 Support was removed for all address family configuration modes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp scan-time command to change how frequently the software processes scanner tasks, such as
conditional advertisement, dynamic MED changes, and periodic maintenance tasks.
bgp read,
write
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
101
BGP Commands
bgp update-delay
bgp update-delay
To set the maximum initial delay for a Border Gateway Protocol (BGP)-speaking router to send the first
updates, use the bgp update-delay command in an appropriate configuration mode. To restore the initial
delay to its default value, use the no form of this command.
Syntax Description seconds Delay in seconds for the router to send the first updates. Range is 0 to 3600.
always (Optional) Specifies that the router always wait for the update delay time, even if all neighbors
have finished sending their initial updates sooner.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When BGP is started, it waits a specified period of time for its neighbors to establish peering sessions and to
complete sending their initial updates. After all neighbors complete their initial updates, or after the update
delay timer expires, the best path is calculated for each route, and the software starts sending advertisements
out to its peers. This behavior improves convergence time. If the software were to advertise a route as soon
as it learned it, it would have to readvertise the route each time it learned a new path that was preferred over
all previously learned paths.
Use the bgp update-delay command to tune the maximum time the software waits after the first neighbor
is established until it starts calculating best paths and sending out advertisements.
bgp read,
write
Examples The following example shows how to set the maximum initial delay to 240 seconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
102
BGP Commands
bgp write-limit
bgp write-limit
Note The bgp write-limit command is deprecated in Release 4.2.0, and replaced with update limit commands.
For more information, see the commands update limit, on page 513, update limit address-family, on page 514,
update limit sub-group, on page 516.
To modify the upper bounds on update message queue lengths or to enable desynchronization, use the bgp
write-limit command in an appropriate configuration mode. To return the bounds to their default values and
to disable desynchronization, use the no form of this command.
Syntax Description group-limit Per-update group limit on the number of update messages the software queues. Range is
500 to 100000000. Group limit cannot be greater than the global limit.
global-limit Global limit on the number of update messages the software queues. Range is 500 to
100000000.
Release 4.2.0 This command was deprecated and replaced with the update limit command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the bgp write-limit command to configure both a per-update group and a global limit on the number
of messages the software queues when updating peers. Increasing these limits can result in faster Border
Gateway Protocol (BGP) convergence, but also may result in higher memory use during convergence. In
addition, this command can be used to enable desynchronization. Desynchronization can decrease memory
use and speed up convergence for the fastest neighbors if one or more neighbors in an update group process
updates significantly slower than other neighbors in the same group. However, enabling desynchronization
can cause a significant degradation in overall convergence time, especially if the router is experiencing high
CPU utilization. For this reason, enabling desynchronization is discouraged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
103
BGP Commands
bgp write-limit
bgp read,
write
Examples The following example shows how to configure BGP to operate with a per-update group limit of
9000 messages and a global limit of 27,000 messages:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
104
BGP Commands
bmp-activate
bmp-activate
To enable Border Gateway Protocol (BGP) Monitoring Protocol (BMP) logging for a neighbor, use the
bmp-activate server command in neighbor configuration mode. To disable BMP logging for a neighbor, use
the no form of this command.
Syntax Description server server-id Enables monitoring by the BMP server specified by the server-id variable. You can
configure multiple bmp-activate commands under same neighbor with different server
IDs to enable monitoring by multiple BMP servers.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
Examples The following example shows how to activate BMP on a neighbor with IP address 1.1.1.1, which is
monitored by BMP server with server ID as 4:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 1.1.1.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# bmp-activate server 4
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
105
BGP Commands
bmp server
bmp server
To configure Border Gateway Protocol (BGP) Monitoring Protocol (BMP) server and to enter BMP server
configuration mode, use the bmp server command in Global Configuration mode. To remove a particular
BMP server configuration, use no form of this command.
description LINE Specifies BMP server description. Description can be up to 250 alphanumeric
characters.
initial-delay delay-time Sets the delay, in seconds, before initial connect request is sent to a BMP server.
The delay that you can set ranges from 1 to 3600 seconds. The default is 7 seconds.
initial-refresh {delay Delay to initiate route refresh requests to BMP enabled neighbors.
| skip}
Configures the initial refresh options to handle refresh requests sent by the router
to its BMP-enabled neighbors.
Sets the delay, in seconds, before an initial refresh request is sent by the router to
its BMP-enabled neighbors. The delay range is 1 to 3600 seconds with a default
of 1 second. The default is not to skip refresh requests.
Configures the router to skip sending any refresh requests to its BMP-enabled
neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
106
BGP Commands
bmp server
precedence Sets the precedence values in the IP header. The precedence value can be a number
from 0 to 7, or it can be one of the following keywords:
critical —Set packets with critical precedence (5)
flash — Set packets with flash precedence (3)
flash-override —Set packets with flash override precedence (4)
immediate —Set packets with immediate precedence (2)
internet —Set packets with internetwork control precedence (6)
network —Set packets with network control precedence (7)
priority —Set packets with priority precedence (1)
routine —Set packets with routine precedence (0)
The default is internet (6) .
stats-reporting-period Specifies statistics reporting period, in seconds, to BMP servers. The reporting
period that you can set ranges from 1 to 3600 seconds.
The default is 0.
update-source type Specifies the source (physical or virtual interface) to reach the BMP server.
interface-path-id
Note Use the show interfaces command to see a list of all interfaces currently
configured on the router.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
107
BGP Commands
bmp server
Examples This example shows how to configure initial refresh delay of 30 seconds for BGP neighbors on BMP
server with server ID as 4:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bmp server 4 initial-refresh delay 30
This example shows how to configure GigabitEthernet at location 0/0/0/1 as source interface to reach
BMP server:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bmp server 5 update-source gigabitEthernet 0/0/0/1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
108
BGP Commands
capability additional-paths receive
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the capability additional-paths receive command to selectively enable or disable additional paths receive
capability negotiation for a particular neighbor or neighbor-group or session-group. Configuring
additional-paths receive command in global address-family mode is a pre-requisite for negotiating additional
paths receive capability with the peer.
If you enter the capability additional-paths receive command after some BGP sessions are established, you
must restart those sessions for the new configuration to take effect. Use the clear bgp command to restart
sessions.
The following example shows how to advertise capability of receiving additional paths:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
109
BGP Commands
capability additional-paths receive
RP/0/RSP0/CPU0:router(config-bgp)#neighbor 10.2.3.4
RP/0/RSP0/CPU0:router(config-bgp-nbr)#capability additional-paths receive
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
110
BGP Commands
capability additional-paths send
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the capability additional paths send command to selectively enable or disable additional paths send
capability negotiation for a particular neighbor or neighbor-group or session-group. Configuring the
additional-paths send command in global address-family mode is a pre-requisite for negotiating additional
paths send capability with the peer.
You must restart the BGP sessions for the new configuration to take effect. Use the clear bgp command to
restart sessions.
The following example shows how to advertise capability of sending additional paths to the peer:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
111
BGP Commands
capability additional-paths send
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
112
BGP Commands
capability orf prefix
Syntax Description receive Sets the capability to receive the ORF from a specified neighbor.
both Sets the capability to receive and send the ORF from or to a specified neighbor.
none Sets the capability to no for ORF receive or send from or to a specified neighbor.
Command Default The routing device does not receive or send route prefix filter lists.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The advertisement of the prefix list ORF capability by a BGP speaker indicates whether the speaker can send
prefix lists to the specified neighbor and whether it accepts prefix lists from the neighbor. The speaker sends
a prefix list if it indicated the ability to send them, and if the neighbor indicated it was willing to accept them.
Similarly, the neighbor sends a prefix list to the speaker if it indicated the ability to send them and the speaker
indicated the willingness to accept them.
Note The capability orf and prefix list filter specified by orf route-policy must be explicitly configured.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
113
BGP Commands
capability orf prefix
If the neighbor sends a prefix list and the speaker accepts it, the speaker applies the received prefix list, plus
any locally configured outbound filters, to limit its outbound routing updates to the neighbor. Increased filtering
prevents unwanted routing updates between neighbors and reduces resource requirements for routing update
generation and processing.
Use the capability orf prefix command to set whether to advertise send and receive capabilities to the
specified neighbor.
Note Sending a receive capability can adversely affect performance, because updates sent to that neighbor cannot
be replicated for any other neighbors.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the
group inherit the configuration. Values of commands configured specifically for a neighbor override inherited
values.
bgp read,
write
Examples The following example shows how to configure the capability orf prefix command:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# route-policy orfqq
RP/0/RSP0/CPU0:router:(config-rpl)# if orf prefix in (10.0.0.0/8 ge 20) then
RP/0/RSP0/CPU0:router(config-rpl)# pass
RP/0/RSP0/CPU0:router(config-rpl)# endif
RP/0/RSP0/CPU0:router(config-rpl)# if orf prefix in (1910::16 ge 120) then
RP/0/RSP0/CPU0:router(config-rpl)# pass
RP/0/RSP0/CPU0:router(config-rpl)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
RP/0/RSP0/CPU0:router(config)# router bgp 65530
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.0.101.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# remote-as 65534
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# route-policy pass-all out
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# capability orf prefix both
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# orf route-policy orfqq
af-group, on page 27 Creates an address family group for BGP neighbors and enters address
family group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
show bgp neighbors, on page 366 Displays information about BGP neighbors. Use the received prefix-filter
keywords to display information on the prefix list filter.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
114
BGP Commands
capability suppress 4-byte-as
Syntax Description inheritance-disable Prevents capability suppress 4-type-as being inherited from the parent.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, the software advertises the 4-byte AS capability to BGP peers. To override this default behavior,
use the capability suppress 4-byte-as command under the command modes listed in the ''Command Modes''
section. If configured under the neighbor group or session group, all neighbors using the group inherit the
configuration. Use the no option to remove the command.
Caution The BGP session resets automatically, if the 4-byte AS capability of an existing BGP session is changed by
configuring capability suppress 4-byte-as or capability suppress 4-byte-as inheritance-disable .
bgp read,
write
Examples The following example shows how to configure the capability suppress 4-byte-as command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
115
BGP Commands
capability suppress 4-byte-as
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
116
BGP Commands
capability suppress 4-byte-as
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
117
BGP Commands
clear bgp
clear bgp
To reset a group of Border Gateway Protocol (BGP) neighbors, use the clear bgp command in EXEC mode.
clear bgp [{ipv4 {unicast | labeled-unicast | all | tunnel } | ipv6 {unicast} | all {unicast | multicast |
all | labeled-unicast | tunnel} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast}
| ipv6 unicast}}]
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast and labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address prefixes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
118
BGP Commands
clear bgp
Use the clear bgp command to reset the sessions of the specified group of neighbors (hard reset); it removes
the TCP connection to the neighbor, removes all routes received from the neighbor from the BGP table, and
then re-establishes the session with the neighbor.
If the graceful keyword is specified, the routes from the neighbor are not removed from the BGP table
immediately, but are marked as stale. After the session is re-established, any stale route that has not been
received again from the neighbor is removed.
bgp execute
Examples The following example shows how to hard reset neighbor 10.0.0.1:
clear bgp soft, on page 138 Soft resets a group of BGP neighbors.
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about the TCP and BGP connections to
neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
119
BGP Commands
cef consistency-hashing auto-recovery
Usage Guidelines Configuring the command does not alter the current state. The command takes effect on the next link down
or up events.
Example
Router# configure
Router(config)# cef consistent-hashing auto-recovery
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
120
BGP Commands
clear bgp dampening
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast For VRF, specifies IPv4 unicast and labeled-unicast address families.
}
Command Default If no IP address is specified, dampening information for all routes is cleared.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
121
BGP Commands
clear bgp dampening
Always use the clear bgp dampening command for an individual address-family. The all option for
address-families with clear bgp dampening should never be used during normal functioning of the system.
For example, use
clear bgp ipv4 unicast dampening prefix x.x.x./y
bgp execute
Examples The following example shows how to clear the route dampening information for all 172.20.0.0/16
IPv4 unicast paths:
bgp dampening, on page 77 Enables BGP route dampening or changes various BGP route
dampening factors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
122
BGP Commands
clear bgp external
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
graceful (Optional) Clears all external peers with a hard reset and a graceful restart.
This option is available when an address family is not specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
123
BGP Commands
clear bgp external
bgp execute
Examples The following example shows how to clear all BGP external peers:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
124
BGP Commands
clear bgp flap-statistics
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast } For VRF, specifies IPv4 unicast or labeled-unicast address families.
regexp regexp (Optional) Clears flap statistics for routes whose AS paths match the
regular expression.
route-policy route-policy-name (Optional) Clears flap statistics for the specific route policy.
/mask-length (Optional) Network mask of the network for which flap counts are to
be cleared.
ip-address (Optional) Neighbor address. Clears only flap statistics for routes
received from this neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
125
BGP Commands
clear bgp flap-statistics
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp execute
Examples The following example shows how to clear the flap count for all routes (in all address families)
originating in autonomous system 1:
The following example shows how to clear the flap count for all IPv4 unicast routes received from
neighbor 172.20.1.1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
126
BGP Commands
clear bgp long-lived-stale
clear bgp vrf {vrf-name | all} {ipv4 | ipv6} unicast nbr-address long-lived-stale
Syntax Description vrf vrf-name Deletes all paths received from the given neighbor that are long-lived-stale for the specified
VRF
vrf all Deletes all paths received from the given neighbor that are long-lived-stale for all VRFs.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
This command deletes all paths received from the given neighbor for all VRFs:
RP/0/0/CPU0:router# clear bgp vrf all ipv4 unicast 192.172.20.10 long-lived-stale
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
127
BGP Commands
clear bgp nexthop performance-statistics
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast } For VRF, specifies IPv4 unicast or labeled-unicast address families.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear bgp nexthop performance-statistics command to reset the total number of notifications
received from the Routing Information Base (RIB) and the cumulative next-hop processing time. The following
information is cleared from the show bgp nexthops command output:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
128
BGP Commands
clear bgp nexthop performance-statistics
bgp execute
Examples The following example shows how to clear next-hop performance statistics:
show bgp nexthops, on page 393 Displays information about the BGP next-hop notifications.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
129
BGP Commands
clear bgp nexthop registration
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast } For VRF, specifies IPv4 unicast or labeled-unicast address families.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
130
BGP Commands
clear bgp nexthop registration
Use the clear bgp nexthop registration command to perform an asynchronous registration of the next hop
with the RIB. The show bgp nexthops command output shows a critical notification as the LastRIBEvent
for the next hop when the clear bgp nexthop registration command is used.
bgp execute
Examples The following example shows how to reregister the next hop with the RIB:
show bgp nexthops, on page 393 Displays information about the BGP next-hop notifications.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
131
BGP Commands
clear bgp peer-drops
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp execute
Examples The following example shows how to clear the connection-dropped counter for all BGP neighbors:
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
132
BGP Commands
clear bgp performance-statistics
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp execute
Examples The following example shows how to clear the performance statistics for all address families:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
133
BGP Commands
clear bgp self-originated
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast } For VRF, specifies IPv4 unicast or labeled-unicast address families.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Self-originated routes are routes locally originated by the network command, redistribute command, or
aggregate-address command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
134
BGP Commands
clear bgp self-originated
bgp execute
Examples The following example shows how to clear self-originated IPv4 routes:
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate and
advertise to its neighbors.
redistribute (BGP), on page 242 Redistributes routes from another routing protocol into BGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
135
BGP Commands
clear bgp shutdown
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast } For VRF, specifies IPv4 unicast or labeled-unicast address families.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp execute
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
136
BGP Commands
clear bgp shutdown
Examples The following example shows how to clear all shut-down BGP neighbors:
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about the TCP and BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
137
BGP Commands
clear bgp soft
clear bgp {ipv4{unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast |
multicast | labeled-unicast | all } | all {unicast | multicast | labeled-unicast | all | tunnel |
mdt} | vpnv4 unicast | vrf {vrf-name | all} | vpnv6 unicast} {* ip-address | asas-number |
external}soft[[{in | {prefix-filter} | out}]]
all For subaddress families, specifies prefixes for all subaddress families.
all For address family, specifies prefixes for all address families.
ipv4 { unicast | For VRF, specifies IPv4 unicast or labeled-unicast address families.
labeled-unicast }
as as-number Autonomous system (AS) number for all neighbors to be reset. Range for
2-byte numbers is 1 to 65535. Range for 4-byte numbers is 1.0 to
65535.65535.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
138
BGP Commands
clear bgp soft
prefix-filter (Optional) Specifies to send a new Outbound Route Filter (ORF) to the
neighbor. Neighbor installs the new ORF and resends its routes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear bgp soft command to trigger a soft reset of the specified address families for the specified
group of neighbors. This command is useful if you change the inbound or outbound policy for the neighbors,
or any other configuration that affects the sending or receiving of routing updates.
If an outbound soft reset is triggered, BGP resends all routes for the address family to the given neighbors.
If an inbound soft reset is triggered, BGP by default sends a REFRESH request to the neighbor, if the neighbor
has advertised the ROUTE_REFRESH capability. To determine whether the neighbor has advertised the
ROUTE_REFRESH capability, use the show bgp neighbors command, and look for the following line of
output:
If the neighbor does not support route refresh, but the soft-reconfiguration inbound command is configured
for the neighbor, then BGP uses the routes cached as a result of the soft-reconfiguration inbound command
to perform the soft reset.
If you want BGP to use the cached routes even if the neighbor supports route refresh, you can use the always
keyword when configuring the soft-reconfiguration inbound command.
If the neighbor does not support route refresh and the soft-reconfiguration inbound command is not
configured, then inbound soft reset is not possible. In this case, an error is printed.
Note By default, if the configuration for an inbound or outbound route policy is changed, BGP performs an automatic
soft reset. Use the bgp auto-policy-soft-reset disable command to disable this behavior.
bgp execute
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
139
BGP Commands
clear bgp soft
Examples The following example shows how to trigger an inbound soft clear for IPv4 unicast routes received
from neighbor 10.0.0.1:
bgp auto-policy-soft-reset disable, on page 53 Disables an automatic soft reset of BGP peers when the
configured inbound route policy is modified.
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp neighbors, on page 366 Displays information about the TCP and BGP connections
to neighbors.
soft-reconfiguration inbound, on page 494 Configures the software to store updates received from a
neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
140
BGP Commands
default-information originate (BGP)
default-information originate
no default-information originate
Command Default BGP does not permit redistribution of a default route into BGP.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the redistribute command to redistribute routes from another protocol into BGP. By default, if these
routes include the default route (0.0.0.0/0 for IPv4 or ::/0 for IPv6), the default route is ignored. Use the
default-information originate command to change this behavior so that the default route is not ignored and
is redistributed into BGP along with the other routes for the protocol being redistributed.
bgp read,
write
Examples The following example shows how to configure BGP to redistribute the default route into BGP:
redistribute (BGP), on page 242 Redistributes routes from another protocol into BGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
141
BGP Commands
default-martian-check disable
default-martian-check disable
To disable the Martian check on the IPv4 and IPv6 prefixes, use the default-martian-check disable command
in the address-family configuration mode. To enable the Martian check on the IPv4 and IPv6 prefixes, use
the no form of this command.
default-martian-check disable
no default-martian-check disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples This example shows how to disable Martian check for an IPv4 address prefix.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 multicast
RP/0/RSP0/CPU0:router(config-bgp-af)# default-martian-check disable
This example shows how to disable Martian check for an IPv6 address prefix.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv6 multicast
RP/0/RSP0/CPU0:router(config-bgp-af)# default-martian-check disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
142
BGP Commands
default-metric (BGP)
default-metric (BGP)
To set default metric values for the Border Gateway Protocol (BGP), use the default-metric command in
an appropriate configuration mode. To disable metric values, use the no form of this command.
default-metric value
no default-metric [value]
Syntax Description value Default metric value appropriate for the specified routing protocol. Range is 1 to 4294967295.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-metric command to set the Multi Exit Discriminator (MED) to advertise to peers for routes
that do not already have a metric set (routes that were received with no MED attribute).
Note The metric values that you apply using the default-metric command take effect only for a new prefix which
gets into the BGP table. The metrics for the existing prefixes in the BGP table remain the same. Also, when
you remove the default-metric command from the configuration, the metrics which were previously assigned
for prefixes are not updated. To get out of this condition, clear the BGP neighborship.
bgp read,
write
Examples The following example shows how to set the BGP default metric:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
143
BGP Commands
default-originate
default-originate
To cause a Border Gateway Protocol (BGP) speaker (the local router) to send the default route 0.0.0.0/0 to a
neighbor for use as a default route, use the default-originate command in an appropriate configuration mode.
To disable this function, use the no form of this command.
Syntax Description inheritance-disable (Optional) Prevents the default-originate command characteristics from
being inherited from a parent group.
route-policy route-policy-name (Optional) Specifies the name of a route policy. The route policy allows
route 0.0.0.0 to be injected conditionally. IPv6 address family is supported.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Release 5.3.2 This command is supported in L2VPN EVPN address family group configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The default-originate command does not require the presence of the default route (0.0.0.0/0 for IPv4 or ::/0
for IPv6) in the local router. When the default-originate command is used with a route policy, the default
route is advertised if any route in the BGP table matches the policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
144
BGP Commands
default-originate
In the L2VPN EVPN address-family group configuration mode, conditional advertising of the default route
using a route policy is not supported.
bgp read,
write
Examples The following example shows how to unconditionally advertise the route 0.0.0.0/0 to the neighbor
172.20.2.3:
The following example shows how to advertise the route 0.0.0.0/0 to the neighbor 172.20.2.3 only
if a route exists in the BGP table that matches the route policy called default-default-policy:
default-information originate (BGP), on Allows the default route to be redistributed into BGP from another
page 141 routing protocol.
af-group, on page 27 Creates an address family group for BGP neighbors and enters
address family group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration
mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
145
BGP Commands
description (BGP)
description (BGP)
To annotate a neighbor, neighbor group, VPN routing and forwarding (VRF) neighbor, or session group, use
the description command in an appropriate configuration mode. To remove the annotation, use the no form
of this command.
description text
no description [{text}]
Neighbor configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the description command to provide a description of a neighbor, neighbor group, VRF neighbor, or
session group. The description is used to save user comments and does not affect software function.
bgp read,
write
Examples The following example shows how to configure the description “Our best customer” on the neighbor
192.168.13.4:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)#router bgp 65000
RP/0/RSP0/CPU0:router(config-bgp)#neighbor 192.168.13.4
RP/0/RSP0/CPU0:router(config-bgp-nbr)#description Our best customer
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
146
BGP Commands
distance bgp
distance bgp
To allow the use of external, internal, and local administrative distances that could be used to prefer one class
of routes over another, use the distance bgp command in an appropriate configuration mode. To disable the
use of administrative distances, use the nono form of this command.
Syntax Description external-distance Administrative distance for Border Gateway Protocol (BGP) external routes. External
routes are routes for which the best path is learned from a neighbor external to the
autonomous system. Range is 1 to 255. Routes with a distance of 255 are not installed in
the routing table.
internal-distance Administrative distance for BGP internal routes. Internal routes are those routes that are
learned from another BGP entity within the same autonomous system. Range is 1 to 255.
Routes with a distance of 255 are not installed in the routing table.
local-distance Administrative distance for BGP local routes. The local-distance argument applies to
locally generated aggregate routes (such as the routes generated by the aggregate-address
command) and backdoor routes installed in the routing table. Range is 1 to 255. Routes
with a distance of 255 are not installed in the routing table.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the distance bgp command if another protocol is known to be able to provide a better route to a node
than was actually learned using external BGP, or if some internal routes should be preferred by BGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
147
BGP Commands
distance bgp
Note Changing the administrative distance of BGP internal routes is considered risky and is not recommended.
One problem that can arise is the accumulation of routing table inconsistencies, which can interfere with
routing.
bgp read,
write
Examples The following example shows that iBGP routes are preferable to locally generated routes, so the
administrative distance values are set accordingly:
distance (IS-IS) Defines the administrative distance assigned to routes discovered by the IS-IS protocol.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
148
BGP Commands
distribute bgp-ls (ISIS)
Syntax Description instance-id value (Optional) Specifies the instance identifier defined by the router isis command. Range
is from 1 to 65535.
If the instance-id is not configured, the system assigned instance-id for the ISIS process
will be used.
level 1 | 2 (Optional) Displays IS-IS link-state database for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples This example shows how to distribute ISIS link-state information using BGP LS:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router isis foo
RP/0/RSP0/CPU0:router(config-isis)# distribute bgp-ls instance-id 32 level 2 throttle 5
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
149
BGP Commands
distribute bgp-ls (OSPF)
Syntax Description instance-id value (Optional) Specifies the instance identifier defined by the router ospf command. Range
is from 1 to 65535.
If the instance-id is not configured, the system assigned instance-id for the OSPF process
is used.
throttle (Optional) Specifies throttle time between successive link-state advertisement (LSA)
updates. Range is from 0 to 3600.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples This example shows how to distribute OSPF link-state information using BGP LS:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)# distribute bgp-ls instance-id 32 throttle 10
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
150
BGP Commands
domain-distinguisher
domain-distinguisher
To configure globally unique identifier ASN for IGP domain, use the domain-distinguisher command in
address-family link-state configuration mode. To remove unique identifier, use the no form of this command.
domain-distinguisher unique-id
no domain-distinguisher
Syntax Description unique-id Specifies four-octet unique identifier ASN. Range is from 1 to 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family link-state link-state
RP/0/RSP0/CPU0:router(config-bgp-af)# domain-distinguisher 1234
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
151
BGP Commands
dmz-link-bandwidth
dmz-link-bandwidth
To originate a demilitarized zone (DMZ) link bandwidth extended community for the link to an eBGP or
iBGP neighbor, use the dmz-link-bandwidth command in an Neighbor configuration mode. To stop
origination of the DMZ link bandwidth extended community, use the no form of this command.
dmz-link-bandwidth [{inheritance-disable}]
no dmz-link-bandwidth
Syntax Description inheritance-disable (Optional) Prevents the dmz-link-bandwidth command from being inherited from
a parent group.
Command Default BGP does not originate the DMZ link bandwidth extended community.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the dmz-link-bandwidth command to advertise the bandwidth of links that are used to exit an autonomous
system.
bgp read,
write
Examples This example shows how to advertise the bandwidth of links to eBGP neighbors from router bgp 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
152
BGP Commands
dmz-link-bandwidth
Command Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
153
BGP Commands
dscp (BGP)
dscp (BGP)
To set the differentiated services code point (DSCP) value, use the dscp command in the appropriate
configuration mode. To remove the dscp command from the configuration file and restore the system to its
default interval values, use the no form of this command.
dscp value
no dscp [{value}]
Syntax Description value Value of the DSCP. The DSCP value can be a number from 0 to 63, or it can be one of the following
keywords: default , ef , af11 , af12 , af13 , af21 , af22 , af23 , af31 , af32 , af33 , af41 ,
af42 , af43 , cs1 , cs2 , cs3 , cs4 , cs5 , cs6 , or cs7 .
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the dscp command to change the minimum and maximum packet thresholds for the DSCP value.
Table 3: dscp Default Settings, on page 154 lists the DSCP default settings used by the dscp command. The
DSCP value, corresponding minimum threshold, maximum threshold, and mark probability are listed. The
last row of the table (the row labeled "default") shows the default settings used for any DSCP value not
specifically shown in the table.
af11 32 40 1/10
af12 28 40 1/10
af13 24 40 1/10
af21 32 40 1/10
af22 28 40 1/10
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
154
BGP Commands
dscp (BGP)
af23 24 40 1/10
af31 32 40 1/10
af32 28 40 1/10
af33 24 40 1/10
af41 32 40 1/10
af42 28 40 1/10
af43 24 40 1/10
cs1 22 40 1/10
cs1 24 40 1/10
cs3 26 40 1/10
cs4 28 40 1/10
cs5 30 40 1/10
cs6 32 40 1/10
cs7 34 40 1/10
ef 36 40 1/10
default 20 40 1/10
bgp read,
write
Examples The following example shows how to set the DSCP value to af32:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
155
BGP Commands
ebgp-multihop
ebgp-multihop
To accept and attempt Border Gateway Protocol (BGP) connections to external peers residing on networks
that are not directly connected, use the ebgp-multihop command in an appropriate configuration mode. To
disable connections to external peers and allow only direct connections between neighbors, use the no form
of this command.
Syntax Description ttl-value (Optional) Time-to-live (TTL) value. Range is 1 to 255 hops.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the ebgp-multihop command to enable multihop peerings with external BGP neighbors. The BGP
protocol states that external neighbors must be directly connected (one hop away). The software enforces this
by default; however, the ebgp-multihop command can be used to override this behavior.
Use of the mpls option in the ebgp-multihop command prevents BGP from enabling MPLS on the peering
interface and also prevents allocation of Implicit-NULL rewrite labels for nexthop addresses learned from
the peer. This is useful in some scenarios in which MPLS forwarding labels to the nexthops have already been
learned via BGP labeled-unicast or LDP.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit
the configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
156
BGP Commands
ebgp-multihop
Examples The following example shows how to allow a BGP connection to neighbor 172.20.16.6 of up to 255
hops away:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
157
BGP Commands
export route-policy
export route-policy
To configure an export route policy, use the export route-policy command in an appropriate configuration
mode. To restore the system to its default condition, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the export route-policy command to define the conditions that allow specified routes to be tagged with
specified route-targets.
bgp read,
write
ip-services read,
write
Examples The following example shows how to configure an export route policy:
import route-policy, on page 167 Specifies a route policy to import routes into the VRF instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
158
BGP Commands
export route-target
export route-target
To configure a VPN routing and forwarding (VRF) export route-target extended community, use the export
route-target command in an appropriate configuration mode. To restore the system to its default condition,
use the no form of this command.
Syntax Description as-number:nn (Optional) as-number —Autonomous system (AS) number of the route-target extended
community.
• as-number
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
• nn —32-bit number
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Export route-target extended communities are associated with prefixes when advertised to remote provider
edge (PE) routers. The remote PE routers import the route-target extended communities into a VRF instance
that has the import route-targets that match the exported route-target extended communities.
To specify multiple route targets, enter export route target configuration mode then enter one route target for
each command line.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
159
BGP Commands
export route-target
bgp read,
write
ip-services read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
160
BGP Commands
graceful-maintenance
graceful-maintenance
To allow the network to perform convergence before the router or link is taken out of service, use the
graceful-maintenance command in the router BGP, neighbor or neighbor group configuration mode, as
appropriate. To disable the command, use the no form of this command.
Note This command is executed in either the neighbor configuration or neighbor group configuration mode.
Syntax Description activate Announces routes with the graceful maintenance attributes while activated either
under the neighbor or router BGP configuration. While activated, all routes to this
neighbor are announced with the attribute configured here and all routes from this
neighbor are announced to other neighbors with the graceful maintenance attributes
configured under those neighbors. The GSHUT community is announced regardless
of the other attributes configured here. To allow the GSHUT community to be
announced to eBGP neighbors, you must configure the send-community-gshut-ebgp
command.
all-neighbors If you use the all-neighbors keyword, Graceful Maintenance is activated even for
those neighbors that do not have Graceful Maintenance activated.
retain-routes Choosing retain-routes causes RIB to retain BGP routes when the BGP process is
stopped. You would use retain-routes when only BGP is being brought down instead
of the entire router and if it is known that neighboring routers are being kept in
operation during the maintenance of the local BGP. If RIB has alternative routes
provided by another protocol or a default route, then it is recommended not to retain
BGP routes after the BGP process stops.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
161
BGP Commands
graceful-maintenance
as-prepends Indicates the number of times to prepend the local AS number to the AS path of routes.
as-prepends-value The default value is 0. The keyword inheritance-disable prevents AS prepends from
inheritance-disable being inherited from the parent.
Specifies the number of times to prepend the local AS number to the AS path of routes
and advertises the GSHUT community with the local preference value specified for
the routes. When the router adds the GSHUT community to a route as it advertises it,
it also changes the LOCAL_PREF attribute and prepends the local AS number as
specified in the commands. Sending GSHUT provides flexibility in how neighboring
routers handle the lower preference: they can match it in a route policy and do the
most appropriate thing with it. On the other hand, in simple networks, it is
recommended to set local-preference to 0, rather than to create route policies
everywhere else.
Note LOCAL_PREF is not sent to real eBGP neighbors, but sent to confederation
member AS eBGP neighbors. To lower preference to eBGP neighbors,
as-prepends is required.
local-preference Indicates the range of values for Local Preference. The keyword inheritance-disable
local-pref-value prevents local preference from being inherited from the parent.
inheritance-disable
neighbor configuration
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
162
BGP Commands
host-reachability protocol bgp
Command Default The VTEP relies on a multicast-based data plane flood-and-learn behavior for VTEP peer discovery and
end-host reachability information as defined in the initial IETF VXLAN standards (RFC 7348).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
The following example configuration shows BGP configured as the control plane for a Network
Virtualization EndPoint (NVE) interface (VTEP) that is associated with a VxLAN with identifier 1.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface nve 1
RP/0/RSP0/CPU0:router(config-nve)# member vni 1
RP/0/RSP0/CPU0:router(config-nve-vni)# host-reachability protocol bgp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
163
BGP Commands
ibgp policy out enforce-modifications
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the ibgp policy out enforce-modifications command to set and modify BGP route attributes for updates
to iBGP peers.
If the ibgp policy out enforce-modifications command is configured under router BGP configuration,
then all the changes made by the outbound policy for an iBGP peer will be present in an update message sent
to the peer.
bgp read,
write
Examples The following example shows how to set the ibgp policy out enforce-modifications:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 6500
RP/0/RSP0/CPU0:router(config-bgp)# ibgp policy out enforce-modifications
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
164
BGP Commands
import
import
To configure the import and export of BGP NLRIs between two BGP neighbors with respect to the route
target identifiers, use the import command in the BGP neighbor address family configuration mode. To undo
this command configuration, run the no form of this command.
Syntax Description reoriginate Imports NLRIs that match normal route target identifier
and exports re-originated NLRIs assigned with the
normal route target identifier.
reoriginate stitching-rt Imports NLRIs that match normal route target identifier
and exports re-originated NLRIs assigned with the
stitching route target identifier
stitching-rt reoriginate Imports NLRIs that match stitching route target identifier
and exports re-originated NLRIs assigned with the
normal route target identifier.
stitching-rt reoriginate stitching-rt Imports NLRIs that match stitching route target identifier
and exports re-originated NLRIs assigned with the
stitching route target identifier.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
165
BGP Commands
import
Example
The following example shows how to configure DCI router to import BGP NLRIs that match normal
route target identifier and to export re-originated BGP NLRIs assigned with the stitching route target
identifier.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 1.1.1.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family l2vpn evpn
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# import reoriginate stitching-rt
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
166
BGP Commands
import route-policy
import route-policy
To configure an import route policy, use the import route-policy command in an appropriate configuration
mode. To restore the system to its default condition, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the import route-policy command to define the conditions that allow specified routes to be imported
into the VPN routing and forwarding (VRF) instance if the routes are tagged with specified route-targets.
bgp read,
write
ip-services read,
write
Examples The following example shows how to allow only policy-B to be imported to VRF:
export route-policy, on page 158 Specifies a route policy to export routes from the VRF instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
167
BGP Commands
import route-target
import route-target
To configure a VPN routing and forwarding (VRF) import route-target extended community, use the import
route-target command in an appropriate configuration mode. To restore the system to its default condition,
use the no form of this command.
Syntax Description as-number:nn (Optional) Autonomous system (AS) number of the route-target extended community.
• as-number
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
• nn —32-bit number
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the import route-target command to specify that prefixes associated with the configured import
route-target extended communities are imported into the VRF instance.
To specify multiple route targets, enter import route target configuration mode, then enter one route target for
each command line.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
168
BGP Commands
import route-target
bgp read,
write
ip-services read,
write
RP/0/RSP0/CPU0:router(config)#vrf vrf-1
RP/0/RSP0/CPU0:router(config-vrf)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-vrf-af)# import route-target 500:99
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
169
BGP Commands
ignore-connected-check
ignore-connected-check
To enable the software to bypass the directly connected next hop check for single-hop eBGP peering, use the
ignore-connected-check command in an appropriate configuration mode. To re-enable the directly connected
next hop check, use the no form of this command.
ignore-connected-check [{inheritance-disable}]
no ignore-connected-check
Syntax Description inheritance-disable Prevents the ignore-connected-check command from being inherited from the parent.
Command Default Ability to bypass the directly connected next hop check is disabled.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to enable ignore-connected check configuration for neighbor
10.2.3.4:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
170
BGP Commands
is-best-path
is-best-path
To tag the path selected as the best path use theis-best-path command in route policy configuration mode.
is-best-path
Syntax Description is-best-path Checks and tags the path selected as best-path.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
RP/0/RSP0/CPU0:router(config)# route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# if destination i
in is-backup-path is-best-external is-best-path
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
171
BGP Commands
is-backup-path
is-backup-path
To tag all the paths equal to the back up path use, is-backup-path command in route policy configuration
mode.
is-backup-path
Syntax Description is-backup-path Checks and tags the path selected as backup path.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
RP/0/RSP0/CPU0:router(config)# route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# if destination i
in is-backup-path is-best-external is-best-path
RP/0/RSP0/CPU0:router(config)# route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# if destination i
in is-backup-path is-best-external is-best-path
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
172
BGP Commands
is-multi-path
is-multi-path
To tag all the paths equal to the best path based on multi-path context use, is-multi-path command in route
policy configuration mode.
is-multi-path
Syntax Description is-multi-path Checks and tag all the path equal to the as best-path.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
RP/0/RSP0/CPU0:router(config)#route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)#route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)#if destination i
in is-backup-path is-best-external is-best-path
is-multi-path
RP/0/RSP0/CPU0:router(config-rpl)#if destination is-
is-backup-path is-best-external is-best-path is-multi-path
RP/0/RSP0/CPU0:router(config-rpl)#if destination is-best-path then
RP/0/RSP0/CPU0:router(config-rpl-if)#set l
label label-index label-mode level
community lsm-root
RP/0/RSP0/CPU0:router(config-rpl-if)#set community community
RP/0/RSP0/CPU0:router(config-rpl-if)#endif
RP/0/RSP0/CPU0:router(config-rpl)#end-policy
RP/0/RSP0/CPU0:router(config)#commit
Wed Jul 8 16:08:23.436 IST
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
173
BGP Commands
keychain
keychain
To apply key chain-based authentication on a TCP connection between two Border Gateway Protocol (BGP)
neighbors, use the keychain command in an appropriate configuration mode. To disable key chain
authentication, use the no form of this command.
keychain name
no keychain [{name}]
Syntax Description name Key chain name configured using the keychain command. The name must be a maximum of 32
alphanumeric characters.
Command Default When this command is not specified in the appropriate configuration mode, key chain authentication is not
enabled on a TCP connection between two BGP neighbors.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Specify a key chain to enable key chain authentication between two BGP peers. Use the keychain command
to implement hitless key rollover for authentication.
If this command is configured for a neighbor group or a session group, a neighbor using the group inherits
the configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Examples The following example shows how to configure neighbor 172.20.1.1 to use the key chain authentication
configured in the keychain_A key chain:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
174
BGP Commands
keychain
keychain-disable, on page 176 Overrides any inherited key chain configuration from a neighbor group or
session group for BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
175
BGP Commands
keychain-disable
keychain-disable
Note Effective with Release 3.9.0, the keychain-disable command was replaced by the keychain
inheritance-disable command. See the keychain inheritance-disable, on page 178 command for more
information.
To override any inherited key chain configuration from a neighbor group or session group for Border Gateway
Protocol (BGP) neighbors, use the keychain-disable command in an appropriate configuration mode. To
disable overriding any inherited key chain command, use the no form of this command.
keychain-disable
no keychain-disable
Command Default Configured key chains for neighbor and session groups are inherited.
Release 3.9.0 This command was replaced by the keychain inheritance-disable command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you specify a key chain on a neighbor group or session group, all users of the group inherit the key chain.
Specifying a different keychain command specifically on a neighbor that uses the group overrides the
inherited value. Specifying keychain-disable on a neighbor that uses the group disables key chain
authentication for the neighbor.
bgp read,
write
Examples The following example shows how to disable key chain authentication for neighbor 172.20.1.1,
preventing it from inheriting the key chain keychain_A from session group group1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
176
BGP Commands
keychain-disable
keychain, on page 174 Enables key chain authentication on a TCP connection between two BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
177
BGP Commands
keychain inheritance-disable
keychain inheritance-disable
To override any inherited key chain configuration from a neighbor group or session group for Border Gateway
Protocol (BGP) neighbors, use the keychain inheritance-disable command in an appropriate configuration
mode. To disable overriding any inherited key chain command, use the no form of this command.
keychain inheritance-disable
no keychain inheritance-disable
Command Default Configured key chains for neighbor and session groups are inherited.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you specify a key chain on a neighbor group or session group, all users of the group inherit the key chain.
Specifying a different keychain command specifically on a neighbor that uses the group overrides the
inherited value. Specifying keychain inheritance-disable on a neighbor that uses the group disables key
chain authentication for the neighbor.
bgp read,
write
Examples The following example shows how to disable key chain authentication for neighbor 172.20.1.1,
preventing it from inheriting the key chain keychain_A from session group group1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
178
BGP Commands
keychain inheritance-disable
keychain, on page 174 Enables key chain authentication on a TCP connection between two BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
179
BGP Commands
label-allocation-mode
label-allocation-mode
To set the MPLS/VPN label allocation mode, use the label-allocation-mode command in VRF configuration
mode. To remove the label-allocation-mode command from the configuration file and restore the system
to its default condition, use the no form of this command.
label-allocation-mode [{per-ce }]
no label-allocation-mode
Syntax Description per-ce Specifies that the same label is used for all the routes advertised from a unique customer edge (CE)
peer or router.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Each prefix that belongs to a VRF instance is advertised with a single label, causing an additional lookup to
be performed in the VRF forwarding table to determine the customer edge (CE) next hop for the packet. Use
the label-allocation-mode command with the per-ce keyword to avoid the additional lookup on the PE
router and conserve label space. This mode allows the PE router to allocate one label for every immediate
next hop. The label is directly mapped to the next hop so there is no VRF route lookup performed during data
forwarding. However, the number of labels allocated is one for each CE rather than one for each prefix.
Note • The label-allocation-mode under the global IPv6 address family configuration mode is renamed as label
mode, in Cisco IOS-XR Software release 4.3.1 and later releases.
• With the introduction of label mode command, the nexthop labels will no longer be released, when
label-allocation-mode command with the per-ce keyword is unconfigured.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
180
BGP Commands
label-allocation-mode
Examples The following example shows how to set the label allocation mode to customer edge:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
181
BGP Commands
label mode
label mode
To set the MPLS/VPN label mode based on prefix value, use the label mode command in an appropriate
configuration mode. To remove the label mode command from the configuration file and restore the system
to its default condition, use the no form of this command.
Use this syntax for vrf all configuration mode under VPN IPv4/IPv6 AF (address family) mode or global
IPv6 AF configuration mode:
Syntax Description per-ce Specifies that the same label is used for all routes advertised from a unique customer edge
(CE) peer or route.
per-vrf Specifies that the same label is used for all routes advertised from a unique VRF.
per-prefix Specifies that the same label is used for all routes advertised from a unique prefix.
Note This keyword is applicable only for IPv4/IPv6 AF configuration mode under vrf
mode.
route-policy Specifies a route policy to select prefixes for setting the label mode.
Note If a policy attached at label-mode attachpoint evaluates to pass and a label mode is not explicitly set, per-prefix
is used as the default label mode.
If a policy attached at label-mode attachpoint evaluates to a drop, per-prefix is used as a default label mode.
If any label mode is set explicitly in this case, it will be ignored.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
182
BGP Commands
label mode
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
To configure label mode at VPN-AF level and to have all the VRF AFs inherit that configuration, you must
use vrf all, which is available under VPN-AF mode.
The inheritance rules followed are:
• label mode configuration under VRF-AF, overrides label-allocation-mode configuration under VRF
and label mode configuration under VPN-AF.
• label-allocation-mode configuration under VRF, overrides label mode configuration under VPN-AF.
• The order of priority to determine the label mode in the configurations is:
1. VRF-AF: label mode
2. VRF: label-allocation-mode
3. VPN-AF: label mode
4. N/A: per-prefix
Note Even if label mode is in use, per-vrf label is allocated for connected, aggregate, and local prefixes.
The example shows how to configure label mode selection at VPNv4 AF level:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# vrf all
RP/0/RSP0/CPU0:router(config-bgp-af)# label mode route-policy policy_A
The example shows how to configure label mode selection at VRF IPv4 AF level:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 109
RP/0/RSP0/CPU0:router(config-bgp)# vrf vrf-1
RP/0/RSP0/CPU0:router(config-bgp-vrf)# rd 1:1
RP/0/RSP0/CPU0:router(config-bgp-vrf)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-vrf)# label mode route-policy policy_B
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
183
BGP Commands
local-as
local-as
To allow customization of the autonomous system number for external Border Gateway Protocol (eBGP)
neighbor peerings, use the local-as command in an appropriate configuration mode. To disable customization
of local autonomous system values for eBGP neighbor peerings, use the no form of this command.
no-prepend (Optional) Specifies that local autonomous system values are not prepended to
announcements from the neighbor.
replace-as (Optional) Specifies that prepend only local autonomous system values to
announcements to the neighbor.
Command Default The BGP autonomous system number specified in the router bgp command is used, except when
confederations are in use. The confederation autonomous system is used for external neighbors in an autonomous
system that is not part of the confederation.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The dual-as
keyword was added. The disable keyword was replaced with the inheritance-disable
keyword.
Release 5.2.2 Support was added to specify the same autonomous system number for local-as and
remote-as commands.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
184
BGP Commands
local-as
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You can specify the autonomous system number the local BGP uses to peer with each neighbor. The autonomous
system number specified with this command cannot be the local BGP autonomous system number (specified
with the router bgp command) or the autonomous system number of the neighbor (specified with the
remote-as command). However, from Release 5.2.2, the autonomous system number for local-as and
remote-as can be the same, which makes the resulting neighbor peering being treated as iBGP. This command
cannot be specified for internal neighbors or for external neighbors in an autonomous system that is part of a
confederation.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit
the configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Examples The following example shows BGP using autonomous system 30 for the purpose of peering with
neighbor 172.20.1.1:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
185
BGP Commands
long-lived-graceful-restart
long-lived-graceful-restart
To enable long lived graceful restart (LLGR) on the BGP neighbors, use the long-lived-graceful-restart
command in neighbor VPN address family mode. To disable LLGR, use the no form of this command.
Syntax Description capable Treats the neighbor as LLGR capable even if it does not advertise the capabilities.
stale-time Causes the local router to advertise the LLGR capability to the neighbor and to enable LLGR
for prefixes received from the neighbor.
Usage Guidelines When this command is configured, the BGP session is reset, because the changes need to be advertised to the
neighbor in a BGP OPEN message.
When the BGP session to a neighbor goes down the routes received from it will be marked LLGR stale if all
of the following conditions are met:
• Either the neighbor is configured as capable or the neighbor sent the LLGR capability in its BGP OPEN
message
• The accept time is not configured to be 0.
• The stale time that the neighbor sent in the LLGR capability in its BGP OPEN message is not 0.
• The neighbor session was not brought down with a clear command on the local router.
• The neighbor sent either the LLGR or graceful restart capability in its BGP OPEN message.
LLGR routes will only be advertised to a neighbor that is LLGR capable, either because it is configured as
capable or because it has sent the LLGR capability in its BGP OPEN message. An LLGR route is either one
that has been marked as LLGR stale, because the BGP session from which it was received went down or
because it has the LLGR_STALE community and does not have the NO_LLGR community.
bgp read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
186
BGP Commands
long-lived-graceful-restart
Examples This example shows how to configure the neighbor to be LLGR capable for the given address family:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 3.3.3.3
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# long-lived-graceful-restart capable
The long-lived-graceful-restart capable command enables the LLGR capability on the neighbor;
even though the neighbor does not advertise the LLGR capabilities during session information.
The following example shows how to advertise :
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 3.3.3.3
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# long-lived-graceful-restart stale-time send 20
accept 30
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
187
BGP Commands
lpts punt excessive-flow-trap routing-protocols-enable
Usage Guidelines You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
When subscriber interface or interface-based-flow is configured, you can not configure the
routing-protocol-enable command. The reverse of this also holds good, that is, if the routing-protocol-enable
command is configured, you cannot configure a subscriber interface or interface-based-flow.
L3 routing-protocols to be enabled on non-subscriber interfaces mac.
Note The routing-protocols-enable command can be configured only after configuring non-subscriber-interface
mac.
lpts read
basic-services read-write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
188
BGP Commands
lpts punt excessive-flow-trap penalty-timeout bgp
Syntax Description timeout The penalty timeout value for the bgp protocol in minutes. It is the period of time at which bgp
bad flow remains to be in bad actor state.
Value ranges from 1 to 1000.
Usage Guidelines You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
If the penalty-timeout value for bgp is configured as 20, then bgp packets are dropped for 20 minutes.
lpts read
basic-services read-write
Examples This example shows to set penalty time out for bgp bad actor:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
189
BGP Commands
match flow-tag
match flow-tag
To identify specific flow-tag values as match criteria in a class-map, use the match flow-tag command in
class-map configuration mode. To remove a specific flow tag value from the matching criteria for a class-map,
use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
190
BGP Commands
match flow-tag
No local label
IP Precedence: Not Set
QoS Group ID: Not Set
Flow-tag: 220
Route Priority: RIB_PRIORITY_RECURSIVE (12) SVD Type
RIB_SVD_TYPE_LOCAL
Download Priority 4, Download Version 7
No advertising protos.
RP/0/0/CPU0:ios-xr#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
191
BGP Commands
maximum-paths (BGP)
maximum-paths (BGP)
To control the maximum number of parallel routes that Border Gateway Protocol (BGP) installs in the routing
table, use the maximum-paths command in an appropriate configuration mode. To set the maximum number
of parallel routes the software installs to the default value, use the no form of this command.
eibgp Specifies internal and external BGP multipath peers. eiBGP allows simultaneous use of
internal and external paths.
maximum Maximum number of parallel routes that BGP installs in the routing table. Range is 2 to 64.
unequal-cost (Optional) Allows iBGP multipaths to have different BGP next-hop Interior Gateway Protocol
(IGP) metrics. This option is available when the ibgp keyword is used.
selective (Optional) Allows BGP to be configured such that only routes from selected neighbors can
be considered for multipath. This option is used with the multipath option.
Note Under non-default VRF address-family, maximum number of paths allowed is 32 only.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum-paths command to allow the BGP to allow the BGP protocol to install multiple paths into
the routing table for each prefix. With the eBGP option, multiple paths are installed for external peers that
are from the same autonomous system and are equal cost (according to the BGP best-path algorithm). Similarly
with the iBGP option, multiple paths are installed for internal peers that are equal cost based on the BGP
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
192
BGP Commands
maximum-paths (BGP)
best-path algorithm. With the eiBGP option, multiple paths from both iBGP and eBGP are eligible for multipath
selection. The IGP metric to the BGP next hop is the same as the best-path IGP metric unless the router is
configured for unequal cost iBGP multipath or eiBGP multipath. The selective option restricts multipath
eligible routes to those that come from peers configured with the multipath option.
See Implementing BGP in the Routing Configuration Guide for Cisco ASR 9000 Series Routers for information
on the BGP best-path algorithm.
Note The maximum-paths command with the eibgp keyword cannot be configured if the ibgp or ebgp
keywords have been configured, because the eibgp keyword is a super set of the ibgp or ebgp keywords.
bgp read,
write
Examples The following example shows how to allow a maximum of four paths to a destination to be installed
into the IPv4 unicast routing table:
The following example shows how you can configure selective multipath for iBGP and eBGP peers.
Note This configuration requires the multipath option to be configured for the neighbors. See the multipath
command in the Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference
Guide for more information.
For information on how this configuration is used, see the BGP Selective Multipath section in the
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
193
BGP Commands
maximum-prefix (BGP)
maximum-prefix (BGP)
To control how many prefixes can be received from a neighbor, use the maximum-prefix command in an
appropriate configuration mode. To set the prefix limits to the default values, use the no form of this command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
194
BGP Commands
maximum-prefix (BGP)
Command Default When this command is not specified, the following defaults apply:
• IPv4 Unicast: 1048576
• IPv4 Labeled-unicast: 131072
• IPv6 Unicast: 524288
• IPv6 Labeled-unicast: 131072
• IPv4 Tunnel: 1048576
• IPv4 Multicast: 131072
• IPv6 Multicast: 131072
• IPv4 MVPN: 2097152
• VPNv4 Unicast: 2097152
• IPv4 MDT: 131072
• VPNv6 Unicast: 1048576
• L2VPN EVPN: 2097152
• IPv4 Flowspec: 1048576
• IPv6 Flowspec: 524288
• VPNv4 Flowspec: 2097152
• VPNv6 Flowspec: 1048576
Command Modes IPv4 address family group, neighbor address family, and neighbor group address family configuration
IPv6 address family group, neighbor address family, and neighbor group address family configuration
IPv4 tunnel address family group, neighbor group address family, and neighbor address family configuration
IPv4 flowspec under neighbor address family, neighbor group address family, and address family group
configuration
IPv6 flowspec under neighbor address family, neighbor group address family, and address family group
configuration
VPNv4 flowspec under neighbor address family, neighbor group address family, and address family group
configuration
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
195
BGP Commands
maximum-prefix (BGP)
VPNv6 flowspec under neighbor address family, neighbor group address family, and address family group
configuration
L2VPN EVPN under neighbor address family, neighbor group address family, and address family group
configuration
Release 4.2.1 The default prefix limit was increased for IPv4 unicast, IPv6 unicast, VPNv4 unicast, and
VPNv6 unicast address families as:
• IPv4 unicast: 1048576
• IPv6 unicast: 524288
• VPNv4 unicast: 2097152
Usage Guidelines Use the maximum-prefix command to configure a maximum number of prefixes that a BGP router is allowed
to receive from a neighbor. It adds another mechanism (besides routing policy) to control prefixes received
from a peer.
When the number of received prefixes exceeds the maximum number configured, the software terminates the
peering, by default, after sending a cease notification to the neighbor. However, if the warning-only keyword
is configured, the software writes only a log message, but continues peering with the sender. If the peer is
terminated, the peer stays down until the clear bgp command is issued or the restart time-interval option
is used.
This command takes effect immediately if configured on an established neighbor, unless the number of prefixes
received from the neighbor already exceeds the configured limits.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the
group inherit the configuration. Values of commands configured specifically for a neighbor override inherited
values.
bgp read,
write
Examples This example shows the maximum number of IP Version 6 (IPv6) unicast prefixes allowed from
neighbor 192.168.40.25 set to 5000, threshold value 80%, and restart time interval 20 minutes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
196
BGP Commands
maximum-prefix (BGP)
This example shows the maximum number of IP Version 4 (IPv4) unicast prefixes allowed from the
neighbor 192.168.40.24 set to 1000:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 10
RP/0/RSP0/CPU0:router(config-bgp)#neighbor 10.0.0.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)#maximum-prefix 5000 discard-extra-paths
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
clear bgp, on page 118 Resets a BGP connection using BGP hard or soft reconfiguration.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
197
BGP Commands
mpls activate (BGP)
Neighbor configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Thempls activate command enables MPLS on the interface specified and also adds the implicit null rewrite
corresponding to the peer associated with the interface. The interface specified must be the one corresponding
to the inter-AS ASBR or CSC peer.
bgp read,
write
Examples The following example shows how to activate MPLS for InterAS Option B (with confederations):
RP/0/RSP0/CPU0:router(config)#router bgp 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
198
BGP Commands
mpls activate (BGP)
2002
mpls activate
interface GigabitEthernet0/1/0/0
redistribute connected
neighbor 10.0.0.9
remote-as 2002
route-policy pass in
route-policy pass in
The following example shows how to activate MPLS for CSC (with confederations):
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
199
BGP Commands
mpls activate (BGP)
address-family (BGP), on page 16 Enters address family configuration mode for configuring BGP routing
sessions.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
200
BGP Commands
mvpn
mvpn
To enable BGP instance to connect to PIM/PIM6, use the mvpn command in router configuration mode. To
disable BGP instance -PIM/PIM6 connection, use the no form of this command.
mvpn
no mvpn
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure mvpn and enable PIM/PIM6 connection:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#mvpn
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
201
BGP Commands
multipath
multipath
Enables multiple paths for a BGP neighbor.
To disable this function, use the no form of this command.
multipath
no multipath
Usage Guidelines To configure BGP selective multipath feature, the multipath option must be enabled on the required BGP
neighbor. The multipath configuration for a neighbor works when configured with the selective option of
the maximum-paths command.
BGP read,
write
Examples The following example shows how to enable multiple paths for a BGP neighbor.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# maximum-paths ibgp 4 selective
RP/0/RSP0/CPU0:router(config-bgp-af)# maximum-paths ebgp 5 selective
RP/0/RSP0/CPU0:router(config-bgp-af)# neighbor 1.1.1.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# multipath
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# commit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
202
BGP Commands
neighbor (BGP)
neighbor (BGP)
To enter neighbor configuration mode for configuring Border Gateway Protocol (BGP) routing sessions, use
the neighbor command in an appropriate configuration mode. To delete all configuration for a neighbor and
terminate peering sessions with the neighbor, use the no form of this command.
neighbor ip-address
no neighbor ip-address
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
From router configuration mode, you can use this command to enter neighbor configuration mode.
From neighbor configuration mode, you can enter address family configuration for the neighbor by using the
address-family command, which allows you to configure routing sessions for IP Version 4 and IP Version
6 address prefixes.
The neighbor command does not cause the neighbor to be configured and does not result in a peering to be
established with the neighbor. To create the neighbor, you configure a remote autonomous system number
by entering the remote-as command, or the neighbor can inherit a remote autonomous system from a neighbor
group or session group if the use command is applied.
Note A neighbor must have must a remote autonomous system number, and an IP address and address family must
be enabled on the neighbor.
Unlike IPv4, IPv6 must be enabled before any IPv6 neighbors can be defined. Enable IPv6 in router
configuration mode using the address-family command.
Note Configuration for the neighbor cannot occur (peering is not established) until the neighbor is given a remote
as-number and neighbor address.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
203
BGP Commands
neighbor (BGP)
The no form of this command causes the peering with the neighbor to be terminated and all configuration
that relates to the neighbor to be removed.
bgp read,
write
Examples The following example shows how to place the router in neighbor configuration mode for BGP
routing process 1 and configure the neighbor IP address 172.168.40.24 as a BGP peer:
The following example shows how to enable IPv6 for BGP, then place the router in neighbor
configuration mode for an IPv6 neighbor, 3000::1, and configure neighbor 3000::1 as a BGP peer:
address-family (BGP), on page 16 Enters address family configuration mode for configuring BGP routing
sessions.
remote-as (BGP), on page 248 Adds an entry to the BGP neighbor table.
use, on page 524 Inherits characteristics from a neighbor group, session group, or address
family group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
204
BGP Commands
neighbor-group
neighbor-group
To create a neighbor group and enter neighbor group configuration mode, use the neighbor-group command
in router configuration mode. To remove a neighbor group and delete all configuration associated with the
group, use the no form of this command.
neighbor-group name
no neighbor-group name
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The neighbor-group command puts the router in neighbor group configuration mode and creates a neighbor
group.
A neighbor group helps you apply the same configuration to one or more neighbors. After a neighbor group
is configured, each neighbor can inherit the configuration through the use command. If a neighbor is configured
to use a neighbor group, the neighbor, by default, inherits the entire configuration of the neighbor group,
which includes the address family-independent and address family-specific configurations. The inherited
configuration can be overridden if you directly configure commands for the neighbor or if you configure
session groups or address family groups with the use command.
From neighbor group configuration mode, you can configure address family-independent parameters for the
neighbor group. To enter address family-specific configuration for the neighbor group, use the address-family
command when in the neighbor group configuration mode.
Note If an address family is configured for a neighbor group, neighbors that use the neighbor group attempt to
exchange routes in that address family.
The no form of this command ordinarily causes all configuration for the neighbor group to be removed. If
using the no form would result in a neighbor losing its remote autonomous system number, the configuration
is rejected. In this scenario, the neighbor configuration must be either removed or configured with a remote
autonomous system number before the neighbor group configuration can be removed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
205
BGP Commands
neighbor-group
Note Neighbor groups should not be configured with a mixture of IPv4 and IPv6 address families, because such a
neighbor group is not usable by any neighbor. Note that within the Cisco IOS XR system configuration
architecture, it is possible to create such a neighbor group; however, any attempt to use it is rejected.
bgp read,
write
Examples The following example shows how to create a neighbor group called group1 that has IP Version 4
(IPv4) unicast and IPv4 multicast activated along with various configuration features. The neighbor
group is used by neighbor 10.0.0.1 and neighbor 10.0.0.2, which allows them to inherit the entire
group1 configuration.
address-family (BGP), on page 16 Enters various address family configuration modes for configuring BGP
routing sessions.
neighbor (BGP), on page 203 Enters neighbor configuration mode for configuring BGP routing
sessions.
use, on page 524 Inherits characteristics from a neighbor group, a session group, or an
address family group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
206
BGP Commands
neighbor internal-vpn-client
neighbor internal-vpn-client
To preserve the iBGP-CE (customer edge) attributes inside the VPN attribute set (ATTR-SET) and send it
across to the core, use the neighbor internal-vpn-client command in the VRF neighbor configuration mode.
To disable the command, use the no form of this command.
internal-vpn-client Stacks the iBGP-CE neighbor path in the VPN attribute set.
Usage Guidelines The neighbor ip-address internal-vpn-client command enables PE devices to make the entire VPN cloud
act as an internal VPN client to the CE devices connected internally. This command is used so that existing
internal BGP VRF lite scenarios are not affected. You need not configure autonomous system override for
CE devices after enabling this command.
bgp read,
write
Examples The following example shows how to configure L3VPN iBGP PE-CE:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# vrf blue neighbor 10.10.10.1
RP/0/RSP0/CPU0:router(config-bgp-vrf-nbr)# internal-vpn-client
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
207
BGP Commands
network (BGP)
network (BGP)
To specify that the Border Gateway Protocol (BGP) routing process should originate and advertise a locally
known network to its neighbors, use the network command in an appropriate configuration mode. To disable
originating or advertising the network to neighbors, use the no form of this command.
/ prefix-length Length of the IP address prefix. A decimal value that indicates how many
of the high-order contiguous bits of the address compose the prefix (the
network portion of the address). A slash (/) must precede the decimal
value.
route-policy route-policy-name (Optional) Specifies a route policy to use to modify the attributes of the
network.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
A network specified with this command is originated and advertised to neighbors only if there exists a route
for the network in the routing table. That is, there must be a route learned using local or connected networks,
static routing, or a dynamic IGP such as IS-IS or OSPF.
Other than the available system resources on the router, no limit exists on the number of network commands
that can be configured.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
208
BGP Commands
network (BGP)
Examples The following example shows how to configure the local router to originate the IPv4 unicast network
172.20.0.0/16:
network backdoor, on page 210 Specifies a backdoor route to a BGP border router that provides better
information about the network.
redistribute (BGP), on page 242 Redistributes routes from one routing domain into another routing domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
209
BGP Commands
network backdoor
network backdoor
To set the administrative distance on an external Border Gateway Protocol (eBGP) route to that of a locally
sourced BGP route, causing it to be less preferred than an Interior Gateway Protocol (IGP) route, use the
network backdoor command in an appropriate configuration mode. To disable setting the administrative
distance to the value for locally sourced BGP routes, use the no form of this command.
/ prefix-length Length of the IP address prefix. A decimal value that indicates how many of the high-order
contiguous bits of the address compose the prefix (the network portion of the address). A
slash (/) must precede the decimal value.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Configuring the network backdoor command does not cause BGP to originate a network, even if an IGP
route for the network exists. Ordinarily, the backdoor network would be learned through both an eBGP and
IGP. The BGP best-path selection algorithm does not change when a network is configured as a backdoor
network.
bgp read,
write
Examples The following example shows IP Version 4 (IPv4) unicast network 192.168.40.0/24 configured as
a backdoor network:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
210
BGP Commands
network backdoor
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate and
advertise to its neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
211
BGP Commands
next-hop-self
next-hop-self
To disable next-hop calculation and insert your own address in the next-hop field of Border Gateway Protocol
(BGP) updates, use the next-hop-self command in an appropriate configuration mode. To enable next-hop
calculation, use the no form of this command.
next-hop-self [{inheritance-disable}]
no next-hop-self [{inheritance-disable}]
Syntax Description inheritance-disable (Optional) Allows a next-hop calculation override when this feature may be inherited
from a neighbor group or address family group.
Command Default When this command is not specified, the software calculates the next hop for BGP updates accepted by the
router.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Release 4.0 This command was supported in the following address family configuration modes:
• IPv4 labeled-unicast
• IPv6 labeled-unicast
• VRF labeled-unicast
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
212
BGP Commands
next-hop-self
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the next-hop-self command to set the BGP next-hop attribute of routes being advertised over a peering
session to the local source address of the session.
This command is useful in nonmeshed networks in which BGP neighbors may not have direct access to all
other neighbors on the same IP subnet.
If this command is configured for a neighbor group or address family group, a neighbor using the group
inherits the configuration. Configuring the command specifically for a neighbor overrides any inherited value.
Configuring the next-hop-self command under IPv4 labeled-unicast, IPv6 labeled-unicast, or VRF
labeled-unicast address family configuration mode enables next-hop-self for labeled prefixes advertised to an
iBGP peer.
bgp read,
write
Examples The following example shows how to set the next hop of the update field for all IP Version 4 (IPv4)
unicast routes advertised to neighbor 172.20.1.1 to an address of the local router:
The following example shows how to disable the next-hop-self command for neighbor 172.20.1.1.
If not overridden, the next hop would be inherited from address family group group1:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
213
BGP Commands
next-hop-self
Command Description
use, on page 524 Inherits characteristics from a neighbor group, session group, or address family
group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
214
BGP Commands
next-hop-unchanged
next-hop-unchanged
To disable overwriting of the next hop before advertising to external Border Gateway Protocol (eBGP) peers,
use the next-hop-unchanged command in an appropriate configuration mode. To enable overwriting of the
next hop, use the no form of this command.
Syntax Description inheritance-disable (Optional) Allows overwriting of the next hop before advertising to eBGP peers when
this feature may be inherited from a neighbor group or address family group.
multipath (Optional) Disables overwriting of next-hop calculation for multipath prefixes learned
from eBGP neighbors and advertised to iBGP neighbors.
Note The multipath keyword is supported only for IPv4 and IPv6 unicast address
families. It is not supported with labeled-unicast or VPN address families.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Release 4.0.0 This command was supported in the following address family configuration modes:
• IPv4 labeled-unicast address family configuration
• IPv6 labeled-unicast address family configuration
• IPv4 unicast address family configuration
• IPv6 unicast address family configuration
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
215
BGP Commands
next-hop-unchanged
Usage Guidelines Use the next-hop-unchanged command to propagate the next hop unchanged for multihop eBGP peering
sessions. This command should not be configured on a route reflector, and the next-hop-self command
should not be used to modify the next-hop attribute for a route reflector when this feature is enabled for a
route reflector client.
Note Incorrectly setting BGP attributes for a route reflector can cause inconsistent routing, routing loops, or a loss
of connectivity. Setting BGP attributes for a route reflector should be attempted only by an experienced
network operator.
Use the next-hop-unchanged multipath command to set the next-hop to the eBGP peer egress interface
when configuring eBGP multipath.
bgp read,
write
Examples The following example shows how to disable the overwriting of next hops before advertising to
eBGP peers:
The following example shows how to disable the overwriting of next hops for multipath prefixes:
next-hop-self, on page 212 Disables next-hop calculation and allows you to insert your own address in the
next-hop field of BGP updates.
use, on page 524 Inherits characteristics from a neighbor group, session group, or address family
group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
216
BGP Commands
nexthop resolution prefix-length minimum
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set the minimum prefix-length for nexthop resolution as 32:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#nexthop resolution prefix-length minimum 32
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
217
BGP Commands
nexthop route-policy
nexthop route-policy
To specify that BGP routes are resolved using only next hops whose routes match specific characteristics,
use the nexthop route-policy command in the appropriate configuration mode. To remove the nexthop
route-policy command from the configuration file and restore the system to its default behavior, use the no
form of this command.
Syntax Description route-policy-name Route policy to use for filtering based on next hops.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the nexthop route-policy command to configure route policy filtering using next hops.
The BGP next-hop tracking feature allows you to specify that BGP routes are resolved using only next hops
whose routes have the following characteristics:
• To avoid the aggregate routes, the prefix length must be greater than a specified value.
• The source protocol must be from a selected list, ensuring that BGP routes are not used to resolve next
hops that could lead to oscillation.
This route policy filtering is possible because RIB identifies the source protocol of a route that resolves a next
hop as well as the mask length associated with the route.
The next-hop attach point supports matching using the protocol name and mask length. BGP marks all next
hops that are rejected by the route policy as invalid, and no best path is calculated for the routes that use the
invalid next hop. The invalid next hops continue to stay in the active cache and can be displayed as part of
the show bgp nexthop command with an invalid status.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
218
BGP Commands
nexthop route-policy
Examples The following example shows how to specify the route policy nexthop_A as the policy to use for
filtering next hops:
route-policy (RPL) Defines a route policy and enters route-policy configuration mode.
show bgp nexthops, on page 393 Display statistical information about the BGP next hops.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
219
BGP Commands
nexthop trigger-delay
nexthop trigger-delay
To specify the delay for triggering next-hop calculations, use the nexthop trigger-delay command in the
appropriate configuration mode. To set the trigger delay to the default value, use the no form of this command.
Syntax Description critical Specifies critical next-hop events. For example, when the next hop is unreachable.
non-critical Specifies noncritical next-hop events. For example, Interior Gateway Protocol (IGP) metric
changes.
Command Default critical : 3000 msec for IPv4 address family and IPv6 address family
critical: 0 msec for VPNv4 address family and VPNv6 address family
non-critical: 10000 msec IPv4, IPv6, VPNv4, and VPNv6 address families
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the nexthop trigger-delay command to allow for a dynamic way for Interior Gateway Protocol (IGP)
to converge. This convergence allows BGP to accumulate all notifications and trigger fewer walks, resulting
in fewer interprocess communications (IPCs) to the Routing Information Base (RIB) for route addition,
deletion, and modification and fewer updates to peers.
Note A high delay value can be configured to effectively turn off next-hop tracking.
The non-critical delay value must always be set to at least equal or greater than the critical delay value
.
The delay should be slightly higher than the time it takes for the IGP to settle into a steady state after some
event (IGP convergence time).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
220
BGP Commands
nexthop trigger-delay
bgp read,
write
Examples The following example shows how to set the critical next-hop trigger delay to 3500 milliseconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
221
BGP Commands
nsr (BGP)
nsr (BGP)
To activate Border Gateway Protocol (BGP) nonstop routing (NSR), use the nsr command in BGP global
configuration mode. To deactivate BGP NSR, use the noform of this command.
nsr
no nsr
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the nsr command to enable the Border Gateway Protocol (BGP) Nonstop Routing (NSR) with Stateful
Switchover (SSO). This enables all bgp peerings to maintain the BGP state to ensure continuous packet
forwarding during events that could interrupt service.
bgp read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 120
RP/0/RSP0/CPU0:router(config-bgp)# nsr
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
222
BGP Commands
nsr (BGP)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 120
RP/0/RSP0/CPU0:router(config-bgp)# no nsr
router bgp, on page 263 Configures the Border Gateway Protocol (BGP) routing process.
nsr process-failures switchover Configures failover as a recovery action in case of process failures for active
instances to switch over to a standby route processor (RP) or a standby
distributed route processor (DRP) to maintain nonstop routing (NSR).
show bgp nsr, on page 402 Displays Border Gateway Protocol (BGP) nonstop routing (NSR)
information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
223
BGP Commands
nsr disable (BGP)
nsr disable
no nsr disable
Usage Guidelines Use the nsr disable command to disable Border Gateway Protocol (BGP) Nonstop Routing (NSR) with
Stateful Switchover (SSO). Using the no form of this command enables all BGP peerings to maintain the
BGP state to ensure continuous packet forwarding during events that could interrupt service.
Note In releases prior to R 5.2.3, NSR is disabled by default, and must be configured manually.
bgp read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 120
RP/0/RSP0/CPU0:router(config-bgp)# nsr disable
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 120
RP/0/RSP0/CPU0:router(config-bgp)# no nsr disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
224
BGP Commands
nsr disable (BGP)
router bgp, on page 263 Configures the Border Gateway Protocol (BGP) routing process.
nsr process-failures switchover Configures failover as a recovery action in case of process failures for active
instances to switch over to a standby route processor (RP) or a standby
distributed route processor (DRP) to maintain nonstop routing (NSR).
show bgp nsr, on page 402 Displays Border Gateway Protocol (BGP) nonstop routing (NSR)
information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
225
BGP Commands
orf
orf
To specify Outbound Route Filter (ORF) and inbound filtering criteria, use the orf route-policy command
in an appropriate configuration mode. To restore the system to its default condition, use the no form of this
command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to configure outbound and inbound filtering criteria:
RP/0/RSP0/CPU0:router(config)#router bgp 6
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 172.20.1.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# remote-as 1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)#orf route-policy policy_A
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
226
BGP Commands
orf
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
227
BGP Commands
password (BGP)
password (BGP)
To enable Message Digest 5 (MD5) authentication on a TCP connection between two Border Gateway Protocol
(BGP) neighbors, use the password command in an appropriate configuration mode. To disable MD5
authentication, use the no form of this command.
Syntax Description clear Specifies that an unencrypted password follows. The password must be a case-sensitive, clear-text
unencrypted password.
encrypted Specifies that an encrypted password follows. The password must be a case-sensitive, encrypted
password.
password Password of up to 80 characters. The password can contain any alphanumeric characters.
However, if the first character is a number or the password contains a space, the password must
be enclosed in double quotation marks; for example, “2 password.”
Command Default When this command is not specified in the appropriate configuration mode, MD5 authentication is not enabled
on a TCP connection between two BGP neighbors.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Configure a password to enable authentication between two BGP peers. Use the password command to
verify each segment sent on the TCP connection between the peers. The same password must be configured
on both networking devices, otherwise a connection cannot be made. The authentication feature uses the MD5
algorithm. Specifying this command causes the software to generate and check the MD5 digest on every
segment sent on the TCP connection.
Configuring a neighbor password does not cause the existing session for a neighbor to end. However, until
the new password is configured on the remote router, the local BGP process does not receive keepalive
messages from the remote device. If the password is not updated on the remote device by the end of the hold
time, the session ends. The hold time can be changed using the timers command or the timers bgp command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
228
BGP Commands
password (BGP)
If this command is configured for a neighbor group or neighbor address family group, a neighbor using the
group inherits the configuration. Values of commands configured specifically for a neighbor overrides inherited
values.
bgp read,
write
Examples The following example shows how to configure neighbor 172.20.1.1 to use MD5 authentication with
the password password1:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
password-disable, on page 231 Overrides any inherited password configuration from a neighbor group or
session group for BGP neighbors.
session-group, on page 276 Creates a session group and enters session group configuration mode.
timers (BGP), on page 504 Set the timers for a specific BGP neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
229
BGP Commands
password (rpki-server)
password (rpki-server)
To specify a SSH password for the RPKI cache-server, use the password command in rpki-server configuration
mode. To remove the SSH passwords, use the no form of this command.
password password
no password password
Syntax Description password Enters a password to be used for the SSH transport mechanism.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
SSH expects to use an authentication method to connect to a remote server. The SSH authentication method
to connect to RPKI server is password-based. So, the RPKI cache-server must be configured with username
and password. A username and password must be configure for each server configured under BGP that uses
the SSH transport
This example shows how to configure a username (rpki-user) and password (rpki-ssh-pass) for the
RPKI cache-server SSH transport mechanism:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#username rpki-user
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#password rpki-ssh-pass
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
230
BGP Commands
password-disable
password-disable
To override any inherited password configuration from a neighbor group or session group for Border Gateway
Protocol (BGP) neighbors, use the password-disable command in an appropriate configuration mode. To
disable overriding any inherited password command, use the no form of this command.
password-disable
no password-disable
Command Default Configured passwords for neighbor and session groups are inherited.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you specify a password on a neighbor group or session group, all users of the group inherit the password.
Specifying a different password command specifically on a neighbor that uses the group overrides the
inherited value. Specifying password-disable on a neighbor that uses the group disables password
authentication for the neighbor.
bgp read,
write
Examples The following example shows how to disable MD5 authentication for neighbor 172.20.1.1, preventing
it from inheriting the password password1 from session group group1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
231
BGP Commands
password-disable
RP/0/RSP0/CPU0:router(config-bgp-nbr)# password-disable
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
password (BGP), on page 228 Enables MD5 authentication on a TCP connection between two BGP
neighbors.
session-group, on page 276 Creates a session group and enters session group configuration mode.
use, on page 524 Inherits characteristics from a neighbor group, a session group, or an address
family group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
232
BGP Commands
permanent-network
permanent-network
To define a prefix set as permanent, use the permanent-network command in the global address family
configuration mode. To remove a prefix set as permanent, use the no form of this command. The
permanent-network command uses a route-policy to identify the set of prefixes (networks) for which
permanent paths needs to be created.
The permanent network feature supports only prefixes in IPv4 unicast and IPv6 unicast address-families under
the default Virtual Routing and Forwarding (VRF).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples This example shows how to define permanent path for a route policy named
POLICY-PERMANENT-NETWORK-IPv4:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-af)# permanent-network route-policy POLICY-PERMANENT-NETWORK-IPv4
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
233
BGP Commands
precedence
precedence
To set the precedence level, use the precedence command in the appropriate configuration mode. To remove
the precedence command from the configuration file and restore the system to its default interval values,
use the no form of this command.
precedence value
no precedence [value]
Syntax Description value Value of the precedence. The precedence value can be a number from 0 to 7, or it can be one of the
following keywords:
critical —Set packets with critical precedence (5)
flash — Set packets with flash precedence (3)
flash-override —Set packets with flash override precedence (4)
immediate —Set packets with immediate precedence (2)
internet —Set packets with internetwork control precedence (6)
network —Set packets with network control precedence (7)
priority —Set packets with priority precedence (1)
routine —Set packets with routine precedence (0)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the precedence command to set the precedence value.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
234
BGP Commands
precedence
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
235
BGP Commands
preference (rpki-server)
preference (rpki-server)
To specify a preference value for the RPKI cache-server, use the preference command rpki-server configuration
mode. To remove the preference value, use the no form of this command.
preference preference-value
no preference preference-value
Syntax Description preference-value Specifies a RPKI cache preference value. Range is 1 to 10.
Note A lower value is recommended
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set preference value for RPKI configuration as 1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-cache)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-cache)#username rpki-user
RP/0/RSP0/CPU0:router(config-bgp-rpki-cache)#password rpki-ssh-pass
RP/0/RSP0/CPU0:router(config-bgp-rpki-cache)#preference 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
236
BGP Commands
purge-time (rpki-server)
purge-time (rpki-server)
To configure the time BGP waits to keep routes from RPKI cache-server after the cache session drops, use
the purge-time command in rpki-server configuration mode. To remove the purge-time configuration, use
the no form of this command.
purge-time time-in-seconds
no purge-time time-in-seconds
Syntax Description time-in-seconds Sets the purge time in seconds. Range is 30 to 360 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When a cache session is dropped then a "purge-timer" is started for that cache. If the session re-establishes
within the timer interval, then the purge timer is stopped and no further action is taken. If the cache session
does not re-establish within the timer interval, only then does BGP remove all ROAs from the cache.
This example shows how to set the purge-time for RPKI cache as 30 seconds:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#username rpki-user
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#password rpki-ssh-pass
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#preference 1
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#purge-time 30
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
237
BGP Commands
rd
rd
To configure a route distinguisher, use the rd command in VRF configuration mode. To disable the route
distinguisher, use the no form of this command.
Syntax Description as-number:nn • as-number —16-bit Autonomous system (AS) number of the route distinguisher
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
• nn —32-bit number
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the rd command to make the prefix unique across multiple VRFs.
Auto assignment of route distinguishers can be done only if a router ID is assigned using the bgp router-id
command in BGP router configuration mode. The unique router ID is used for automatic route distinguisher
generation.
The following are restrictions when configuring route distinguishers:
• BGP router-id must be configured before rd auto can be configured
• Route distinguisher cannot be changed or removed when an IPv4 unicast address family is configured
under VRF.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
238
BGP Commands
rd
• BGP router-id cannot be changed or removed when rd auto is configured under a VRF.
• When rd auto is configured under a VRF, the IP address for the router distinguisher configured under
another VRF must be different from that of the BGP router-id
• If a route distinguisher with same IP address as BGP router-id exists, the rd auto is not permitted.
bgp read,
write
Examples The following example shows how to automatically assign a unique route distinguisher to VRF
instance vrf-1:
bgp router-id, on page 100 Configures a fixed router ID for a BGP-speaking router.
export route-target, on page 159 Configures a VRF export route-target extended community.
import route-target, on page 168 Configures a VRF import route-target extended community.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
239
BGP Commands
receive-buffer-size
receive-buffer-size
To set the size of the receive buffers for a Border Gateway Protocol (BGP) neighbor, use the
receive-buffer-size command in an appropriate configuration mode. To remove the receive-buffer-size
command from the configuration file and restore the system to its default condition in which the software
uses the default size, use the no form of this command.
Syntax Description socket-size Size, in bytes, of the receive-side socket buffer. Range is 512 to 131072.
bgp-size (Optional) Size, in bytes, of the receive buffer in BGP. Range is 512 to 131072.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the receive-buffer-size command to increase the buffer size when receiving updates from a neighbor.
Using larger buffers can improve convergence time because it allows the software to process a larger number
of packets simultaneously. However, allocating larger buffers consumes more memory on the router.
Note Increasing the socket buffer size uses more memory only when more messages are waiting to be processed
by the software. In contrast, increasing the BGP buffer size uses extra memory indefinitely.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit
the configuration. Values of commands configured specifically for a neighbor override inherited values.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
240
BGP Commands
receive-buffer-size
bgp read,
write
Examples The following example shows how to set the receive buffer sizes for neighbor 172.20.1.1 to be 65,536
bytes for the socket buffer and 8192 bytes for the BGP buffer:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration
mode.
send-buffer-size, on page 269 Sets the size of the send buffers for a BGP neighbor.
session-group, on page 276 Creates a session group and enters session group configuration mode.
socket receive-buffer-size, on page 490 Sets the size of the receive buffers for all BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
241
BGP Commands
redistribute (BGP)
redistribute (BGP)
To redistribute routes from one routing domain into Border Gateway Protocol (BGP), use the redistribute
command in an appropriate configuration mode. To disable route redistribution, use the no form of this
command.
Connected
redistribute connected [metric metric-value] [route-policy route-policy-name]
no redistribute connected [metric metric-value] [route-policy route-policy-name]
Static
redistribute static [metric metric-value] [route-policy route-policy-name]
no redistribute static [metric metric-value] [route-policy route-policy-name]
Syntax Description connected Redistributes connected routes. Connected routes are established automatically
when IP is enabled on an interface.
metric metric-value (Optional) Specifies the Multi Exit Discriminator (MED) attribute used for the
redistributed route. Range is 0 to 4294967295. Use a value consistent with the
destination protocol.
By default, the Interior Gateway Protocol (IGP) metric is assigned to the route. For
connected and static routes the default metric is 0.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
242
BGP Commands
redistribute (BGP)
eigrp Specifies that routes are distributed from EIGRP. You must be in IPv4 unicast or
multicast address family configuration mode or in VRF IPv4 address family
configuration mode.
process-id For the eigrp keyword, an EIGRP instance name from which routes are to be
redistributed.
For the isis keyword, an IS-IS instance name from which routes are to be
redistributed.
For the ospf keyword, an OSPF instance name from which routes are to be
redistributed.
The process-id value takes the form of a string. A decimal number can be entered,
but it is stored internally as a string.
match { internal | (Optional) Specifies the criteria by which OSPF routes are redistributed into other
external [ 1 | 2 ] | routing domains. It can be one or more of the following:
nssa-external [ 1 | 2
• internal —Routes that are internal to a specific autonomous system (intra-
]}
and inter-area OSPF routes).
• external [ 1 | 2 ]—Routes that are external to the autonomous system, but are
imported into OSPF as Type 1 or Type 2 external routes.
• nssa-external [ 1 | 2 ]—Routes that are external to the autonomous system,
but are imported into OSPF as Type 1 or Type 2 not-so-stubby area (NSSA)
external routes.
For the external and nssa-external options, if a type is not specified, then both
Type 1 and Type 2 are assumed.
isis Specifies that routes are distributed from the IS-IS protocol.
Redistribution from IS-IS is allowed under IPv4 unicast, IPv4 multicast, IPv6
unicast, and address-families. Redistribution is not allowed under VPNv4
address-families.
level { 1 | (Optional) Specifies the IS-IS level from which routes are redistributed. It can be
1-inter-area | 2 } one of the following:
• 1 —Routes are redistributed from Level 1 routes.
• 1-inter-area —Routes are redistributed from Level 1 interarea routes.
• 2 —Routes are redistributed from Level 2 routes.
ospf Specifies that routes are distributed from the OSPF protocol. You must be in IPv4
unicast or multicast address family configuration mode or in VRF IPv4 address
family configuration mode.
rip Specifies that routes are distributed from RIP. You must be in IPv4 unicast or
multicast address family configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
243
BGP Commands
redistribute (BGP)
For OSPF, the default is to redistribute internal, external, and NSSA external routes of Type 1 and Type 2.
By default, the Interior Gateway Protocol (IGP) metric is assigned to the route. For connected and static routes
the default metric is 0.
metric metric-value: 0
match { internal | external [ 1 | 2 ] | nssa-external [ 1 | 2 ]}: If no match is specified, the default is to
match all routes.
Command Modes IPv4 address family configuration, both unicast and multicast (connected, eigrp, isis, ospf, rip, and static
are supported)
IPv6 address family configuration, both unicast and multicast (connected, eigrp,
isis,
ospfv3,
and static are supported)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note When redistributing routes (into BGP) using both command keywords for setting or matching of attributes
and a route policy, the routes are run through the route policy first, followed by the keyword matching and
setting.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
244
BGP Commands
redistribute (BGP)
Each instance of a protocol may be redistributed independently of the others. Changing or removing
redistribution for a particular instance does not affect the redistribution capability of other protocols or other
instances of the same protocol.
Networks specified using the network command are not affected by the redistribute command; that is,
the routing policy specified in the network command takes precedence over the policy specified through
the redistribute command.
bgp read,
write
Examples The following example shows how to redistribute IP Version 4 (IPv4) unicast OSPF routes from
OSPF instance 110 into BGP:
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate and
advertise to its neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
245
BGP Commands
refresh-time (rpki-server)
refresh-time (rpki-server)
To configure the time BGP waits in between sending periodic serial queries to the RPKI server, use the
refresh-time command in rpki-server configuration mode. To remove the refresh-time configuration, use the
no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set the refresh-time for BGP to wait in between sending periodic serial
queries to the server as 30 seconds:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#username rpki-user
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#password rpki-ssh-pass
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#preference 1
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#purge-time 30
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#refresh-time 30
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
246
BGP Commands
response-time (rpki-server)
response-time (rpki-server)
To configure the time BGP waits for a response from the RPKI cache-server after sending a serial or reset
query, use the response-time command in rpki-server configuration mode. To remove the response-time
configuration, use the no form of this command.
Syntax Description off Specifies to wait indefinitely for a response from the RPKI cache.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set the time for BGP to wait for a response from the RPKI server as 30
seconds, after sending a serial or reset query:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 72.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#username rpki-user
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#password rpki-ssh-pass
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#preference 1
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#purge-time 30
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#refresh-time 30
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#response-time 30
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
247
BGP Commands
remote-as (BGP)
remote-as (BGP)
To create a Border Gateway Protocol (BGP) neighbor and begin the exchange of routing information, use the
remote-as command in an appropriate configuration mode. To delete the entry for the BGP neighbor, use
the no form of this command.
remote-as as-number
no remote-as [as-number]
Syntax Description as-number Autonomous system (AS) to which the neighbor belongs.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the remote-as command to create a neighbor and assign it a remote autonomous system number. A
neighbor must have a remote autonomous system number before any other commands can be configured for
it. Removing the remote autonomous system from a neighbor causes the neighbor to be deleted. You cannot
remove the autonomous system number if the neighbor has other configuration.
Note We recommend that you use the no neighbor command rather than the no remote-as command to delete
a neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
248
BGP Commands
remote-as (BGP)
A neighbor specified with a remote autonomous system number that matches the autonomous system number
specified in the router bgp command identifies the neighbor as internal to the local autonomous system.
Otherwise, the neighbor is considered external.
Configuration of the remote-as command for a neighbor group or session group using the neighbor-group
command or session-group command causes all neighbors using the group to inherit the characteristics
configured with the command. Configuring the command directly for the neighbor overrides the value inherited
from the group.
In the neighbor configuration submode, configuring use of a session group or neighbor group for which
remote-as is configured creates a neighbor and assigns it an autonomous system number if the neighbor has
not already been created.
Note Do not combine remote-as commands and no use neighbor-group commands, or remote-as commands
and no use session-group commands, in the same configuration commit.
bgp read,
write
Examples The following example shows how to assign autonomous system numbers on two neighbors, neighbor
10.0.0.1, (internal) and neighbor 192.168.0.1 (external), setting up a peering session that shares
routing information between this router and each of these neighbors:
The following example shows how to configure a session group called group2 with an autonomous
system number 1. Neighbor 10.0.0.1 is created when it inherits the autonomous system number 1
from session group group2.
RP/0/RSP0/CPU0:router(config)#router bgp 1
RP/0/RSP0/CPU0:router(config-bgp)# session-group group2
RP/0/RSP0/CPU0:router(config-bgp-sngrp)# remote-as 1
RP/0/RSP0/CPU0:router(config-bgp-sngrp)# exit
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 10.0.0.1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# use session-group group2
neighbor (BGP), on page 203 Enters neighbor configuration mode for configuring BGP routing sessions.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
249
BGP Commands
remote-as (BGP)
Command Description
session-group, on page 276 Creates a session group and enters session group configuration mode.
use, on page 524 Inherits characteristics from a neighbor group, session group, or address family
group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
250
BGP Commands
remove-private-as
remove-private-as
To remove private autonomous system numbers from autonomous system paths when generating updates to
external neighbors, use the remove-private-as command in an appropriate configuration mode. To place
the router in the default state in which it does not remove private autonomous system numbers, use the no
form of this command.
Syntax Description inheritance-disable (Optional) Permits the feature to be disabled from a neighbor group or address family
group instead of being inherited.
entire-aspath (Optional) Removes the entire private autonomous system numbers from an autonomous
system path only if all ASes in the path are private.
Command Default When this command is not specified in the appropriate configuration mode, private autonomous system
numbers are not removed from updates sent to external neighbors.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Release 4.1.0 This command was supported on ASR 9000 Ethernet Line Card (Cisco ASR 9000's
A9K-SIP-700).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
251
BGP Commands
remove-private-as
bgp read,
write
Examples The following example shows a configuration that removes the private autonomous system number
from the IP Version 4 (IPv4) unicast updates sent to 172.20.1.1:
The following example shows how to disable the remove private autonomous system number feature
for neighbor 172.20.1.1, preventing this feature from being automatically inherited from address
family group group1:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
252
BGP Commands
remove-private-as
Command Description
remote-as (BGP), on page 248 Allows entries to the BGP neighbor table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
253
BGP Commands
retain local-label
retain local-label
To retain the local label until the network is converged, use the retain local-label command in an appropriate
address family configuration mode. To disable the retaining of the local label, use the no form of this
command.
Syntax Description minutes Local retention time in minutes. The range is 3 to 60 minutes. The default retention time is 5 minutes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to enable local label retention for 5 minutes:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# retain local-label 5
additional-paths install backup, on page 8 Installs a backup path into the forwarding table
advertise best-external, on page 22 Advertises the best-external path to the iBGP and route-reflector
peers.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
254
BGP Commands
retain route-target
retain route-target
To accept received updates with specified route targets, use the retain route-target command in an appropriate
configuration mode. To disable the retaining of routes tagged with specified route targets, use the no form of
this command.
Syntax Description all Accepts received updates containing at least one route target.
route-policy router-policy-name Accepts received updates accepted by a specified route filter policy.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the retain route-target command to configure a route reflector (RR) to retain routes tagged with specific
route targets (RT).
The retain route-target is a required command for Inter-AS option B ASBR. By default, an Inter-AS option
B ASBR needs the retain route-target configured to get VPNv4 BGP table from PE routers, either with the
all or with the route-policy option.
A provider edge (PE) router is not required to hold all VPNv4 routes. The PE router holds only routes that
match the import RT of the VPNs configured on it, but a RR must retain all VPNv4 routes because it may
peer with PE routers and different PEs may require different RT-tagged VPNv4 routes. Configuring an RR
to hold only routes that have a defined set of RT communities and configuring some of these RRs to service
a different set of VPNs provides scalability to the RRs. A PE can be configured to peer with all RRs that
service the VPN routing and forwarding (VRF) instances configured on the PE. When a new VRF is configured
with an RT for which the PE does not already hold routes, the PE issues route refresh requests to the RRs and
gets the relevant VPN routes.
The route-policy route-policy-name keyword and argument takes the policy name that lists the extended
communities that a path should have for the RR to retain the path.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
255
BGP Commands
retain route-target
Examples The following example shows how to configure RR to retain all routes with the route filter policy
ft-policy-A:
import route-target, on page 168 Configures a VRF import route-target extended community.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
256
BGP Commands
route-policy (BGP)
route-policy (BGP)
To apply a routing policy to updates advertised to or received from a Border Gateway Protocol (BGP) neighbor,
use the route-policy command in an appropriate configuration mode. To disable applying routing policy to
updates, use the no form of this command.
Syntax Description route-policy-name Name of route policy. Up to 16 parameters can follow the route-policy-name, enclosed
in brackets ([ ]).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-policy command to specify a routing policy for an inbound or outbound route. The policy can
be used to filter routes or modify route attributes. The route-policy command is used to define a policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
257
BGP Commands
route-policy (BGP)
Note Configuring a large number of uniquely named outbound neighbor policies can adversely affect performance.
This is true even if the uniquely named route policies are functionally identical. The user is discouraged from
configuring multiple functionally identical route policies for use with this command. For example, if Policy
A and Policy B are identical but named for different neighbors, the two policies should be configured as a
single policy.
If the route-policy command is configured for a neighbor group or neighbor address family group, all
neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor
override inherited values.
bgp read,
write
Examples The following example shows how to apply the In-Ipv4 policy to inbound IP Version 4 (IPv4) unicast
routes from neighbor 172.20.1.1:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
route-policy (RPL) Defines a route policy and enters route-policy configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
258
BGP Commands
route-reflector-client
route-reflector-client
To configure the router as a Border Gateway Protocol (BGP) route reflector and configure the specified
neighbor as its client, use the route-reflector-client command in an appropriate configuration mode. To
disable configuring the neighbor as a client, use the no form of this command.
route-reflector-client [inheritance-disable]
no route-reflector-client [inheritance-disable]
Syntax Description inheritance-disable (Optional) Allows the configuration inherited from a neighbor group or address family
group to be overridden.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is restricted to internal BGP (iBGP) neighbors only.
Use the route-reflector-client command to configure the local router as the route reflector and the specified
neighbor as one of its clients. All neighbors configured with this command are members of the client group,
and the remaining iBGP peers are members of the nonclient group for the local route reflector.
By default, all iBGP speakers in an autonomous system must be fully meshed with each other, and neighbors
do not readvertise iBGP learned routes to other iBGP neighbors.
With route reflection, all iBGP speakers need not be fully meshed. An iBGP speaker, the route reflector,
passes learned iBGP routes to some number of iBGP client neighbors. Learned iBGP routes eliminate the
need for each router running BGP to communicate with every other device running BGP in the autonomous
system.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
259
BGP Commands
route-reflector-client
The local router is a route reflector as long as it has at least one route reflector client.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the
group inherit the configuration. Values of commands configured specifically for a neighbor override inherited
values.
bgp read,
write
Examples The following example shows neighbor at 172.20.1.1 configured as a route reflector client for IP
Version 4 (IPv4) unicast routes:
The following example disables the route-reflector client for neighbor 172.20.1.1, preventing this
feature from being automatically inherited from address family group group1:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
bgp cluster-id, on page 71 Configures the cluster ID if the BGP cluster has more than one route reflector.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
260
BGP Commands
optimal-route-reflection
optimal-route-reflection
To enable the BGP optimal route reflector (ORR) feature, use the optimal-route-reflection command in
router BGP, or neighbor configuration mode, as appropriate.
Syntax Description orr-group-name Specify the ORR group name. A maximum of 32 characters are allowed.
primary-ip-address Specify the primary SPF root IP address. Depending on the address family configured
under BGP, the SPF root IP address can be either IPv4 or IPv6.
The primary SPF root IP address is the IP address of the router for which best path
is calculated.
secondary-ip-address [Optional] Specify the secondary SPF root IP address. Depending on the address
family configured under BGP, the SPF root IP address can be either IPv4 or IPv6.
The secondary SPF root IP address is the IP address of the nearest neighbor of the
router for which best path is calculated.
tertiary-ip-address [Optional] Specify the tertiary SPF root IP address. Depending on the address family
configured under BGP, the SPF root IP address can be either IPv4 or IPv6.
The secondary SPF root IP address is the IP address of the nearest neighbor of the
router for which best path is calculated.
neighbor configuration
Usage Guidelines
Task ID Task Operation
ID
bgp read,
write
This sample shows how to determine shortest exit point for the router with IP address 192.0.2.1, in
the domain with AS number 6500, and ORR group name group1. This configuration is executed on
virtual router reflector:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
261
BGP Commands
optimal-route-reflection
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
262
BGP Commands
router bgp
router bgp
To configure the Border Gateway Protocol (BGP) routing process, use the router bgp command in Global
Configuration mode mode. To remove all BGP configurations and terminate the BGP routing process, use
the no form of this command.
Syntax Description as-number Number that identifies the autonomous system (AS) in which the router resides.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1
to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
instance Specifies an instance and instance name. The maximum length for the instance name
instance-name is 32 characters.
The router bgp instance instance-name command replaced the distributed speaker
command.
Release 3.9.0 Asplain format for 4-byte Autonomous system number notation was supported.
Release 4.2.0 The instance and instance-name keyword and argument were added to support BGP
Multi-Instance/Multi-AS feature. The command with the instance and instance-name keyword
and argument replaced the distributed speaker command.
Usage Guidelines Use the router bgp command to set up a distributed routing core that automatically guarantees the loop-free
exchange of routing information between autonomous systems.
bgp read,
write
rib read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
263
BGP Commands
router bgp
Examples The following example shows how to configure a BGP process for autonomous system 120:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
264
BGP Commands
rpki server
rpki server
To enter resource public key infrastructure (RPKI) cache-server (rpki-sever) configuration mode and enable
rpki parameters configuration, use the rpki server command in Router BGP configuration mode. To remove
the rpki-server configuration mode and delink cache-server from the cache list, use the no form of this
command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure an rpki cache-server database and enter rpki-server configuration
mode:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-cache)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
265
BGP Commands
rpki route
rpki route
To statically configure an RPKI route, use the rpki route command in the router BGP configuration submode.
The no form of this command removes the RPKI routes.
Syntax Description ip-address/length Specifies the IP address of the network along with the minimum
prefix length.
max max-prefix-length Specifies the maximum prefix length (32 for IPv4 and 128 for
IPv6).
origin origin-autonomous-system-number Specifies the autonomous system number.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In general, BGP receives the Route-Origin-Attestation (ROA) information from RPKI cache. However, the
rpki route command is used for verification. This command can be used to configure both IPv4 and IPv6
ROAs.
This command contains all the essential attributes of an ROA record, that is, the prefix-block (IP address/length
(minimum/maximum)) and the origin AS authorized to create the prefix-block.
Multiple static ROAs can be configured through this command and these entries will be included in the routers
RPKI database, as if they were fetched from an RPKI cache.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki route 192.168.1.0/24 max 30 origin 65001
RP/0/RSP0/CPU0:router(config-bgp)#rpki route 172.200.0.0/16 max 24 origin 300
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
266
BGP Commands
rpki route
RP/0/RSP0/CPU0:router(config-bgp)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
267
BGP Commands
selective-vrf-download disable
selective-vrf-download disable
To disable selective VRF download (SVD) on a line card to enable download all prefixes and labels to the
line card, use the selective-vrf-download disable command in global configuration mode. To enable the
SVD, use the no form of this command.
selective-vrf-download disable
no selective-vrf-download disable
Release Support for this command was removed. This command was replaced with the no svd platform
4.3.1 enable command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must failover the active RP or reload the router after disabling SVD for the configuration change to get
activated.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#selective-vrf-download disable
show svd state, on page 480 Displays Selective VRF Download (SVD) state information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
268
BGP Commands
send-buffer-size
send-buffer-size
To set the size of the send buffers for a Border Gateway Protocol (BGP) neighbor, use the send-buffer-size
command in an appropriate configuration mode. To set the size of the send buffers to the default values, use
the no form of this command.
Syntax Description socket-size Size, in bytes, of the send-side socket buffer. Range is 4096 to 131072.
bgp-size (Optional) Size, in bytes, of the BGP process send buffer. Range is 4096 to 131072.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the send-buffer-size command to increase the buffer size employed when sending updates to a neighbor.
Using larger buffers can improve convergence time because the software can process more packets
simultaneously. However, allocating larger buffers uses more memory on the router.
Note Increasing the socket buffer size uses more memory only when more messages are waiting to be processed
by the software. In contrast, increasing the BGP buffer size uses more memory indefinitely.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit
the configuration. Values of commands configured specifically for a neighbor override inherited values.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
269
BGP Commands
send-buffer-size
bgp read,
write
Examples The following example shows how to set the send buffer sizes for neighbor 172.20.1.1 to be 8192
bytes for both the socket buffer and the BGP buffer:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration
mode.
receive-buffer-size, on page 240 Sets the size of the receive buffers for a BGP neighbor.
session-group, on page 276 Creates a session group and enters session group configuration mode.
socket send-buffer-size, on page 492 Sets the size of the send buffers for all BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
270
BGP Commands
send-community-ebgp
send-community-ebgp
To specify that community attributes should be sent to an external Border Gateway Protocol (eBGP) neighbor,
use the send-community-ebgp command in an appropriate configuration mode. To disable sending community
attributes to an eBGP neighbor, use the no form of this command.
send-community-ebgp [{inheritance-disable}]
no send-community-ebgp [{inheritance-disable}]
Syntax Description inheritance-disable (Optional) Allows configuration inherited from a neighbor group or address family
group to be overridden.
Command Default Community (COMM) attributes are NOT sent to eBGP peers (including PE-CE peers).
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the send-community-ebgp command to control whether community attributes are sent to eBGP
neighbors. This command cannot be configured for iBGP neighbors as community attributes are always sent
to iBGP neighbors.
When IOS XR BGP updates community attributes for eBGP VPN peers (VPNv4 or VPNv6), there is no need
to configure the send-community-ebgp command separately. The community attributes are updated by
default.
If this command is configured for a neighbor group or address family group, all neighbors using the group
inherit the configuration. Configuring the command specifically for a neighbor overrides inherited values.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
271
BGP Commands
send-community-ebgp
bgp read,
write
Examples The following example shows how to disable the router that sends community attributes to neighbor
172.20.1.1 for IP Version 4 (IPv4) multicast routes:
The following example shows how to disable the delivery of community attributes to neighbor
172.20.1.1, preventing this feature from being inherited from address family group group1:
af-group, on page 27 Creates an address family group for BGP neighbors and enters
address family group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration
mode.
send-extended-community-ebgp, on page Specifies that extended community attributes are sent to eBGP
274 neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
272
BGP Commands
send-community-gshut-ebgp
send-community-gshut-ebgp
To direct the router to add the gshut community to the path having the gshut attribute or the path being sent
to a connection that has graceful maintenance activated, use the send-community-gshut-ebgp command in
the neighbor address family configuration mode. To disable the g-shut community from being announced to
ebgp neighbors, use the no form of this command.
send-community-gshut-ebgp [{inheritance-disable}]
Syntax Description inheritance-disable (Optional) Prevent send-community-gshut-ebgp from being inherited from the parent.
Usage Guidelines Under neighbor address family configuration, use the send-community-gshut-ebgp command to allow the
g-shut community to be sent if it is an ebgp neighbor. A path acquires the gshut attribute when it is received
from a connection that has graceful maintenance activated. The sending of the gshut community if it is present
because the path was received with that community or if it was added by outbound policy is governed like
all other communities by the send-community-ebgp configuration.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
273
BGP Commands
send-extended-community-ebgp
send-extended-community-ebgp
To specify that extended community attributes should be sent to external Border Gateway Protocol (eBGP)
neighbors, use the send-extended-community-ebgp command in an appropriate configuration mode. To
disable sending extended community attributes to eBGP neighbors, use the no form of this command.
send-extended-community-ebgp [{inheritance-disable}]
no send-extended-community-ebgp [{inheritance-disable}]
Syntax Description inheritance-disable (Optional) Allows configurations inherited from a neighbor group or address family
group to be overridden.
Command Default Extended community (EXTCOMM) attributes are NOT sent to eBGP peers (including PE-CE peers).
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the send-extended-community-ebgp command to control whether extended community attributes are
sent to eBGP neighbors. This command cannot be used for iBGP neighbors as extended community attributes
are always sent to iBGP neighbors.
When IOS XR BGP updates community attributes for eBGP VPN peers (VPNv4 or VPNv6), there is no need
to configure the send-extended-community-ebgp command separately. The community attributes are updated
by default.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the
group inherit the configuration. Values of commands configured specifically for a neighbor override inherited
values.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
274
BGP Commands
send-extended-community-ebgp
bgp read,
write
Examples The following example shows how to configure the router to send extended community attributes
to neighbor 172.20.1.1 for IP Version 4 (IPv4) multicast routes:
The following example shows how to disable the delivery of extended community attributes to
neighbor 172.20.1.1, preventing this feature from being automatically inherited from address family
group group1:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address
family group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
send-community-ebgp, on page 271 Specifies that community attributes should be sent to an eBGP neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
275
BGP Commands
session-group
session-group
To create a session group and enter session group configuration mode, use the session-group command in
router configuration mode. To remove a session group and delete all configurations associated with it, use
the no form of this command.
session-group name
no session-group name
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the session-group command to create a session group from which neighbors can inherit configuration
that is address family-independent. That is, session groups cannot have address family-specific configuration.
This command enters the session group configuration mode in which configuration for a session group is
entered.
Many commands can be configured in both session group configuration mode and neighbor configuration
mode.
Use of session groups saves time and reduces the router configuration size. Because the configuration of a
session group can be inherited by any number of neighbors, use of the group can eliminate the need to copy
long or complex configurations on each of a large number of neighbors. A neighbor can inherit all configuration
from a session group simply by configuring the use command. Specific inherited session group configuration
commands can be overridden for a specific neighbor by explicitly configuring the command for the specific
neighbor.
The no form of this command causes all of the configuration for the session group to be removed. You cannot
use the no form of this command if removing the group would leave one or more neighbors without a
configured remote autonomous system number.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
276
BGP Commands
session-group
Examples The following example shows a session group called group1 that is used by two neighbors, 10.0.0.1
and 10.0.0.2. Because group1 is a session group, it contains only address family-independent
configuration. And because group1 is used by neighbors 10.0.0.1 and 10.0.0.2, they inherit the
configuration of the group.
The following example shows a session group called group1 used by two neighbors, 10.0.0.1 and
10.0.0.2. Because group1 is a session group, it contains only address family-independent configuration.
And because group1 is used by neighbors 10.0.0.1 and 10.0.0.2, they inherit the configuration of the
group. However, the password password1 configuration from group1 is overridden for neighbor
10.0.0.2, using the password-disable command in the neighbor 10.0.0.2 configuration submode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
277
BGP Commands
session-open-mode
session-open-mode
To establish a Border Gateway Protocol (BGP) session with a specific TCP open mode, use the
session-open-mode command in an appropriate configuration mode. To restore the default state, use the no
form of this command.
Syntax Description active-only Ensures that the BGP session can be established only when the request is initiated by the local
end (active-open request) and all passive-open requests (from the other end) are rejected by
the local BGP.
both Allows BGP sessions to be established from both incoming or outgoing TCP connection
requests, with one being rejected in the event of a request collision.
passive-only Ensures that the local BGP does not initiate any TCP open requests and the session can be
established only when the request comes from the remote end.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
BGP, by default, tries to initiate an active TCP connection whenever a new neighbor is configured. A remote
neighbor may also initiate the TCP connection before the local BGP can initiate the connection. This initiation
of a TCP connection by a remote neighbor is considered a passive-open request and it is accepted by the local
BGP. This default behavior can be modified using the session-open-mode command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
278
BGP Commands
session-open-mode
Note The BGP connection is not opened and, as a result the BGP session, is not established if both the peering
neighbors use the same nondefault TCP session open mode—active-only or passive-only. If both ends are
configured with active-only, each neighbor rejects the TCP open request from the other end. One neighbor
must be configured as passive-only or both. Similarly, if both neighbors are configured with passive-only,
neither neighbor initiates the TCP open request and the BGP session is not established. Again, one neighbor
must be configured as active-only or both. There is one exception. A connection open request from a neighbor
that is configured with the TCP session open mode to be passive-only is processed to detect whether there is
a connection collision before the request is rejected. This exception enables the local BGP to reset the session
if the remote neighbor goes down and it is not detected by the local router.
Use the session-open-mode command when it may be necessary to preconfigure a neighbor that does not
exist. Ensure that BGP does not spend any time actively trying to set up a TCP session with the neighbor. A
BGP session does not come up between two neighbors, both of which configure the same nondefault value (
active-only or passive-only keyword) for this command.
bgp read,
write
Examples The following example shows how to enable a BGP session on router bgp 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
279
BGP Commands
set flow-tag
set flow-tag
To set the flow-tag value for the PBR BGP, use the set flow-tag command in route-policy configuration
mode.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set flow-tag command to set the flow-tag to classify packets.
This command is supported at the BGP table-policy attachpoint. Prefixes are marked for subsequent processing
in the forwarding plane. After flow-tag propagation through Border Gateway Protocol (BGP), flow-tag is
enabled on an interface, corresponding traffic shaping and policing is completed using packet classification
based on the flow-tag value.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
280
BGP Commands
show bgp
show bgp
To display entries in the Border Gateway Protocol (BGP) routing table, use the show bgp command in EXEC
mode.
show bgp [{ipv4 {unicast | multicast | labeled-unicast | all | tunnel | | flowspec} | ipv6 {unicast |
multicast | all | labeled-unicast | | flowspec} | all {unicast | multicast | all | labeled-unicast | mdt |
tunnel} | vpnv4 { flowspec | multicast | unicast} [rd rd-address] | vrf {vrf-name | all} [{ipv4 {unicast
| labeled-unicast} | ipv6 {unicast | flowspec}}] | { flowspec | unicast} | [instance] | [instances] |
flowspec}] [ip-address [{mask | /prefix-length} [{longer-prefixes | unknown-attributes |
bestpath-compare}]]] [standby] [detail]
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address families.
labeled-unicast }
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
281
BGP Commands
show bgp
/ prefix-length (Optional) Prefix length of the BGP route to match. A slash (/) must precede
the decimal value.
longer-prefixes (Optional) Displays a route with the specified prefix length and more-specific
routes if available. The longer-prefixes keyword is available when the
ip-address and mask or /prefix-length arguments are specified.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.1.1 The command output was modified to display from BGP Accept Own configuration.
Release 4.0.0 The command output was modified to display BGP add-path information.
Release 4.3.0 The command output was modified to include information from update wait-install
configuration.
Release 5.1.1 The command output was modified to display the status of permanent paths.
Release 5.2.0 The command output was modified to include the following:
• Flowspec configuration information
• VPNv4 multicast prefixes
Release 5.2.2 The command output was modified to include the BGP Persistence or long lived graceful
restart (LLGR) status.
Release 5.3.2 The command output was modified to include graceful maintenance feature information.
Release 6.1.2 The command output was modified to include BGP optimal route reflector feature information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
282
BGP Commands
show bgp
Without BGP ORR configured in the network, the vRR selects R4 as the closest exit point for RR clients R2,
R3, R5, and R6, and reflects the 6/8 prefix learned from R4 to these RR clients R2, R3, R5, and R6. From the
topology, it is evident that for R2 the best path is R1 and not R4. This is because the vRR calculates best path
from the RR's point of view.
When the BGP ORR is configured in the network, the vRR calculates the shortest exit point in the network
from R2’s point of view and determines that R1 is the closest exit point to R2. vRR then reflects the 6/8 prefix
learned from R1 to R2.
set default-afi
Note The set default-afi command is used to specify the default address family for the sessions and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
283
BGP Commands
show bgp
BGP contains a separate routing table for each address family and subaddress family combination that has
been configured. The address family and subaddress family options specify the routing table to be examined.
If the all keyword is specified for an address family or a subaddress family, each matching routing table is
examined in turn.
Note Running the show bgp command immediately after configuring a large and complex route policy may result
in timeout of the system database shown through an error message (SYSDB-SYSDB-6-TIMEOUT_EDM). It is
recommended, that the show command be run, after the new route policy takes effect.
Use the show bgp ip-address { mask | / prefix-length } command to display detailed information for a
specific route. If the mask and prefix length are omitted, the details of the longest matching prefix for the IP
address are displayed.
Use the show bgp command to display all routes in the specified BGP routing table. Use the show bgp
ip-address { mask | / prefix-length } longer-prefixes command to display those routes more specific than
a particular prefix.
Use the unknown-attributes keyword to display details of any transitive attributes associated with a route
that are not understood by the local system.
bgp read
The above show output states that the best path for R2 is through R1, whose IP address is 192.0.2.1
and the metric of the path is 20.
Execute the show bgp command from the vRR to determine the best path calculated for R2 by ORR.
R2 has its own update-group because it has a different best path (or different policy configured) than
those of other peers.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
284
BGP Commands
show bgp
The following is sample output from the show bgp command in EXEC mode with the BGP
Persistence or long lived graceful restart (LLGR) status:
RP/0/RSP0/CPU0:router# show bgp vpnv4 uni rd 2:1 3.0.0.0/24
[KBGP routing table entry for 3.0.0.0/24, Route Distinguisher: 2:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 350584 350584
Local Label: 16010
Last Modified: Jun 23 06:22:12.821 for 00:03:27
Paths: (1 available, best #1)
Not advertised to any peer
Path #1: Received by speaker 0
Not advertised to any peer
6913, (Received from a RR-client), (long-lived stale)
4.4.4.4 (metric 3) from 3.3.3.3 (4.4.4.4)
Received Label 16000
Origin EGP, localpref 100, valid, internal, best, group-best, import-candidate,
not-in-vrf
Received Path ID 0, Local Path ID 1, version 350584
Extended community: RT:2:1
Originator: 4.4.4.4, Cluster list: 3.3.3.3
The following is the sample output from the show bgp <IP address> command displaying the
graceful-shutdown community and the graceful-shut path attribute with BGP graceful maintenance
feature activated:
RP/0/0/CPU0:R4#show bgp 5.5.5.5
...
10.10.10.1 from 10.10.10.1 (192.168.0.5)
Received Label 24000
Origin incomplete, metric 0, localpref 100, valid, internal, best, group-best,
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
285
BGP Commands
show bgp
import-candidate
Received Path ID 0, Local Path ID 1, version 4
Community: graceful-shutdown
Originator: 192.168.0.5, Cluster list: 192.168.0.1
...
The following is sample output from the show bgp command in EXEC mode:
RP/0/RSP0/CPU0:router#show bgp
BGP router identifier 172.20.1.1, local AS number 1820
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0xe0000000
BGP main routing table version 3
Dampening enabled
BGP scan interval 60 secs
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
286
BGP Commands
show bgp
Field Description
BGP generic scan Interval (in seconds) between scans of the BGP table by a generic scanner.
interval
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between BGP scans for the specified address family and
subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was sourced by
BGP using a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
287
BGP Commands
show bgp
Field Description
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
path origin code.
The following is sample output from the show bgp command with the network specified:
Field Description
bRIB/RIB Version of the network for sending to the RIB. You can compare this version
with the bRIB/RIB version for the process (at the top of show bgp summary
) to verify whether the network has been sent to the RIB.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
288
BGP Commands
show bgp
Field Description
SendTblVer Version of the network for advertising to neighbors. This can be compared
with the neighbor version to determine whether the network has been
advertised to a particular neighbor.
Paths List of paths for the network (that is, routes to reach the network). The
number of paths and the index of the best path are given.
not advertised to any peer Best path was received with a NO_ADVERTISE community and is not
advertised to any neighbor.
not advertised to EBGP peer Best path was received with a NO_EXPORT community and is not advertised
to any eBGP neighbor.
not advertised outside local AS Best path was received with a LOCAL_AS community and is not advertised
to peers outside the local AS.
Advertisements of this net are Network is a more-specific prefix of a configured aggregate and has been
suppressed by an aggregate suppressed. It is not advertised to any neighbors unless they have an
unsuppress-map configured.
Advertised to update-groups List of update-groups to which the net has been advertised. Update-groups
that have only one peer are not listed here.
Advertised to peers List of neighbors to which the net has been advertised to. Neighbors that are
in one of the update-groups listed above are not listed separately. Only
neighbors that are in unique update-groups are listed.
Received by speaker 0 BGP process where the path originated. This is always “speaker 0” for
standalone mode. It will be the speaker-id when BGP is in distributed mode.
AS Path Autonomous system (AS) path that was received for the path. If the AS path
is empty, then “Local” is displayed. This is the case for paths that are locally
generated on this router or on a neighboring router within the same AS.
aggregated by If the path is an aggregate, the router-id of the router that performed the
aggregation.
suppressed due to dampening Path has been suppressed due to the configured path dampening.
history entry Path is withdrawn, but a copy is kept to store the dampening information.
Received from a RR-client Path was received from a route reflector client.
received-only If soft reconfiguration inbound is configured, the path was received but
dropped by inbound policy, or was accepted and modified. In either event,
the received-only value is a copy of the original, unmodified path.
received & used If soft reconfiguration inbound is configured, the path was received and
accepted by inbound policy, but not modified.
stale Neighbor from which the path was received is down, and the path is kept
and marked as stale to support graceful restart.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
289
BGP Commands
show bgp
Field Description
<nexthop> from <neighbor> Next hop for the path. If the next hop is known by a mechanism outside BGP
(<router-id>) (for example, for redistributed paths), then 0.0.0.0 is displayed. After the
next hop, the neighbor from whom the path was received is displayed, along
with the neighbor’s router-id. If the path was locally generated (for example,
an aggregate or redistributed path), then 0.0.0.0 is displayed for the neighbor
address.
localpref Local preference value. This is used to determine the preferred exit point
from the local autonomous system. It is propagated throughout the local
autonomous system.
weight Locally assigned weight (if not 0) of the path. Weight is used in choosing
the preferred path to a route. It is not advertised to any neighbor.
atomic-aggregate Path was received with the atomic-aggregate flag set. Some path information
has been removed through aggregation.
best Path is the best path for the network and is used for routing and advertised
to peers.
multipath Path is a multipath and is installed into the RIB along with the best path.
Originator Originator of the path within the AS Cluster list if the path is reflected.
AS Cluster list List of RR clusters the path has passed through if the path is reflected
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
290
BGP Commands
show bgp
Field Description
flapped Number of times the path has flapped and the time since the first flap.
Maximum suppress time Maximum length of time for which the path can be suppressed.
The following is sample output from the show bgp command with the ip-address/prefix-length
detail options:
Versions:
Speaker 3 3
201.48.20.1
Flags: 0x1000003
200 201
The following is sample output from the show bgp command with the additional paths received from:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
291
BGP Commands
show bgp
Flags: 0x040630f2
Last Modified: Nov 11 12:44:05.811 for 00:00:16
Paths: (3 available, best #2)
Advertised to CE peers (in unique update groups):
10.51.0.10
Path #1: Received by speaker 0
Flags: 0x3
Not advertised to any peer
111 111 111 111 111 111 111 111
10.51.0.10 from 10.51.0.10 (11.11.11.11)
Origin IGP, metric 0, localpref 100, valid, external
Received Path ID 0, Local Path ID 0, version 0
Extended community: RT:55:1
Path #2: Received by speaker 0
Flags: 0x5060007
Advertised to CE peers (in unique update groups):
10.51.0.10
561 562 563 564 565
13.0.6.50 from 13.0.6.50 (13.0.6.50)
Received Label 16
Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate,
imported
Received Path ID 0, Local Path ID 1, version 63
Extended community: RT:55:1
Path #3: Received by speaker 0
Flags: 0x4060007
Not advertised to any peer
591 592 593 594 595
13.0.9.50 from 13.0.9.50 (13.0.9.50)
Received Label 16
Origin IGP, localpref 100, valid, internal, backup, add-path, import-candidate,
imported
Received Path ID 0, Local Path ID 4, version 63
Extended community: RT:22:232 RT:55:1
This is sample output to explain 'import suspect' state and 'import-suspect' field in show bgp command
output:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
292
BGP Commands
show bgp
The show bgp command output displays 'import suspect' when potential import oscillation has been
detected for the prefix. Import of such a prefix is not affected. However, import of the prefix can be
dampened in future if the oscillation continues. If the oscillation stops during the next import run,
the prefix will no longer be marked 'import supect'.
This is sample output of show bgp {ipv4 | vpnv4} unicast summary when the update wait-install
command was configured for an address family. The output displays the "RIBAckVer" field.
This is sample output from show bgp vpnv4 unicast rd prefix/length command that displays Accept
Own prefix information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
293
BGP Commands
show bgp
This is sample output from show bgp vrf vrf-name ipv4unicast prefix/length command that displays
Accept Own prefix information on a customer (originating) VRF:
This is sample output from show bgp vrf vrf-name ipv4unicast prefix/length command that displays
Accept Own prefix information on a service VRF:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
294
BGP Commands
show bgp
Field Description
accept-own-self The Accept Own path in the customer VRF contains
the "accept-own-self" keyword/flag.
The output of show bgp {vpnv4 | vpnv6} unicast rd command may display the optional BGP
attribute not-in-vrf. If a path in a VPNvX net is marked as not-in-vrf, it may be due to any of
the following conditions:
• The RD of the VPNvX net is not the same as any of the RDs configured for VRFs on the router.
• The RD of the VPNvX net is the same as the RD configured for a specific VRF on the router,
but the path is not imported to the specified VRF. For example, the route-targets attached to the
path do not match any of the import route-target [as-number:nn | ip-address:nn] configured
for VRF, vrf_1.
If the not-in-vrf net is set, it indicates that the path does not belong to the VRF.
This is sample output from the show bgp ipv4 unicast command showing the status of the permanent
network:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
295
BGP Commands
show bgp
bgp default local-preference, on page 79 Changes the default local preference value.
network (BGP), on page 208 Specifies a local network that the BGP routing process should
originate and advertise to its neighbors.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received
from a BGP neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current
session.
set default-safi Sets the default subaddress Family Identifier (SAFI) for the
current session.
show bgp cidr-only, on page 324 Displays routes with nonnatural netmasks.
show bgp community, on page 328 Displays routes belonging to the specified communities.
show bgp inconsistent-as, on page 345 Displays networks with inconsistent origin autonomous
system.
show bgp regexp, on page 436 Displays routes matching an AS path regular expression.
show bgp route-policy, on page 440 Displays networks that match a route policy.
show bgp summary, on page 450 Displays the status of all BGP connections.
show bgp truncated-communities, on page Displays networks with community lists truncated by policy.
461
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
296
BGP Commands
show bgp bmp
Syntax Description server server-id Displays information about BMP server as specified by the server-id variable.
summary Displays summary information about all the configured BMP servers.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
Examples The following example shows sample output from the show bgp bmp command when the summary
keyword is used:
The following example shows sample output from the show bgp bmp command when the server
keyword, with server ID as 4, is used:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
297
BGP Commands
show bgp bmp
Message Stats:
Total messages sent: 60
INITIATION: 1
TERMINATION: 0
STATS-REPORT: 0
PER-PEER messages: 59
Neighbor 20.0.101.11
Messages pending: 0
Messages sent: 59
PEER-UP: 1
PEER-DOWN: 0
ROUTE-MON: 58
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
298
BGP Commands
show bgp update out
show bgp [vrf vrf-name] [afi safi] update out [{brief | detail}]
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example displays sample output from the show bgp update out command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
299
BGP Commands
show bgp update out
Filter-groups: 1
Neighbors: 3
History:
Update OutQ Hi: 300 bytes (1 messages)
Update OutQ Cumulative: 600 bytes (2 messages)
Update OutQ Discarded: 0 bytes (0 messages)
Update OutQ Cleared: 0 bytes (0 messages)
Last discarded from OutQ: --- (never)
Last cleared from OutQ: --- (never)
Update generation throttled 0 times, last event --- (never)
Update generation recovered 0 times, last event --- (never)
Update generation mem alloc failed 0 times, last event --- (never)
RP/0/RSP0/CPU0:PE51_ASR-9010#
RP/0/RSP0/CPU0:PE51_ASR-9010#
RP/0/RSP0/CPU0:PE51_ASR-9010#show bgp update out filter-group
Thu Sep 13 01:43:48.183 DST
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
300
BGP Commands
show bgp update in error process
Syntax Description brief (Optional) Displays brief information on process level update generation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
This example displays sample output from the show bgp update in error process command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
301
BGP Commands
show bgp update out filter-group
show bgp [vrf vrf-name] [afi safi] update out filter-group [fg-process-id] [{brief | detail}]
afi safi Specifies the address family and subsequent address family identifiers.
fg-process-id Specifies the filter-group process ID in <x.y> format. Range is < 0-15>.<0-4294967295>.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
This example displays sample output from show bgp update out filter-group command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
302
BGP Commands
show bgp update out process
Syntax Description brief (Optional) Displays brief information on process level update generation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example displays sample output from the show bgp update out process brief command:
History:
Update OutQ Hi: 300 bytes (1 messages)
Update OutQ Cumulative: 1200 bytes (4 messages)
Update OutQ Discarded: 0 bytes (0 messages)
Update OutQ Cleared: 0 bytes (0 messages)
Last discarded from OutQ: --- (never)
Last cleared from OutQ: --- (never)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
303
BGP Commands
show bgp update out process
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
304
BGP Commands
show bgp update out sub-group
show bgp [vrf vrf-name] [afi safi] update out [update-group ug-index] sub-group [sg-index]
[{brief | detail}]
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example displays sample output from the show bgp update out sub-group command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
305
BGP Commands
show bgp update out sub-group
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
306
BGP Commands
show bgp update out update-group
show bgp [vrf vrf-name] [afi safi] update out update-group [ug-index] [{brief | detail}]
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows the significant fields on display form the show bgp update out update-group
command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
307
BGP Commands
show bgp update out update-group
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
308
BGP Commands
show bgp vrf update in error
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
This example displays sample output from show bgp vrf vrf1 update in error command:
VRF "default"
Malformed Update messages: 0
Neighbors that received malformed Update messages: 0
Last malformed update received: --- (never)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
309
BGP Commands
show bgp advertised
show bgp [ipv4 { all | labeled-unicast | multicast | tunnel | unicast }] advertised [neighbor
ip-address] [standby] [summary]
show bgp [ ipv6 { all | labeled-unicast | multicast | unicast}] advertised [neighbor ip-address]
[standby] [summary]
show bgp [ all { all | labeled-unicast | multicast | tunnel | unicast }] advertised [neighbor
ip-address] [standby] [summary]
show bgp [ vpnv4 unicast [rd rd-address]] advertised [neighbor ip-address] [standby] [summary]
show bgp [ vpnv6 unicast [ rd rd-address]] advertised [neighbor ip-address] [standby] [summary]
show bgp [ vrf {vrf-name | all} [{ ipv4 | {labeled-unicast | unicast} | ipv6 unicast}]] advertised
[neighbor ip-address] [standby] [summary]
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
310
BGP Commands
show bgp advertised
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each address family and subaddress family combination that is
configured. The address family and subaddress family options specify the routing table to be examined. If the
all keyword is specified for the address family or subaddress family, each matching routing table is examined
in turn.
Use the show bgp advertised command to display the routes that have been advertised to peers or a specific
peer. To preview advertisements that would be sent to a peer under a particular policy, even if the corresponding
update messages have not been generated yet, use the show bgp policy command.
Note When you issue the show bgp advertised command, a route is not displayed in the output unless an
advertisement for that route has already been sent (and not withdrawn). If an advertisement for the route has
not yet been sent, the route is not displayed.
Use the summary keyword to display a summary of the advertised routes. If you do not specify the summary
keyword, the software displays detailed information about the advertised routes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
311
BGP Commands
show bgp advertised
Note The show bgp advertised command does not display the application of any outbound policy in the route
details it displays. Consequently, this command provides only an indication of whether a particular route has
been advertised, rather than details of which attributes were advertised. Use the show bgp policy
sent-advertisements command to display the attributes that are advertised.
bgp read
Examples The following is sample output from the show bgp advertised command in EXEC mode:
Field Description
Next Hop IP address of the next system that is used when a packet is forwarded to the destination
network. An entry of 0.0.0.0 indicates that the router has a non-BGP route to this network.
Advertised to Indicates the peer to which this entry was advertised. This field is used in the output when
displaying a summary of the advertisements to all neighbors.
The following is sample output from the show bgp advertised command for detailed advertisement
information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
312
BGP Commands
show bgp advertised
Field Description
is advertised to IP address of the peer to which this route has been advertised. If the route has been
advertised to multiple peers, the information is shown separately for each peer.
neighbor IP address of the peer that advertised this route, or one of the following:
Local—Route originated on the local system.
Local Aggregate—Route is an aggregate created on the local system.
neighbor router id BGP identifier for the peer, or the local system if the route originated on the local
system.
Not advertised to any Indicates the no-advertise well-known community is associated with this route.
peer Routes with this community are not advertised to any BGP peers.
Not advertised to any Indicates the no-export well-known community is associated with this route. Routes
EBGP peer with this community are not advertised to external BGP peers, even if those external
peers are part of the same confederation as the local router.
Not advertised outside Indicates the local-AS well-known community is associated with this route. Routes
the local AS with this community value are not advertised outside the local autonomous system
or confederation boundary.
(received-only) This path is not used for routing purposes. It is used to support soft reconfiguration,
and records the path attributes before inbound policy was applied to a path received
from a peer. A path marked “received-only” indicates that either the path was
dropped by inbound policy, or the path information was modified by inbound
policy and a separate copy of the modified path is used for routing.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
313
BGP Commands
show bgp advertised
Field Description
(received & used) Indicates that the path is used both for soft reconfiguration and routing purposes.
A path marked “received and used,” implies the path information was not modified
by inbound policy.
Attributes after inbound Displays attributes associated with the received route, after any inbound policy
policy was applied has been applied.
AGG—Aggregator attribute is present.
AS—AS path attribute is present.
ATOM—Atomic aggregate attribute is present.
COMM—Communities attribute is present.
EXTCOMM—Extended communities attribute is present.
LOCAL—Local preference attribute is present.
MET—Multi Exit Discriminator (MED) attribute is present.
next hop—IP address of the next system used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
ORG—Origin attribute is present.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
314
BGP Commands
show bgp advertised
Field Description
aggregator Indicates that the path was received with the aggregator attribute. The autonomous
system number and router-id of the system that performed the aggregation are
shown.
metric Value of the interautonomous system metric, otherwise known as the MED metric.
localpref Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system
community Community attributes associated with the path. Community values are displayed
in AA:NN format, except for the following well-known communities:
Local-AS—Community with value 4294967043 or hex 0xFFFFFF03. Routes with
this community value are not advertised outside the local autonomous system or
confederation boundary.
no-advertise—Community with value 4294967042 or hex 0xFFFFFF02. Routes
with this community value are not advertised to any BGP peers.
no-export—Community with value 4294967041 or hex 0xFFFFFF01. Routes with
this community are not advertised to external BGP peers, even if those peers are
in the same confederation with the local router.
Extended community Extended community attributes associated with the path. For known extended
community types, the following codes may be displayed:
RT—Route target community
SoO—Site of Origin community
LB—Link Bandwidth community
Cluster lists Router ID or cluster ID of all route reflectors through which the route has passed.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default subaddress Family Identifier (SAFI) for the current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
315
BGP Commands
show bgp advertised
Command Description
route-policy (BGP), on page 257 Applies a route policy to incoming and outgoing routes.
show bgp policy, on page 409 Displays information about BGP advertisements under a proposed policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
316
BGP Commands
show bgp af-group
configuration (Optional) Displays the effective configuration for the af-group, including any settings that
have been inherited from af-groups used by this af-group.
defaults (Optional) Displays all configuration settings, including any default settings.
inheritance Displays the af-groups from which this af-group inherits configuration settings.
users Displays the neighbors, neighbor groups, and af-groups that inherit configuration from this
af-group.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show bgp af-group command with the group-name configuration argument and keyword to
display the effective configuration of an af-group, taking into account any configuration that may be inherited
from other af-groups through the use af-group command. The source of each command is shown.
If the defaults keyword is specified, all configuration for the af-group, including default values, is shown.
Default configuration is identified in the show output. Use the nvgen keyword to display configuration
formatted in the style of the show running-config command. This output is suitable for cutting and pasting
into configuration sessions.
Use the show bgp af-group command with the group-name inheritance argument and keyword to display
the address family groups from which the specified af-group inherits configuration.
Use the show bgp af-group command with the group-name users argument and keyword to display the
neighbors, neighbor groups, and af-groups that inherit configuration from the specified af-group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
317
BGP Commands
show bgp af-group
bgp read
The following is sample output from the show bgp af-group command with the configuration
keyword in EXEC mode. The source of each command is shown in the right column. For example,
default-originate is configured directly on af-group group1 , and the remove-private-AS
command is inherited from af-group group2, which in turn inherits it from af-group group3.
The following is sample output from the show bgp af-group command with the users keyword:
The following is sample output from the show bgp af-group command with the inheritance
keyword. This example shows that the specified af-group group1 directly uses the group2 af-group,
which in turn uses the group3 af-group:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
318
BGP Commands
show bgp af-group
Table 8: show bgp af-group Field Descriptions, on page 319 describes the significant fields shown
in the display.
This table describes the significant fields shown in the display.
Field Description
[dflt] Indicates the setting is not explicitly configured or inherited, and the default value for the setting
is used. This field may be shown when the defaults keyword is specified.
<not Indicates that the configuration is disabled by default. This field may be shown when the defaults
set> keyword is specified.
show bgp neighbors, on page 366 Displays information about BGP neighbors, including configuration
inherited from neighbor groups, session groups, and address family
groups.
show bgp neighbor-group, on page 362 Displays information about configuration for neighbor groups.
use, on page 524 af-group Configures an af-group to inherit the configuration of a specified
af-group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
319
BGP Commands
show bgp attribute-key
all (Optional) For address family, specifies prefixes for all address families.
all (Optional) For subaddress family, specifies prefixes for all subaddress
families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
320
BGP Commands
show bgp attribute-key
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
bgp read
Examples The following is sample output from the show bgp attribute-keycommand in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
321
BGP Commands
show bgp attribute-key
============================
Field Description
BGP generic scan interval Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer
from which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
322
BGP Commands
show bgp attribute-key
Field Description
Origin codes Origin of the path. The origin code is displayed at the end of each line in the
table. It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was sourced
by BGP using a network or aggregate-address command.
e—Entry originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed
into BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Processed n prefixes, n Number of prefixes and number of paths processed for the table.
paths
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set Sets the default Subaddress Family Identifier (SAFI) for the current session.
default-safi
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
323
BGP Commands
show bgp cidr-only
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used. This command is applicable
only for IPv4 prefixes. If the default address family is not IPv4, then the ipv4 keyword must be used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
324
BGP Commands
show bgp cidr-only
Border Gateway Protocol (BGP) contains a separate routing table for each address family and subaddress
family combination that has been configured. The address family and subaddress family options specify the
routing table to be examined. If the all keyword is specified for subaddress family, all subaddress family
routing tables are examined.
The show bgp cidr-only command applies only for IPv4 prefixes. If the ipv4 keyword is not specified and
the default address family is not IPv4, the command is not available.
Use the show bgp cidr-only command to display CIDR routes. Routes that have their correct class (class
A, B, or C) prefix length are not displayed.
bgp read
Examples The following is sample output from the show bgp cidr-only command in EXEC mode:
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
325
BGP Commands
show bgp cidr-only
Field Description
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was sourced by
BGP using a network or aggregate-address command.
e—Entry originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
326
BGP Commands
show bgp cidr-only
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
327
BGP Commands
show bgp community
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel}] community community-list
[exact-match]
show bgp [ipv6 {unicast}] community community-list [exact-match]
show bgp [all {unicast | multicast | labeled-unicast | all | tunnel}] community community-list
[exact-match]
show bgp [vpnv4 unicast [rd rd-address]] community community-list [exact-match]
show bgp [vrf {vrf-name | all} [{ipv4 | {unicast | labeled-unicast} | ipv6 unicast}]] community
community-list [exact-match]
all (Optional) For subaddress families, specifies prefixes for all subaddress families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address families.
labeled-unicast }
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
328
BGP Commands
show bgp community
community-list Between one and seven communities. Each community can be a number in the
range from 1 to 4294967295, a community specified in AA:NN format, or one of
the following well-known communities:
graceful-shutdown — Reduced preference for shutdown (well-known community)
local-AS —Well-known community with value 4294967043 or hex 0xFFFFFF03.
Routes with this community value are not advertised outside the local autonomous
system or confederation boundary.
no-advertise —Well-known community with value 4294967042 or hex
0xFFFFFF02. Routes with this community value are not advertised to any BGP
peers.
no-export —Well-known community with value4294967041 or hex 0xFFFFFF01.
Routes with this community are not advertised to external BGP peers, even if
those peers are in the same confederation as the local router.
internet —Well-known community whose value is not defined in BGP RFC. IOS
XR BGP uses a value of 0 for the internet community. Routes with this community
are advertised to all peers without any restrictions.
For the AA:NN format:
AA—Range is 0 to 65535.
NN—Range is 1 to 4294967295.
Up to seven community numbers can be specified.
exact-match (Optional) Displays those routes that have communities exactly matching the
specified communities.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
329
BGP Commands
show bgp community
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify the routing table to be examined. If the all keyword
is specified for the address family or the subaddress family, each matching routing table is examined in turn.
If more than seven communities are required, it is necessary to configure a route policy and use the show bgp
route-policy, on page 440 command.
Use the exact-match keyword to display only those routes with a set of communities exactly matching the
list of specified communities. If you omit the exact-match keyword, those routes containing at least the
specified communities are displayed.
bgp read
The following is sample output from the show bgp community graceful-shutdown command
displaying the graceful maintenance feature information:
RP/0/0/CPU0:R4#show bgp community graceful-shutdown
Tue Jan 27 13:36:25.006 PST
BGP router identifier 192.168.0.4, local AS number 4
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0xe0000000 RD version: 18
BGP main routing table version 18
BGP scan interval 60 secs
Examples The following is sample output from the show bgp community command in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
330
BGP Commands
show bgp community
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Status codes Status of the table entry. The status is displayed as a three character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
331
BGP Commands
show bgp community
Field Description
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate
and advertise to its neighbors.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
332
BGP Commands
show bgp convergence
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
333
BGP Commands
show bgp convergence
Border Gateway Protocol (BGP) contains a separate routing table for each configured address family and
subaddress family combination. The address family and subaddress family options specify the routing table
to be examined. If the all keyword is specified for the address family or subaddress family, each matching
routing table is examined in turn.
Use the show bgp convergence command to see if there is any pending work for BGP to perform. The software
checks the following conditions to determine whether the specified address family has converged. If all the
conditions are true, the address family is considered converged.
• All received updates have been processed and best routes selected.
• All selected routes have been installed in the global Routing Information Base (RIB).
• All selected routes have been advertised to peers, including any peers that are not established (unless
those peers have been administratively shut down). See the shutdown (BGP) command for more
information about administrative shutdown.
While testing that all selected routes have been advertised to peers, the show bgp convergencecommand
checks the size of the write queue for each neighbor. Because this queue is shared by all address families,
there is a small possibility that the command indicates the address family has not converged when, in fact, it
has converged. This could happen if the neighbor write queue contained messages from some other address
family.
If the specified address family has not converged, the show bgp convergence command output does not
indicate the amount of work that is pending. To display this information, use theshow bgp summary command.
bgp read
Examples The following shows the result of using the show bgp convergence command for an address family
that has converged:
Converged.
All received routes in RIB, all neighbors updated.
All neighbors have empty write queues.
The following shows the result of using the show bgp convergence command for an address family
that has not converged:
Not converged.
Received routes may not be entered in RIB.
One or more neighbors may need updating.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
334
BGP Commands
show bgp convergence
Field Description
Converged/Not converged Specifies whether or not all routes have been installed in the RIB and updates
have been generated and sent to all neighbors.
[All] Received routes... For convergence, all routes must have been installed into the RIB and all
updates must have been generated. For non-convergence, some routes may
not be installed in the RIB, or some routes that have been withdrawn have
not yet been removed from the RIB, or some routes that are up to date in
the RIB have not been advertised to all neighbors.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
show bgp summary, on page 450 Displays the status of BGP peer connections.
shutdown (BGP), on page 484 Disables a neighbor without removing all of its configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
335
BGP Commands
show bgp dampened-paths
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 {unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
336
BGP Commands
show bgp dampened-paths
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify the routing table to be examined. If the all keyword
is specified for the address family or for the subaddress family, each matching routing table is examined in
turn.
bgp read
Examples The following is sample output from the show bgp dampened-pathscommand in EXEC mode:
Field Description
BGP generic scan interval Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
337
BGP Commands
show bgp dampened-paths
Field Description
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address
family and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the
table. It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Reuse Time (in hours:minutes:seconds) after which the path is made available.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
338
BGP Commands
show bgp dampened-paths
Command Description
bgp dampening, on page 77 Enables BGP route dampening or changes various BGP route
dampening factors.
clear bgp dampening, on page 121 Clears BGP route dampening information and unsuppresses the
suppressed routes.
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate
and advertise to its neighbors.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current
session.
show bgp flap-statistics, on page 340 Displays BGP routes that have flapped.
show bgp neighbors, on page 366 Displays information about the TCP and BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
339
BGP Commands
show bgp flap-statistics
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address families.
labeled-unicast }
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
regexp regular-expression (Optional) Displays flap statistics for all paths that match the regular
expression.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
340
BGP Commands
show bgp flap-statistics
cidr-only (Optional) Displays only routes whose prefix length does not match the
classful prefix length for that network. The cidr-only keyword can be
specified only if the address family is IPv4.
/ prefix-length (Optional) Length of the IP address prefix. A decimal value that indicates
how many of the high-order contiguous bits of the address compose the prefix
(the network portion of the address). A slash (/) must precede the decimal
value.
longer-prefixes (Optional) Displays flap statistics for the specified prefix and more-specific
prefixes. The longer-prefixes keyword is available when the ip-address
and mask or /prefix-length arguments are specified.
detail (Optional) Displays dampening parameters for the path. The detail keyword
cannot be specified if the longer-prefixes keyword is specified. The detail
keyword is available when the ip-address argument or ip-address and
mask or /prefix-length arguments are specified.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify the routing table to be examined. If the all keyword
is specified for the address family or subaddress family, each matching routing table is examined in turn.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
341
BGP Commands
show bgp flap-statistics
Flap statistics are maintained only for paths if dampening is enabled using the bgp dampening command. If
dampening is not enabled, the show bgp flap-statistics command does not display any paths.
If no arguments or keywords are specified, the software displays flap statistics for all paths for the specified
address family. You can use the regexp , filter-list, cidr-only, and longer-prefixes options to limit the set
of paths displayed.
If you specify a network address without a mask or prefix length, the longest matching prefix for the network
address is displayed. When displaying flap statistics for a single route, use the detail keyword to display
dampening parameters for the route.
bgp read
Examples The following is sample output from the show bgp flap-statistics command:
The following is sample output from the show bgp flap-statistics command with the detail keyword
in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
342
BGP Commands
show bgp flap-statistics
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening has been enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address
family and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
343
BGP Commands
show bgp flap-statistics
Field Description
Reuse Time (in hours:minutes:seconds) after which the path is made available.
Half life Half-life value used when dampening this route. The half-life is the amount of time
that must elapse to reduce the reuse penalty by half. The half-life value is specified
using the bgp dampening command.
Suppress Suppress value used to dampen this route. The suppress value is the value that the
penalty must exceed for the route to be suppressed. The suppress value can be
configured using the bgp dampening command.
Reuse penalty Reuse penalty used to dampen this route. The penalty must fall below the reuse
penalty for the route to be unsuppressed. The reuse penalty can be configured using
the bgp dampening command.
Max supp. time Maximum length of time that the route may be suppressed due to dampening. The
maximum suppress time can be configured using the bgp dampening command.
bgp dampening, on page 77 Enables BGP route dampening or changes various BGP route
dampening factors.
set default-afi Sets the default Address Family Identifier (AFI) for the current
session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current
session.
show bgp dampened-paths, on page 336 Displays the BGP dampened routes.
show bgp neighbors, on page 366 Displays information about BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
344
BGP Commands
show bgp inconsistent-as
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel}] inconsistent-as [standby]
show bgp [ipv6 {unicast}] inconsistent-as [standby]
show bgp [all {unicast | multicast | labeled-unicast | all | tunnel}] inconsistent-as [standby]
show bgp vpnv4 unicast [rd rd-address] inconsistent-as [standby]
show bgp [vrf {vrf-name | all} [{ipv4 | {unicast | labeled-unicast} | ipv6 unicast}]] inconsistent-as
[standby]
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
345
BGP Commands
show bgp inconsistent-as
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify the routing table to be examined. If the all keyword
is specified for the address family or for the subaddress family, each matching routing table is examined in
turn.
Use the show bgp inconsistent-ascommand to search through all prefixes in the specified BGP routing table
and display the paths for any prefix that has inconsistent originating autonomous system numbers. The
originating autonomous system is the last autonomous system number displayed in the path field and should
be the same for all paths.
If a prefix has one or more paths originating from different autonomous systems, all paths for that prefix are
displayed.
bgp read
Examples The following is sample output from the show bgp inconsistent-as command in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
346
BGP Commands
show bgp inconsistent-as
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
347
BGP Commands
show bgp inconsistent-as
Field Description
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate
and advertise to its neighbors.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default -safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
348
BGP Commands
show bgp labels
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
ipv4 {unicast | labeled-unicast } (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
349
BGP Commands
show bgp labels
bgp read
Examples The following is sample output from the show bgp labelscommand in EXEC mode:
BGP VRF BAR, state: Active BGP Route Distinguisher: 100:1 BGP router identifier 10.1.1.1,
local AS number 100
BGP table state: Active BGP main routing table version 12
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
350
BGP Commands
show bgp labels
Field Description
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer
from which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the
table. It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was sourced
by BGP using a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed
into BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default subaddress Family Identifier (SAFI) for the current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
351
BGP Commands
show bgp l2vpn
detail Provides detailed output for the specified route distinguisher and BGP prefix.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The following example is sample output from the show bgp l2vpn vpls for route distinguisher 1:1:
RP/0/RSP0/CPU0:router#show bgp l2vpn vpls rd 1:1 2:1
BGP routing table entry for 2:1/32, Route Distinguisher: 1:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 2 2
Local Label: 16000
Paths: (1 available, best #1)
Advertised to update-groups (with more than one peer):
0.1
Advertised to peers (in unique update groups):
100.100.100.1
Path #1: Received by speaker 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
352
BGP Commands
show bgp l2vpn
Local
0.0.0.0 from 0.0.0.0 (200.200.200.1)
Origin IGP, localpref 100, valid, redistributed, best, import-candidate
Extended community: RT:4:4 L2VPN:19:0:1500
Block Size:10
The following example is sample output from the show bgp l2vpn vpws for route distinguisher
200:200:
RP/0/RSP0/CPU0:router#show bgp l2vpn vpws rd 200:200 3:1
BGP routing table entry for 3:1/32, Route Distinguisher: 200:200
Versions:
Process bRIB/RIB SendTblVer
Speaker 6 6
Local Label: 16015
Paths: (1 available, best #1)
Advertised to update-groups (with more than one peer):
0.1
Advertised to peers (in unique update groups):
100.100.100.1
Path #1: Received by speaker 0
Local
0.0.0.0 from 0.0.0.0 (200.200.200.1)
Origin IGP, localpref 100, valid, redistributed, best, import-candidate
Extended community: RT:2:2 L2VPN:4:0:1500
Circuit Vector:0xfd 0xff
Block Size:10
The following example is sample output from the show bgp l2vpn vpls for local NLRI:
RD is 3.3.3.3:3276, NH Address is 100.0.0.1, and VPLS ID is 150:200. The RT is 200:100.
Note The RT and VPLS-ID are always same for the same VPLS instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
353
BGP Commands
show bgp l2vpn
The following example is sample output from the show bgp l2vpn vpls for remote NLRI:
RD is 2.2.2.2:3435, NH Address is 200.0.0.1, and VPLS ID is 150:200. The RT is 200:100.
RP/0/RSP0/CPU0:router#show bgp l2vpn vpls rd 2.2.2.2:3435 200.0.0.1
Sat Jun 6 16:53:55.726 PST
BGP routing table entry for 200.0.0.1, Route Distinguisher: 2.2.2.2:3435
Versions:
Process bRIB/RIB SendTblVer
Speaker 5 5
Last Modified: Jun 6 11:20:57.944 for 05:32:58
Paths: (1 available, best #1)
Not advertised to any peer
Path #1: Received by speaker 0
Local
30.0.0.2 from 30.0.0.2 (133.133.133.133)
Origin IGP, localpref 100, valid, internal, best, import-candidate, imported
Extended community: RT:200:50 VPLS-ID:150:200
The following example is sample output of the show bgp l2vpn evpn command for a Data Center Interconnect
Layer 3 Gateway.
RP/0/RSP0/CPU0:router#show bgp l2vpn evpn
Fri Aug 21 00:24:10.773 PDT
BGP router identifier 30.30.30.30, local AS number 100
BGP generic scan interval 60 secs
Non-stop routing is enabled
BGP table state: Active
Table ID: 0x0 RD version: 0
BGP main routing table version 16
BGP NSR Initial initsync version 1 (Reached)
BGP NSR/ISSU Sync-Group versions 16/0
BGP scan interval 60 secs
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
354
BGP Commands
show bgp l2vpn
*>i[5][4231][112][fec0::1001]/176
11.0.0.1 100 0 i
*>i[5][4232][112][fec0::1:1001]/176
11.0.0.1 100 0 i
The following example is sample output of the show bgp l2vpn evpn rd command for a Data Center
Interconnect Layer 3 Gateway. This sample output provides details for the specified route distinguisher and
prefix.
RP/0/RSP0/CPU0:router# show bgp l2vpn evpn rd 100:1 [5][4231][112][fec0::1001]/176 detail
Fri Aug 21 00:34:43.747 PDT
BGP routing table entry for [5][4231][112][fec0::1001]/176, Route Distinguisher: 100:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 5 5
Flags: 0x04040001+0x00000000;
Last Modified: Aug 21 00:16:58.000 for 00:17:46
Paths: (1 available, best #1)
Not advertised to any peer
Path #1: Received by speaker 0
Flags: 0x4000600025060005, import: 0x3f
Not advertised to any peer
Local
11.0.0.1 (metric 2) from 20.0.0.1 (11.0.0.1)
Received Label 16001
Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate,
reoriginate, not-in-vrf
Received Path ID 0, Local Path ID 1, version 5
Extended community: Flags 0x2: Encapsulation Type:8 Router MAC:aabb.ccdd.eeff RT:65540:1
RT:40.40.40.40:1 RT:100:1
Originator: 11.0.0.1, Cluster list: 20.20.20.20
EVPN ESI: ffff.ffff.ffff.ffff.ff01, Gateway Address : fec0::254
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
355
BGP Commands
show bgp l2vpn vpls
show bgp l2vpn vpls {summary | rd | neighbors | nexthops | bdomain | advertised | process}
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
The following example is sample output from the show bgp l2vpn vpls command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
356
BGP Commands
show bgp l2vpn vpls
The following example is sample output from the show bgp l2vpn vpls command with the summary
keyword:
The following example is sample output from the show bgp l2vpn vpls command for Route
Distinguisher: 101:1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
357
BGP Commands
show bgp l2vpn vpls
The following example is sample output from the show bgp l2vpn vpls command for BGP neighbor
10.10.10.10:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
358
BGP Commands
show bgp l2vpn vpls
The following example is sample output from the show bgp l2vpn vpls command with the advertised
keyword:
The following example is sample output from the show bgp l2vpn vpls command with the nexthops
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
359
BGP Commands
show bgp l2vpn vpls
The following example is sample output from the show bgp l2vpn vpls command with the process
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
360
BGP Commands
show bgp l2vpn vpls
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
361
BGP Commands
show bgp neighbor-group
configuration (Optional) Displays the effective configuration for the neighbor group, including any
configuration inherited by this neighbor group.
inheritance Displays the af-groups, session groups, and neighbor groups from which this neighbor group
inherits configuration.
users Displays the neighbors and neighbor groups that inherit configuration from this neighbor
group.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show bgp neighbor-group command with the group-name configuration argument and keyword
to display the effective configuration of a neighbor group, including any configuration inherited from session
groups, address family groups, and neighbor groups through application of the use command. The source of
each configured command is also displayed.
Use the defaults keyword to display all configuration for the neighbor group, including default configuration.
The command output identifies default onfiguration. Use the nvgen keyword to display configuration in the
output form of show running-configcommand. Output in this form is suitable for cutting and pasting into a
configuration session.
Theshow bgp neighbor-group command with the group-name inheritance argument and keyword displays
the session groups, address family groups, and neighbor groups from which the specified neighbor group
inherits configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
362
BGP Commands
show bgp neighbor-group
The show bgp neighbor-group group-name command displays the neighbors and neighbor groups that inherit
configuration from the specified neighbor group.
bgp read
The following is sample output from the show bgp neighbor-group command with the configuration
keyword:
neighbor-group group1
remote-as 1982 []
timers 30 90 [n:group2 n:group3]
dmzlink-bw [n:group2 n:group3 s:group3]
address-family ipv4 unicast []
capability orf prefix both [n:group2 a:group2]
remove-private-AS [n:group2 a:group2 a:group3]
send-community-ebgp [n:group2 a:group2]
send-extended-community-ebgp [n:group2 a:group2]
soft-reconfiguration inbound [n:group2 a:group2 a:group3]
weight 100 [n:group2]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
363
BGP Commands
show bgp neighbor-group
The configuration source is shown to the right of each command. In the output, the remote-as
command is configured directly on neighbor group group1, and the send-community-ebgp command
is inherited from neighbor group group2, which in turn inherits the setting from af-group group2.
The following is sample output from the show bgp neighbor-group command with the users
keyword. This output shows that the group1 neighbor group inherits session (address
family-independent configuration parameters) from the group2 neighbor group. The group1 neighbor
group also inherits IPv4 unicast configuration parameters from the group2 neighbor group:
Session: n:group1
IPv4 Unicast: n:group1
The following is sample output from the show bgp neighbor-group command with the inheritance
keyword. This output shows that the specified neighbor group group1 inherits session (address
family-independent configuration) from neighbor group group2, which inherits its own session from
neighbor group group3. Neighbor group group3 inherited its session from session group group3. It
also shows that the group1 neighbor-group inherits IPv4 unicast configuration parameters from the
group2 neighbor group, which in turn inherits them from the group2 af-group, which itself inherits
them from the group3 af-group:
Field Description
[dflt] Indicates the setting is not explicitly configured or inherited, and the default value for the setting
is used. This field may be shown when the defaults keyword is specified.
<not Indicates that the default is for the setting to be disabled. This field may be shown when the
set> defaults keyword is specified.
session-group, on page 276 Creates a session group and enters session group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
364
BGP Commands
show bgp neighbor-group
Command Description
show bgp af-group, on page 317 Displays information about configuration for address family groups.
show bgp neighbors, on page 366 Displays information about BGP neighbors, including configuration
inherited from neighbor groups, session groups, and address family
groups.
show bgp session-group, on page 444 Displays information about the BGP configuration for session groups.
show running-config Displays the contents of the currently running configuration or a subset
of that configuration.
use, on page 524 Inherits configuration from a neighbor group, a session group, or an
address family group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
365
BGP Commands
show bgp neighbors
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
missing-eor (Optional) Displays neighbors that did not send end-of-rib (EoR) notification
in read-only mode.
advertised-routes (Optional) Displays all routes the router advertised to the neighbor.
dampened-routes (Optional) Displays the dampened routes that are learned from the neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
366
BGP Commands
show bgp neighbors
flap-statistics (Optional) Displays flap statistics of the routes learned from the neighbor.
received { prefix-filter | (Optional) Displays information received from the BGP neighbor. The
routes } options are:
prefix-filter— Displays the prefix list filter.
routes—Displays routes from the neighbor before inbound policy
configuration (Optional) Displays the effective configuration for the neighbor, including
any settings that have been inherited from session groups, neighbor groups,
or af-groups used by this neighbor.
defaults (Optional) Displays all configuration settings, including any default settings.
inheritance (Optional) Displays the session groups, neighbor groups, and af-groups
from which this neighbor inherits configuration settings.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Release 3.9.0 Asplain format for 4-byte autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.1.1 The command output was modified to display from BGP Accept Own configuration.
Release 4.0.0 The command output was modified to include information on BGP additional paths send and
receive information.
Release 4.3.0 The command output was modified to include information from update wait-install
configuration.
Release 5.1.1 The command output was modified to display the status of permanent paths.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
367
BGP Commands
show bgp neighbors
Release Modification
Release 5.2.2 The command output was modified to display the following:
• BGP Monitoring Protocol (BMP) information.
• BGP Persistence or long lived graceful restart (LLGR) status.
Release 5.3.2 The command was modified to include graceful maintenance feature information.
Release 5.3.2 The command output was modified display TCP MSS information.
Usage Guidelines
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify which routing table should be examined. If the all
keyword is specified for address family or subaddress family, each matching routing table is examined in
turn.
Use the show bgp neighbors command to display detailed information about all neighbors or a specific
neighbor. Use the performance-statistics keyword to display information about the work related to specific
neighbors done by the BGP process.
Use the show bgp neighbors command with the ip-address received prefix-filter argument and keyword
to display the Outbound Route Filter (ORF) received from a neighbor.
Use the advertised-routes keyword to display a summary of the routes advertised to the specified neighbor.
Use the dampened-routes keyword to display routes received from the specified neighbor that have been
suppressed due to dampening. For more details, see the show bgp dampened-paths command.
To display information about flapping routes received from a neighbor, use the flap-statistics keyword. For
more details, see the show bgp flap-statistics command.
To display the routes received from a neighbor, use the routes keyword. For more details, see the show
bgp command.
Use the show bgp neighbor command with the ip-address configuration argument and keyword to display
the effective configuration of a neighbor, including configuration inherited from session groups, neighbor
groups, or af-groups through application of the use command. Use the defaults keyword to display the
value of all configurations for the neighbor, including default configuration. Use the nvgen keyword to
display configuration output format of the show running-config command. Output in this format is suitable
for cutting and pasting into a configuration session. Use the show bgp neighbors command with the
ip-address inheritance argument and keyword to display the session groups, neighbor groups, and af-groups
from which the specified neighbor inherits configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
368
BGP Commands
show bgp neighbors
bgp read
The following is the sample output from the show bgp neighbors command with the ip-address
and configuration argument and keyword to display graceful maintenance feature attributes:
**************************************************************************
**************************************************************************
**************************************************************************
Examples The following is the sample output from the show bgp neighbors command with BGP Persistence
or long lived graceful restart (LLGR) status:
RP/0/RSP0/CPU0:router# show bgp neighbors 3.3.3.3
BGP neighbor is 3.3.3.3
Remote AS 30813, local AS 30813, internal link
Remote router ID 3.3.3.3
BGP state = Established, up for 2d19h
NSR State: NSR Ready
BFD enabled (initializing)
Last read 00:00:01, Last read before reset 2d19h
Hold time is 180, keepalive interval is 60 seconds
Configured hold time: 180, keepalive: 60, min acceptable hold time: 3
Last write 00:00:03, attempted 19, written 19
Second last write 00:01:03, attempted 19, written 19
Last write before reset 2d19h, attempted 19, written 19
Second last write before reset 2d19h, attempted 19, written 19
Last write pulse rcvd Nov 19 09:24:38.035 last full not set pulse count 66013
Last write pulse rcvd before reset 2d19h
Socket not armed for io, armed for read, armed for write
Last write thread event before reset 2d19h, second last 2d19h
Last KA expiry before reset 2d19h, second last 2d19h
Last KA error before reset 00:00:00, KA not sent 00:00:00
Last KA start before reset 2d19h, second last 2d19h
Precedence: internet
Non-stop routing is enabled
Graceful restart is enabled
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
369
BGP Commands
show bgp neighbors
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
370
BGP Commands
show bgp neighbors
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
371
BGP Commands
show bgp neighbors
The following is sample output from the show bgp neighbors command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
372
BGP Commands
show bgp neighbors
Field Description
BGP neighbor IP address of the BGP neighbor and its autonomous system number. If
the neighbor is in the same autonomous system as the router, then the link
between them is internal; otherwise, it is considered external.
Administratively shut down Neighbor connection is disabled using the shutdown command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
373
BGP Commands
show bgp neighbors
Field Description
TCP open mode TCP mode used in establishing the BGP session. The following valid
TCP mode are supported:
• default—Accept active/passive connections
• passive-only—Accept only passive connections
• active-only—Accept only active connections initiated by the router
Last read Time since BGP last read a message from this neighbor.
hold time Hold time (in seconds) used on the connection with this neighbor.
Neighbor capabilities BGP capabilities advertised and received from this neighbor. The
following valid BGP capabilities are supported:
• Multi-protocol
• Route refresh
• Graceful restart
• Outbound Route Filter (ORF) type (128) Prefix
Route refresh Indicates that the neighbor supports dynamic soft reset using the route
refresh capability.
Address family Indicates that the local system supports the displayed address family
capability. If “received” is displayed, the neighbor also supports the
displayed address family.
Minimum time between Advertisement interval (in seconds) for this neighbor.
advertisement runs
For Address Family Information that follows is specific to the displayed address family.
BGP neighbor version Last version of the BGP database that was sent to the neighbor for the
specified address family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
374
BGP Commands
show bgp neighbors
Field Description
Route reflector client Indicates that the local system is acting as a route reflector for this
neighbor.
Inbound soft reconfiguration Indicates that soft reconfiguration is enabled for routes received from this
allowed neighbor.
Note If the neighbor has route refresh capability, then soft
configuration received-only routes are not stored by the local
system unless “override route refresh” is displayed.
eBGP neighbor with no inbound Indicates that the neighbor does not have an inbound or outbound policy
or outbound policy: defaults to configured using the route-policy (BGP) command. Hence, no routes
drop are accepted from or advertised to this neighbor.
Private AS number removed from Indicates that remove-private-AS is configured on the specified address
updates to this neighbor family for this neighbor.
NEXT_HOP is always this router Indicates that next-hop-self is configured on the specified address family
for this neighbor.
Community attribute sent to this Indicates that send-community-ebgp is configured on the specified address
neighbor family for this neighbor.
Default information originate Indicates that default-originate is configured on the specified address
family for this neighbor, together with the policy used, if one was specified
in the default-originate configuration. An indication of whether the default
route has been advertised to the neighbor is also shown.
AF-dependant capabilities BGP capabilities that are specific to a particular address family. The
following valid AF-dependent BGP capabilities are supported:
• route refresh capability
• route refresh capability OLD value
Outbound Route Filter Neighbor has the Outbound Route Filter (ORF) capability for the specified
address family. Details of the capabilities supported are also shown:
Send-mode—“advertised” is shown if the local system can send an
outbound route filter to the neighbor. “received” is shown if the neighbor
can send an outbound route filter to the local system.
Receive-mode—“advertised” is shown if the local system can receive an
outbound route filter from the neighbor. “received” is shown if the
neighbor can receive an outbound route filter from the local system.
Graceful Restart Capability Indicates whether graceful restart capability has been advertised to and
received from the neighbor for the specified address family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
375
BGP Commands
show bgp neighbors
Field Description
Neighbor preserved the Indicates that when the neighbor connection was last established, the
forwarding state during latest neighbor indicated that it preserved its forwarding state for the specified
restart address family.
Local restart time Restart time (in seconds) advertised to this neighbor.
RIB purge time RIB purge time (in seconds) used for graceful restarts.
Maximum stalepath time Maximum time (in seconds) a path received from this neighbor may be
marked as stale if the neighbor restarts.
Route refresh request Number of route refresh requests sent and received from this neighbor.
Outbound Route Filter (ORF) “sent” indicates that an outbound route filter has been sent to this neighbor.
“received” indicates that an outbound route filter has been received from
this neighbor.
Note A received outbound route filter may be displayed using the
show bgp neighbors command with the received prefix-filter
keywords.
First update is deferred until ORF If the local system advertised the receive capability and the neighbor has
or ROUTE-REFRESH is received advertised send capability, no updates are generated until specifically
asked by the neighbor (using a ROUTE-REFRESH or ORF with
immediate request).
Scheduled to send the Prefix-list Indicates the local system is due to send an outbound route filter request
filter in order to receive updates from the neighbor.
Incoming update prefix filter list Indicates a prefix list is configured to filter inbound updates from the
neighbor.
Default weight Default weight for routes received from the neighbor.
Policy for incoming Indicates a route policy is configured to be applied to inbound updates
advertisements from the neighbor.
Policy for outgoing Indicates a route policy is configured to be applied to outbound updates
advertisements to the neighbor.
Type Indicates whether the condition map selects routes that should be
advertised, or routes that should not be advertised:
Exist—Routes advertised if permitted by the condition route map.
Non-exist—Routes advertised if denied by the condition route map.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
376
BGP Commands
show bgp neighbors
Field Description
Prefix advertised Number of prefixes advertised to the neighbor during the lifetime of the
current connection with the neighbor.
withdrawn Number of prefixes withdrawn from the neighbor during the lifetime of
the current connection with the neighbor.
maximum limit Maximum number of prefixes that may be received from the neighbor.
If “(warning-only)” is displayed, a warning message is generated when
the limit is exceeded, otherwise the neighbor connection is shut down
when the limit is exceeded.
Threshold for warning message Percentage of maximum prefix limit for the neighbor at which a warning
message is generated.
Connections established Number of times the router has established a BGP peering session with
the neighbor.
dropped Number of times that a good connection has failed or been taken down.
Last reset due to Reason that the connection with the neighbor was last reset.
Time since last notification sent Amount of time since a notification message was last sent to the neighbor.
to neighbor
Error Code Type of notification that was sent. The notification data, if any, is also
displayed.
Time since last notification Amount of time since a notification message was last received from the
received from neighbor neighbor.
Error Code Type of notification that was received. The notification data received, if
any, is also displayed
External BGP neighbor may be Indicates ebgp-multihop is configured for the neighbor.
up to <n> hops away
External BGP neighbor not Indicates that the neighbor is not directly attached to the local system.
directly connected
Notification data sent: Data providing more details on the error along with the error notification
sent to the neighbor.
The following is sample output from the show bgp neighbors command with the advertised-routes
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
377
BGP Commands
show bgp neighbors
The following is sample output from the show bgp neighbors command with the routes keyword:
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
378
BGP Commands
show bgp neighbors
Field Description
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
The following is sample output from the show bgp neighbors command with the dampened-routes
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
379
BGP Commands
show bgp neighbors
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address
family and subaddress family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
380
BGP Commands
show bgp neighbors
Field Description
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Reuse Time (in hours:minutes:seconds) after which the path is made available.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
The following is sample output from the show bgp neighbors command with the flap-statistics
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
381
BGP Commands
show bgp neighbors
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening has been enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between when the BGP process scans for the specified
address family and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but
that is being maintained to preserve dampening information. Such routes should
never be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
382
BGP Commands
show bgp neighbors
Field Description
Duration Time (in hours:minutes:seconds) since the router noticed the first flap.
Reuse Time (in hours:minutes:seconds) after which the path is made available.
The following is sample output from the show bgp neighbors command with the
performance-statistics keyword:
Field Description
Read Indicates the number of messages received from the neighbor, the total size of
received messages, the number of read operations performed, and the real time spent
(in seconds) by the process performing read operations for this neighbor.
Read throttled Number of times that reading from the TCP connection to this neighbor has been
throttled. Throttling is due to a backlog of messages that have been read but not
processed.
inbound messages Number of read messages that have been processed, and the real time spent processing
inbound messages for this neighbor.
Wrote Amount of data that has been sent to this neighbor, number of write operations
performed, and the real time spent by the process performing write operations for
this neighbor.
Processing write list Number of messages written from the write list to this neighbor, number of times
the write list has been processed, and real time spent processing the write list.
Note Write lists typically contain only update messages.
Processing write queue Number of messages written from the write queue to this neighbor, number of times
the write queue has been processed, and real time spent processing the write queue.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
383
BGP Commands
show bgp neighbors
Field Description
Received Number of messages received from this neighbor, number of notification messages
received and processed from this neighbor, and number of messages that have been
received, but not yet processed.
Sent Number of messages sent to this neighbor, number of notification messages generated
to be sent to this neighbor, and number of messages queued to be sent to this neighbor.
The following is sample output from the show bgp neighbors command with the configuration
keyword:
neighbor 10.0.101.1
remote-as 2 []
bfd fast-detect []
address-family ipv4 unicast []
policy pass-all in []
policy pass-all out []
address-family ipv4 multicast []
policy pass-all in []
policy pass-all out []
Field Description
address-family Address family and subsequent address family configured on the router.
The following sample output shows sample output from show bgp neighbors command with
additional paths send and receive capabilities advertised to neighbors:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
384
BGP Commands
show bgp neighbors
AF-dependant capabilities:
Graceful Restart capability advertised and received
Neighbor preserved the forwarding state during latest restart
Local restart time is 120, RIB purge time is 600 seconds
Maximum stalepath time is 360 seconds
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
385
BGP Commands
show bgp neighbors
This is sample output of the show bgp neighbors command when update wait-install is enabled. If
the session open is postponed due to the reloading of the LC/FIB, the text "LC/FIB for the nieghobr
in reloading" is displayed next to the BGP state.
This is sample output from show bgp neighbors command that displays status of Accept Own
configuration:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
386
BGP Commands
show bgp neighbors
This sample output from the show bgp neighbor command displays the status of permanent paths:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
387
BGP Commands
show bgp neighbors
The following is sample output from the show bgp neighbors command displaying BGP Monitoring
Protocol (BMP) information:
The following is sample output from the show bgp neighbors command displaying BGP Persistence
or long lived graceful restart (LLGR) status:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
388
BGP Commands
show bgp neighbors
This sample output from the show bgp neighbor command displays TCP MSS information for the
specified neighbor:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
389
BGP Commands
show bgp neighbors
This sample output from the show bgp neighbor command with the configuration keyword displays
TCP MSS configuration:
neighbor 10.0.0.2
remote-as 1 []
tcp-mss 400 [n:n1]
address-family IPv4 Unicast []
network (BGP), on page 208 Specifies a local network that the BGP routing process should
originate and advertise to its neighbors.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from
a BGP neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current
session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current
session.
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp flap-statistics, on page 340 Displays BGP routes that have flapped.
show bgp neighbor-group, on page 362 Displays information about the BGP configuration for neighbor
groups.
shutdown (BGP), on page 484 Disables a neighbor without removing all of its configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
390
BGP Commands
show bgp neighbors nsr
show bgp [{ipv4 {unicast | multicast | all} | ipv6 {unicast | multicast | all} | vpnv4 unicast | vpnv6
unicast | vrf {allvrf_name}}] neighbors nsr [standby]
all (Optional) For address family, specifies prefixes for all address families.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
Examples The following is sample output from the show bgp neighbors nsr command with the standby
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
391
BGP Commands
show bgp neighbors nsr
Field Description
nsr (BGP), on page 222 Activates the Border Gateway Protocol (BGP) nonstop routing (NSR).
show bgp summary nsr, on page 454 Displays the Border Gateway Protocol (BGP) nonstop routing (NSR)
information.
show bgp summary, on page 450 Displays the status of all Border Gateway Protocol (BGP) connections.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
392
BGP Commands
show bgp nexthops
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
393
BGP Commands
show bgp nexthops
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The show bgp nexthops command displays statistical information about next-hop notifications, the time spent
processing the notifications, and details about each next-hop that has been registered with the Routing
Information Base (RIB).
Use the vrf vrf-name keyword and argument to display only the next-hops present in the specified VPN
routing and forwarding (VRF) instance.
The next-hop information is displayed for all active speaker processes in distributed mode. Each speaker
displays a set of next-hops that belongs to the prefixes received by the speaker and next hops that belong to
best paths that were received by other speaker processes. Use the speaker speaker-id keyword and argument
to display information for only the specified speaker process.
bgp read
Examples The following is sample output from the show bgp nexthops command with the VRF specified:
VRF: 900
========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
394
BGP Commands
show bgp nexthops
VRF: 901
========
VRF: 902
========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
395
BGP Commands
show bgp nexthops
VRF: 903
========
VRF: 904
========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
396
BGP Commands
show bgp nexthops
VRF: 905
========
VRF: 906
========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
397
BGP Commands
show bgp nexthops
Received: 1d22h
Time Spent: 0.000 secs
VRF: 907
========
VRF: 908
========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
398
BGP Commands
show bgp nexthops
Received: 82y48w
Bestpaths Deleted: 0
Bestpaths Changed: 0
Time Spent: 0.000 secs
VRF: 909
========
VRF: yellow
===========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
399
BGP Commands
show bgp nexthops
Field Description
Total Nexthop Processing Time Spent Time spent processing trigger delays for critical and noncritical
events for the VRF or address family. The time is specified in
seconds.
Maximum Nexthop Processing Time that has passed since the nexthop notification was received
that resulted in spending the maximum amount of processing time
for all notifications.
Last Notification Processing Time that has passed since the last nexthop notification was
received.
IPv4 Unicast is active. VRF specified output that indicates the IPv4 unicast address family
is active within the VRF.
Nexthop Count Number of next hops for the VRF or address family.
Bestpaths Deleted After Last Walk Number of best paths deleted due to the last notification.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
400
BGP Commands
show bgp nexthops
Field Description
Bestpaths Changed After Last Walk Number of best paths modified due to the last notification.
LastRIBEvent When the last notification was received from the RIB.
RefCount The number of neighbors or prefixes that refer to the next hop in
address family/all format.
bgp redistribute-internal, on page 98 Specifies the delay for triggering BGP next-hop calculations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
401
BGP Commands
show bgp nsr
show bgp [{ipv4 {unicast | multicast | labeled-unicast | all | tunnel} | ipv6 {unicast | multicast | all |
labeled-unicast} | all {unicast | multicast | all | labeled-unicast | tunnel} | vpnv4 unicast | vrf {vrf-name
| all} [{ipv4 {unicast | labeled-unicast} | ipv6 unicast}] | vpvn6 unicast}] nsr [standby]
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
402
BGP Commands
show bgp nsr
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
Examples The following is sample output from the show bgp nsr command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
403
BGP Commands
show bgp nsr
Current BGP NSR state - NSR Ready achieved at: Jan 30 10:00:44
NSR State READY notified to Redcon at: Jan 30 10:16:58
QAD Statistics:
Postit Summary:
The following example shows sample output from the show bgp nsr command with the standby
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
404
BGP Commands
show bgp nsr
QAD Statistics:
Postit Summary:
nsr (BGP), on page 222 Activates Border Gateway Protocol (BGP) nonstop routing (NSR).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
405
BGP Commands
show bgp paths
debug (Optional) Displays attribute process ID, hash bucket, and hash chain ID
attribute information.
regexp regular-expression (Optional) Specifies an autonomous system path that matches the regular
expression.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show bgp paths command to display information about AS paths and the associated attributes with
which the paths were received.
If no options are specified, all stored AS paths are displayed with the number of routes using each path.
Note The AS path information is stored independently of the address family, making it possible that routes from
different address families could be using the same path.
Use the regular-expression argument to limit the output to only those paths that match the specified regular
expression. See the Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide for information
on regular expressions.
Use the detail keyword to display detailed information on the attributes stored with the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
406
BGP Commands
show bgp paths
bgp read
Examples The following is sample output from the show bgp paths command:
Field Description
Proc ID of the process in which the path is stored. This is always “Spk 0.”
NeighborAS Autonomous system number of the neighbor, or 0, if the path information originated locally.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
Metric Value of the interautonomous system metric, otherwise known as the MED metric.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
407
BGP Commands
show bgp paths
Field Description
Path Autonomous system path to the destination network. At the end of the path is the origin code
for the path:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised with a network
or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into BGP from
an IGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
408
BGP Commands
show bgp policy
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
sent-advertisements (Optional) Displays the routes that have been advertised to neighbors. If
a route has not yet been advertised to the neighbor, it is not shown.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
409
BGP Commands
show bgp policy
Command Default Advertisements for all neighbors are displayed if the neighbor ip-address keyword and argument are not
specified. If no address family or subaddress family is specified, the default address family and subaddress
family specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routersfor detailed information and syntax for
the set default-afi and set default-safi commands. If you do not specify a default address family, the default
address family is IPv4. If you do not specify a default subaddress family, the default subaddress family is
unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify the routing table to be examined. If the all keyword
is specified for the address family or subaddress family, each matching routing table is examined in turn.
Use the show bgp policy command to display routes that would be advertised to neighbors under a proposed
policy. Unlike in the show bgp advertised command, the information displayed reflects any modifications
made to the routes when executing the specified policy.
Use the neighbor keyword to limit the output to routes advertised to a particular neighbor. Use the
sent-advertisements keyword to change the output in two ways:
• If a policy is not specified explicitly, any policy configured on the neighbor (using the route-policy
(BGP) command) is executed before displaying the routes.
• Only routes that have already been advertised to the neighbor (and not withdrawn) are displayed. Routes
that have not yet been advertised are not displayed.
Use the summary keyword to display abbreviated output.
bgp read
Examples The following is sample output from the show bgp policy command with the summary keyword
in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
410
BGP Commands
show bgp policy
Field Description
Next Hop IP address of the next system that is used when a packet is forwarded to the destination
network. An entry of 0.0.0.0 indicates that the router has a non-BGP route to this network.
The following is sample output from the show bgp policy command in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
411
BGP Commands
show bgp policy
aspath:
Field Description
Is advertised to IP address of the peer to which this route is advertised. If the route is advertised
to multiple peers, information is shown separately for each peer.
neighbor IP address of the peer that advertised this route, or one of the following:
Local—Route originated on the local system.
Local Aggregate—Route is an aggregate created on the local system.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
412
BGP Commands
show bgp policy
Field Description
neighbor router id BGP identifier for the peer, or the local system if the route originated on the local
system.
Not advertised to any Indicates the no-advertise well-known community is associated with this route.
peer Routes with this community are not advertised to any BGP peers.
Not advertised to any Indicates the no-export well-known community is associated with this route. Routes
EBGP peer with this community are not advertised to external BGP peers, even if those peers
are in the same confederation as the local router.
Not advertised outside Indicates the local-AS well-known community is associated with this route. Routes
the local AS with this community value are not advertised outside the local autonomous system
or confederation boundary.
(received-only) Path is not used for routing purposes. It is used to support soft reconfiguration, and
records the path attributes before inbound policy was applied to a path received
from a peer. A path marked “received-only” indicates that either the path was
dropped by inbound policy, or that a copy of path information was created and
then modified for routing use.
(received & used) Indicates that the path is used both for soft reconfiguration and routing purposes.
A path marked “(received & used)”, implies the path information was not modified
by inbound policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
413
BGP Commands
show bgp policy
Field Description
Attributes after inbound Displays attributes associated with the received route, after any inbound policy
policy was applied has been applied.
AGG—Aggregator attribute is present.
AS—AS path attribute is present.
ATOM—Atomic aggregate attribute is present.
COMM—Communities attribute is present.
EXTCOMM—Extended communities attribute is present.
LOCAL—Local preference attribute is present.
MET—Multi Exit Discriminator (MED) attribute is present.
next hop—IP address of the next system used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
ORG—Origin attribute is present.
aggregator Indicates that the path was received with the aggregator attribute. The AS number
and router-id of the system that performed the aggregation are shown.
metric Value of the interautonomous system metric, otherwise known as the MED metric.
localpref Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system
community Community attributes associated with the path. Community values are displayed
in AA:NN format, except for the following well-known communities:
Local-AS—Community with value 4294967043 or hex 0xFFFFFF03. Routes with
this community value are not advertised outside the local autonomous system or
confederation boundary.
no-advertise—Community with value 4294967042 or hex 0xFFFFFF02. Routes
with this community value are not advertised to any BGP peers.
no-export—Community with value 4294967041 or hex 0xFFFFFF01. Routes with
this community are not advertised to external BGP peers, even if those peers are
in the same confederation as the local router.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
414
BGP Commands
show bgp policy
Field Description
Extended community Extended community attributes associated with the path. For known extended
community types, the following codes may be displayed:
RT—Route target community
SoO—Site of Origin community
LB—Link Bandwidth community
Cluster lists Router ID or cluster ID of all route reflectors through which the route has passed.
Attributes after Displays attributes associated with the received route, after any outbound policy
outbound policy was has been applied.
applied
AGG—Aggregator attribute is present.
AS—AS path attribute is present.
ATOM—Atomic aggregate attribute is present.
COMM—Communities attribute is present.
EXTCOMM—Extended communities attribute is present.
LOCAL—Local preference attribute is present.
MET—Multi Exit Discriminator (MED) attribute is present.
next hop—IP address of the next system used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
ORG—Origin attribute is present.
route-policy (BGP), on page 257 Applies an inbound or outbound routing policy to a neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current
session.
show bgp neighbors, on page 366 Displays information about the TCP and BGP connections to neighbors.
show bgp route-policy, on page 440 Displays BGP information about networks that match an outbound route
policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
415
BGP Commands
show bgp process
show bgp [{ipv4 | {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 | {unicast | multicast
| all | labeled-unicast} | all | {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast |
vpvn6 unicast}] process [performance-statistics] [detail]
all (Optional) For subaddress families, specifies prefixes for all subaddress families.
all (Optional) For address family, specifies prefixes for all address families.
performance- statistics (Optional) Displays performance statistics relative to the work done by the
specified process.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Release 3.9.0 Asplain format for 4-byte autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.0 The command output was modified to include information from BGP additional paths send
and receive capability configurations.
Release 4.3.0 The command output was modified to include information from update wait-install
configuration.
Release 5.3.2 The command output was modified to include graceful maintenance feature information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
416
BGP Commands
show bgp process
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
Use the show bgp process command to display status and summary information for the Border Gateway
Protocol (BGP) process. The output shows various global and address family-specific BGP configurations.
A summary of the number of neighbors, update messages, and notification messages sent and received by the
process is also displayed.
Use the detail keyword to display detailed process information. The detailed process information shows the
memory used by each of various internal structure types.
Use the performance-statistics keyword to display a summary or detail of work done by the BGP processes.
The summary display shows the real time spent performing certain operations and the time stamps for state
transitions during initial convergence.
bgp read
Examples The following is sample output from the show bgp process command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
417
BGP Commands
show bgp process
node0_0_CPU0 Speaker 3 2 1 20 10 0 0
Field Description
BGP is operating in Indicates BGP is operating in standalone mode. This is the only supported
mode.
Router ID BGP identifier assigned to the local system. If this is explicitly configured
using the bgp router-id command, “manually configured” is displayed. If
the router ID is not manually configured, it is determined from a global router
ID. If no global ID is available, the router ID is shown as 0.0.0.0.
Cluster ID Cluster identifier for the local system. If this is manually configured using
the bgp cluster-id command, “manually configured” is displayed.
Fast external fallover enabled Indicates whether fast external fallover is enabled. This is controlled by the
bgp fast-external-fallover disable command.
Neighbor logging enabled Indicates whether logging of peer connection up and down transitions is
enabled. This is controlled by the bgp log neighbor changes disable
command.
Enforce first AS enabled Indicates that strict checking of the first AS number in paths received from
external BGP peers is enabled. This is controlled by the bgp enforce-first-as
disable command.
iBGP to IGP redistribution Indicates internal redistribution is enabled using the bgp
redistribution-internal command.
Treating missing MED as Indicates missing Multi Exit Discriminator (MED) metric values are treated
worst as worst in the route selection algorithm. This is controlled by the bgp
bestpath med missing-as-worst command.
Always compare MED is Indicates that the MED is always used during the route selection algorithm,
enabled even when paths are received from external BGP neighbors in different
autonomous systems. This is controlled by the bgp bestpath med always
command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
418
BGP Commands
show bgp process
Field Description
AS Path ignore is enabled Indicates that the AS path length is ignored by the route selection algorithm.
This is controlled by the bgp bestpath as-path ignore command.
Comparing MED from Indicates that the MED values are used in the route selection algorithm when
confederation peers comparing routes received from confederation peers. This is controlled by
the bgp bestpath med confed command.
Comparing router ID for Indicates that the router ID is used as a tiebreaker by the route selection
eBGP paths algorithm when comparing identical routes received from different external
BGP neighbors. This is controlled by the bgp bestpath compare-routerid
command.
Default local preference Default local preference value used for BGP routes. This is controlled by the
bgp default local-preference command.
Default keepalive Default keepalive interval. This is controlled by the timers bgp command.
Graceful restart enabled Indicates that the graceful restart capability is enabled. The configuration
commands affecting graceful restart behavior are:
• bgp graceful-restart
• bgp graceful-restart purge-time
• bgp graceful-restart stalepath-time
• bgp graceful-restart restart-time
• bgp graceful-restart graceful-reset
Update delay Maximum time that a BGP process stays in read-only mode.
Generic scan interval Interval (in seconds) between BGP scans for address family-independent
tasks. This is controlled by the bgp scan-time command.
Dampening Indicates whether dampening is enabled for the specified address family. This
is controlled by the dampening command.
Client reflection Indicates whether client-to-client route reflection is enabled for the specified
address family. This is controlled by the bgp client-to-client reflection
disable command.
Scan interval Interval (in seconds) between BGP scans for the given address family. This
is controlled by the bgp scan-time command in address family configuration
mode.
Main Table Version Last version of the BGP database that was installed into the main routing
table.
IGP notification Indicates whether Interior Gateway Protocols (IGP) have been notified of
BGP convergence for the specified address family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
419
BGP Commands
show bgp process
Field Description
Estab Number of neighbors that have connections in the established state for this
process.
The following is sample output from the show bgp process command with the Graceful Maintenance
feature enabled:
RP/0/0/CPU0:R1#show bgp process
...
Graceful Maintenance active. Retaining routes in RIB during BGP shutdown
...
Or
Graceful Maintenance active for all neighbors. Retaining routes in RIB during BGP shutdown
**************************************************************************
The following is sample output from the show bgp process command with the detail keyword:
Sent Received
Updates: 3 15
Notifications: 0 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
420
BGP Commands
show bgp process
Allocated Freed
Prefixes: 15 0
Paths: 19 0
Field Description
Router ID BGP identifier assigned to the local system. If this is explicitly configured
using the bgp router-id command, “manually configured” is displayed. If
the router ID is not manually configured, it is determined from a global router
ID. If the global ID is not available, the router ID is shown as 0.0.0.0.
Cluster ID Cluster identifier for the local system. If this is manually configured using
the bgp cluster-id command, “manually configured” is displayed.
Fast external fallover enabled Indicates whether fast external fallover is enabled.
Neighbor logging enabled Indicates whether logging of peer connection up and down transitions is
enabled.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
421
BGP Commands
show bgp process
Field Description
Enforce first AS enabled Indicates that strict checking of the first autonomous system (AS) number
in paths received from external BGP peers is enabled.
iBGP to IGP redistribution Indicates internal redistribution is enabled using the bgp
redistribution-internal command.
Treating missing MED as Indicates missing MED metric values are treated as worst in the route
worst selection algorithm. This is controlled by the bgp bestpath med
missing-as-worst command.
Always compare MED is Indicates that the MED is always used during the route selection algorithm,
enabled even when paths are received from external BGP neighbors in different
autonomous systems. This is controlled by the bgp bestpath med always
command.
AS Path ignore is enabled Indicates that the AS path length is ignored by the route selection algorithm.
This is controlled by the bgp bestpath as-path ignore command.
Comparing MED from Indicates that the MED values are used in the route selection algorithm when
confederation peers comparing routes received from confederation peers. This is controlled by
the bgp bestpath med confed command.
Comparing router ID for Indicates that the router ID is used as a tiebreaker by the route selection
eBGP paths algorithm when comparing identical routes received from different external
BGP neighbors. This is controlled by the bgp bestpath compare-routerid
command.
Default local preference Default local preference value used for BGP routes.
Default keepalive Default keepalive interval. This is controlled by the timers bgp command.
Graceful restart enabled Indicates that the graceful restart capability is enabled. The configuration
commands affecting graceful restart behavior are:
• bgp graceful-restart
• bgp graceful-restart purge-time
• bgp graceful-restart stalepath-time
• bgp graceful-restart restart-time
• bgp graceful-restart graceful-reset
Update delay Maximum time that a BGP process stays in read-only mode.
Generic scan interval Interval (in seconds) between BGP scans for address family-independent
tasks. This is controlled by the bgp scan-time command.
BGP Speaker Process Speaker process responsible for receiving, processing and sending BGP
messages.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
422
BGP Commands
show bgp process
Field Description
established Number of neighbors that have connections in the established state for the
specified process.
Updates Number of update messages sent and received by the specified process.
Notifications Number of notification messages sent and received by the specified process.
Attributes Number of unique sets of attribute information stored in the specified process
and the amount of memory used by the attribute information.
AS Paths Number of unique autonomous system paths stored in the specified process
and the amount of memory used by the AS path information.
Extended communities Number of unique sets of extended community information stored in the
specified process and the amount of memory used by them.
Route Reflector Entries Number of unique sets of route reflector information stored in the specified
process and the amount of memory used by them.
Nexthop Entries Number of entries and memory usage for cached next- hop information.
Update messages queued Total number of update messages queued to be sent across all neighbors for
which the specified process is responsible.
Dampening Indicates whether dampening is enabled for the specified address family.
Client reflection Indicates whether client-to-client route reflection is enabled for the specified
address family. This is controlled by the bgp client-to-client reflection
disable command.
Scan interval Interval (in seconds) between BGP scans for the given address family. This
is controlled by the bgp scan-time command.
Main Table Version Last version of the local BGP database for the specified address family that
was injected into the main routing table.
IGP notification Indicates whether IGPs have been notified of BGP convergence for the
specified address family.
RIB has converged Indicates whether the main routing table version has converged and the
version at which it converged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
423
BGP Commands
show bgp process
Field Description
State BGP system state for the specified address family and process. This may be
one of the following:
read-only mode—Initial set of updates is being recovered. In this mode, route
selection is not performed, routes are not installed in the global RIB, and
updates are not advertised to peers.
best-path calculation mode—Route selection is being performed for the routes
that were received while in read-only mode.
import mode—Routes are imported from one VRF to another VRF once the
best paths are calculated. This mode is supported in VPNv4 unicast address
family mode.
RIB update mode—Routes that were selected in best-path calculation mode
are being installed in the global RIB.
label allocation mode: Labels are allocated for the received prefixes based
on the requirement.
normal mode—Best paths are sent to the peers for routes that exist in the
RIB. The route selection, import processing, RIB updates, and label allocation
are performed as new updates are received.
BGP Table Version Last version used in the BGP database for received routes.
Network Entries Number of sets of prefix information held in the specified BGP process for
the specified address family.
Soft Reconfig Entries Number of sets of prefix information that are present only for the purpose
of supporting soft reconfiguration.
Dampened Paths Number of routes that are suppressed due to dampening for the specified
address family.
History Paths Number of routes that are currently withdrawn, but are being maintained to
preserve dampening information.
Prefixes (Allocated/Freed) Number of sets of prefix information for the specified address family that
have been allocated and freed during the lifetime of the process.
Paths (Allocated/Freed) Number of sets of route information for the specified address family that
have been allocated and freed during the lifetime of the process.
Prefixes (Number/Memory Number of sets of prefix information currently allocated for the specified
Used) address family, and the amount of memory used by them.
Paths (Number/Memory Used) Number of sets of route information currently allocated for the specified
address family, and the amount of memory used by them.
The following is sample output from the show bgp process command with the
performance-statistics keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
424
BGP Commands
show bgp process
Sent Received
Updates: 20 20
Notifications: 0 0
Allocated Freed
Prefixes: 149 0
Paths: 200 0
Updates generated: 149 prefixes in 8 messages from 2 calls (time spent: 0.046 secs)
Scanner: 2 scanner runs (time spent: 0.008 secs)
RIB update: 1 rib update runs, 149 prefixes installed (time spent: 0.024 secs)
Process has converged for IPv4 Unicast.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
425
BGP Commands
show bgp process
Field Description
Router ID BGP identifier assigned to the local system. If this is explicitly configured
using the bgp router-id command, “manually configured” is displayed.
If the router ID is not manually configured, it is determined from a global
router ID. If the global ID is not available, the router ID is shown as 0.0.0.0.
Cluster ID The cluster identifier for the local system. If this is manually configured
using the bgp cluster-id command, “manually configured” is displayed.
Fast external fallover enabled Indicates whether fast external fallover is enabled.
Neighbor logging enabled Indicates whether logging of peer connection up and down transitions is
enabled. This is controlled by the bgp log neighbor changes disable
command.
Enforce first AS enabled Indicates that strict checking of the first AS number in paths received from
external BGP peers is enabled.
iBGP to IGP redistribution Indicates internal redistribution is enabled using the bgp
redistribution-internal command.
Treating missing MED as worst Indicates missing MED metric values are treated as worst in the route
selection algorithm. This is controlled using the bgp bestpath med
missing-as-worst command.
Always compare MED is Indicates that the MED is always used during the route selection algorithm,
enabled even when paths are received from external BGP neighbors in different
autonomous systems. This setting is controlled by the bgp bestpath med
always command.
AS Path ignore is enabled Indicates that the AS path length is ignored by the route selection algorithm.
This is controlled by the bgp bestpath as-path ignore command.
Comparing MED from Indicates that the MED values are used in the route selection algorithm
confederation peers when comparing routes received from confederation peers. This is controlled
by the bgp bestpath med confed command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
426
BGP Commands
show bgp process
Field Description
Comparing router ID for eBGP Indicates that the router ID is used as a tiebreaker by the route selection
paths algorithm when comparing identical routes received from different external
BGP neighbors. This is controlled by the bgp bestpath compare-routerid
command.
Default local preference Default local preference value used for BGP routes.
Default keepalive Default keepalive interval. This setting is controlled by the timers bgp
command.
Graceful restart enabled Indicates that the graceful restart capability is enabled. The configuration
commands affecting graceful restart behavior are: bgp graceful-restart,
bgp graceful-restart purge-time, bgp graceful-restart stalepath-time,
bgp graceful-restart restart-time, and bgp graceful-restart
graceful-reset.
Update delay Maximum time that a BGP process stays in read-only mode.
Generic scan interval Interval (in seconds) between BGP scans for address family-independent
tasks. This setting is controlled by the bgp scan-time command in router
configuration mode.
Dampening Indicates whether dampening is enabled for the specified address family.
Client reflection Indicates whether client-to-client route reflection is enabled for the specified
address family. This is controlled by the bgp client-to-client reflection
disable command.
Scan interval Interval (in seconds) between BGP scans for the given address family. This
is controlled by the bgp scan-time command.
Main Table Version Last version of the local BGP database for the specified address family that
was injected into the main routing table.
IGP notification Indicates whether IGPs have been notified of BGP convergence for the
specified address family.
Read Real time (in seconds) spent reading messages from peers by this process.
Write Real time (in seconds) spent writing messages to peers by this process.
Inbound The real time (in seconds) spent processing messages read from peers by
this process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
427
BGP Commands
show bgp process
Field Description
Config Real time (in seconds) spent processing configuration commands by this
process.
Data Real time (in seconds) spent providing operational data by this process.
Conv Indicates whether the process has converged after the initial update.
Nbr Estab Time stamp (in seconds) recording the time when the first neighbor became
established.
Bestpath Time stamp (in seconds) recording the time the best-path calculation mode
was entered.
RIB Inst Time stamp (in seconds) recording the time RIB update mode was entered.
Read/Write Time stamp (in seconds) recording the time normal mode was entered.
Last Upd Time stamp (in seconds) recording the time the last update was sent to a
neighbor.
Address Family IPv4 Unicast Indicates that BGP has reached initial convergence for the IPv4 unicast
converged in n seconds address family. The time taken for convergence is shown.
Address Family IPv6 Multicast Indicates that BGP has reached initial convergence for the IPv6 multicast
converged in n seconds address family. The time taken for convergence is shown.
The following is sample output from the show bgp process command with the
performance-statistics and detail keywords:
Sent Received
Updates: 20 20
Notifications: 0 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
428
BGP Commands
show bgp process
Processing write list: wrote 18 messages in 4 calls (time spent: 0.000 secs)
Processing write queue: wrote 10 messages in 20 calls (time spent: 0.000 secs)
Socket setup (LPTS): 4 calls (time spent: 0.010 secs)
Configuration: 1 requests (time spent: 0.002 secs)
Operational data: 9 requests (time spent: 0.026 secs)
Allocated Freed
Prefixes: 149 0
Paths: 200 0
Updates generated: 149 prefixes in 8 messages from 2 calls (time spent: 0.046 secs)
Scanner: 2 scanner runs (time spent: 0.008 secs)
RIB update: 1 rib update runs, 149 prefixes installed (time spent: 0.024 secs)
Process has converged for IPv4 Unicast.
Field Description
established Number of neighbors that have connections in the established state for the
specified process.
Updates Number of update messages sent and received by the specified process.
Notifications Number of notification messages sent and received by the specified process.
Attributes Number of unique sets of attribute information stored in the specified process
and the amount of memory used by the attribute information.
AS Paths Number of unique autonomous system paths stored in the specified process,
and the amount of memory used by the AS path information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
429
BGP Commands
show bgp process
Field Description
Extended communities Number of unique sets of extended community information stored in the
specified process and the amount of memory used by them.
Route Reflector Entries Number of unique sets of route reflector information stored in the specified
process and the amount of memory used by them.
Route-map Cache Entries Number of entries and memory usage for cached results for applying a route
map.
Filter-list Cache Entries Number of entries and memory usage for cached results for applying an AS
path filter list.
Next Hop Cache Entries Number of entries and memory usage for cached next-hop information.
Update messages queued Number of update messages queued to be sent across all neighbors for which
the specified process is responsible.
Read Indicates the number of messages read by the process, the total size of read
messages, the number of read operations performed, and the real time spent
by the process performing read operations.
Read throttled Number of times that reading from TCP has been throttled due to a backlog
of messages read but not processed.
inbound messages Number of read messages that have been processed and the real time spent
processing inbound messages.
Wrote Amount of data that has been written by the process, the number of write
operations performed, and the real time spent by the process performing write
operations.
Processing write list Number of messages written from write lists, the number of times the write
list has been processed, and the real time spent processing the write list.
Note Write lists typically contain only update messages.
Processing write queue Number of messages written from write queues, number of times the write
queue has been processed, and the real time spent processing the write queue.
Socket setup Number of socket setup operations performed and the real time spent during
socket setup operations.
Configuration Number of configuration requests received by the process and the real time
spent processing configuration requests.
Operational data Number of requests for operational data (for show commands) received by
the process and the real time spent processing operation data requests
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
430
BGP Commands
show bgp process
Field Description
State BGP system state for the specified address family and process. This may be
one of the following:
read-only mode—Initial set of updates is being recovered. In this mode, route
selection is not performed, routes are not installed in the global RIB, and
updates are not advertised to peers.
best-path calculation mode—Route selection is being performed for the routes
that were received while in read-only mode.
import mode—Routes are imported from one VRF to another VRF once the
best paths are calculated. This mode is supported in VPNv4 unicast address
family mode.
RIB update mode—Routes that were selected in best-path calculation mode
are being installed in the global RIB.
label allocation mode: Labels are allocated for the received prefixes based on
the requirement.
normal mode—Best paths are sent to the peers for routes that exist in the RIB.
The route selection, import processing, RIB updates, and label allocation are
performed as new updates are received.
BGP Table Version Last version used in the BGP database for received routes.
Network Entries Number of sets of prefix information held in the specified BGP process for
the specified address family.
Soft Reconfig Entries Number of sets of prefix information that are present only for the purpose of
supporting soft reconfiguration.
Dampened Paths Number of routes that are suppressed due to dampening for the specified
address family.
History Paths Number of routes that are currently withdrawn, but are being maintained to
preserve dampening information.
Prefixes (Allocated/Freed) Number of sets of prefix information for the specified address family that have
been allocated and freed during the lifetime of the process.
Paths (Allocated/Freed) Number of sets of route information for the specified address family that have
been allocated and freed during the lifetime of the process.
Prefixes (Number/Memory Number of sets of prefix information currently allocated for the specified
Used) address family and amount of memory used by them.
Paths (Number/Memory Number of sets of route information currently allocated for the specified
Used) address family and amount of memory used by them.
Updates generated Number of prefixes for which updates have been generated, the number of
messages used to advertise the updates, the number of update generation runs
performed, and the real time spent generating updates for the specified address
family.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
431
BGP Commands
show bgp process
Field Description
Scanner Number of times the scanner has run for the specified address family and real
time spent in scanner processing.
RIB Update Number of global routing information base update runs performed for the
specified address family, number of prefixes installed, withdrawn, or modified
in the global RIB during these runs, and real time spent performing these runs.
Process has converged Indicates whether the process has reached initial convergence for the specified
address family.
First neighbor established Time stamp (in seconds) recording the time the first neighbor in the process
was established.
Entered DO_BESTPATH Time stamp (in seconds) recording the time best-path calculation mode was
mode entered.
Entered DO_RIBUPD mode Time stamp (in seconds) recording the time RIB update mode was entered.
Entered Normal mode Time stamp (in seconds) recording the time normal mode was entered.
Last UPDATE sent Time stamp (in seconds) recording the time the last update was sent to a
neighbor.
The following is sample output from the show bgp vpnv4 unicast process performance-statistics
detail command:
Sent Received
Updates: 362259 5688505
Notifications: 14 0
Alloc Free
Pool 210: 28955629 28955628
Pool 310: 363103 363103
Pool 600: 4931162 4931162
Pool 1100: 104693 104693
Pool 4300: 799374 799374
Read 34755745 messages (3542094326 bytes) in 30528983 calls (time spent: 6427.769 secs)
Read partly throttled 1506 times
Read 14 times after crossing lower threshold Processed 5836892 inbound update messages
(time spent: 6229.512 secs)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
432
BGP Commands
show bgp process
Allocated Freed
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
433
BGP Commands
show bgp process
The following is sample output from show bgp process detail command with information on additional
paths send and receive information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
434
BGP Commands
show bgp process
……
……
Allocated Freed
Prefixes: 12 0
Paths: 60 0
Path-elems: 12 0
bgp bestpath as-path ignore, on page 54 Sets the autonomous system path length to ignore when
calculating preferred paths.
bgp bestpath compare-routerid, on page Compare identical routes received from external BGP (eBGP)
56 peers during the best-path selection process and select the route
with the lowest router ID.
bgp bestpath med always, on page 59 Compare the Multi Exit Discriminator (MED) for paths from
neighbors in different autonomous systems.
bgp bestpath med missing-as-worst, on Assume paths with no MED attribute have the most undesirable
page 63 MED value possible when performing path selection.
bgp cluster-id, on page 71 Enables reflection of routes between route reflector clients using
a BGP route reflector.
bgp cluster-id, on page 71 Configure the cluster ID if the BGP cluster has more than one
route reflector.
bgp default local-preference, on page 79 Sets the default local preference value.
bgp redistribute-internal, on page 98 Allows the redistribution of iBGP routes into an IGP such as
Intermediate System-to-Intermediate System (IS-IS) or Open
Shortest Path First (OSPF).
bgp router-id, on page 100 Configures a fixed router ID for a BGP-speaking router.
default-metric (BGP), on page 143 Sets default metric values for the BGP.
set default-afi Sets the default Address Family Identifier (AFI) for the current
session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the
current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
435
BGP Commands
show bgp regexp
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
436
BGP Commands
show bgp regexp
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each configured address family and subaddress family combination.
The address family and subaddress family options specify the routing table to be examined. If the all keyword
is specified for the address family or subaddress family, each matching routing table is examined in turn.
Use the show bgp regexp command to display all routes in the specified BGP table whose autonomous system
path is matched by the specified regular expression.
Note If the regular expression contains spaces and parentheses, it must be specified and surrounded by quotation
marks.
bgp read
Examples The following is sample output from the show bgp regexp command:
Field Description
Dampening enabled Displayed if dampening has been enabled for the routes in this BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
437
BGP Commands
show bgp regexp
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is placed at the end of each line in the table. It
can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
438
BGP Commands
show bgp regexp
Field Description
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current
session.
show bgp, on page 281 Displays entries in the BGP routing table.
show bgp route-policy, on page 440 Displays BGP information about networks that match an outbound route
policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
439
BGP Commands
show bgp route-policy
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
440
BGP Commands
show bgp route-policy
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each address family and subaddress family combination that has
been configured. The address family and subaddress family options specify the routing table to be examined.
If the all keyword is specified for the address family or subaddress family, each matching routing table is
examined.
A route policy must be configured to use this command. When the show bgp route-policy command is
entered, routes in the specified BGP table are compared with the specified route policy, and all routes passed
by the route policy are displayed.
If a pass clause is encountered while the route policy is being applied to the route and the route policy processing
completes without hitting a drop clause, the route is displayed. The route is not displayed if a drop clause is
encountered, if the route policy processing completes without hitting a pass clause, or if the specified route
policy does not exist.
The information displayed does not reflect modifications the policy might make to the route. To display such
modifications, use the show bgp policy command.
bgp read
Examples The following is sample output from the show bgp route-policy command in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
441
BGP Commands
show bgp route-policy
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
442
BGP Commands
show bgp route-policy
Field Description
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate
and advertise to its neighbors.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
show bgp policy, on page 409 Displays advertisements under a proposed policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
443
BGP Commands
show bgp session-group
configuration (Optional) Displays the effective configuration for the session group, including any inherited
configuration.
nvgen (Optional) Displays output in the form of the show running-config command.
If the defaults keyword also is specified, the output is not suitable for cutting and pasting
into a configuration session.
inheritance (Optional) Displays the session groups from which this session group inherits configuration.
users (Optional) Display the session groups, neighbor groups, and neighbors that inherit
configuration from this session group.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show bgp session-group command with the group-name configuration argument and keyword
to display the effective configuration of a session group, including any configuration inherited from other
session groups through application of the use command. The source for each configured command is also
displayed.
Use the defaults keyword to display the value of all configuration, including default configuration. Use the
nvgen keyword to display configuration in the form of the show running-config command output. Output
in this form is suitable for cutting and pasting into a configuration session.
Use the show bgp session-group command with the group-name inheritance argument and keyword to
display the session groups from which the specified session group inherits configuration.
Use the show bgp session-group command with the group-name users argument and keyword to display
the neighbors, neighbor groups, and session groups that inherit configuration from the specified session group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
444
BGP Commands
show bgp session-group
bgp read
Examples For the example shown here, the following configuration is used:
session-group group3
advertisement-interval 5
dmzlink-bw
!
session-group group1
use session-group group2
update-source Loopback0
!
session-group group2
use session-group group3
ebgp-multihop 2
The following example shows the show bgp session-group command with the configuration
keyword:
session-group group1
advertisement-interval 5[s:group2 s:group3]
ebgp-multihop 2 [s:group2]
update-source Loopback0 []
dmzlink-bandwidth [s:group2 s:group3]
The source of each command is shown to the right of the command. For example, update-source is
configured directly on session group group1. The dmzlink-bandwidth command is inherited from
session group group2, which in turn inherits it from session group group3.
The following example shows the show bgp session-group command with the users keyword:
IPv4 Unicast:a:group1
The following example shows the show bgp session-group command with the inheritance
keyword.
Session:s:group2 s:group3
The command output shows that the session group group1 directly uses the group2 session group.
The group2 session group uses the group3 session group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
445
BGP Commands
show bgp session-group
Field Description
[dflt] Indicates the command is not explicitly configured or inherited, and the default value for the
command is used. This field may be shown when the defaults keyword is specified.
<not Indicates that the default is for the command to be disabled. This field may be shown when the
set> defaults keyword is specified.
show bgp neighbor-group, on page 362 Displays information about the BGP configuration for neighbor
groups.
show bgp neighbors, on page 366 Displays information about BGP connections to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
446
BGP Commands
show bgp sessions
Syntax Description not-established (Optional) Displays all the neighbors that are not in established state
not-nsr-ready (Optional) Displays all the neighbors that are not nonstop routing (NSR) ready.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The show bgp sessions command without a keyword provides brief information about all the BGP neighbors
configured irrespective of the address family or VRF.
The show bgp sessions command with the not-established keyword shows BGP peers which are yet to
establish their peering relationship.
The show bgp session command with the and not-nsr-ready keyword shows BGP peers which are yet to
reach the nsr ready state.
bgp read
Examples The following is sample output from the show bgp sessions command in EXEC mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
447
BGP Commands
show bgp sessions
The following is sample output from the show bgp sessions command with the not-established
keyword:
The following is sample output from the show bgp sessions command with the not-nsr-ready
keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
448
BGP Commands
show bgp sessions
Field Description
AS Autonomous system.
NSRState State of the Border Gateway Protocol (BGP) nonstop routing (NSR).
show bgp neighbors, on page 366 Displays information about Border Gateway Protocol (BGP) connections
to neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
449
BGP Commands
show bgp summary
show bgp [{ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast
| all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf
{vrf-name | all} [{ipv4 {unicast | labeled-unicast} | ipv6 unicast}] | vpvn6 unicast}] summary
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
450
BGP Commands
show bgp summary
Release Modification
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
Use the show bgp summary command to display a summary of the neighbors for which the specified address
family and subaddress family are enabled. If the neighbor does not have the specified address family and
subaddress family enabled, it is not included in the output of the show command. If the all keyword is
specified for the address family or subaddress family, a summary for each combination of address family and
subaddress family is displayed in turn.
The table versions shown in the output (RcvTblVer, bRIB/RIB, SendTblVer, and TblVer) are specific to the
specified address family and subaddress family. All other information is global.
The table versions provide an indication of whether BGP is up to date with all work for the specified address
family and subaddress family.
• bRIB/RIB < RecvTblVer—Some received routes have not yet been considered for installation in the
global routing table.
• TblVer < SendTblVer—Some received routes have been installed in the global routing table but have
not yet been considered for advertisement to this neighbor.
bgp read
Examples The following is sample output from the show bgp summary command:
RP/0/RSP0/CPU0:router#show bgp summary
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
451
BGP Commands
show bgp summary
Field Description
local AS number Autonomous system number set by the router bgp, on page 263 command.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format
is 1 to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format
is 1.0 to 65535.65535.
BGP generic scan interval Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP main routing table Last version of the BGP database that was injected into the main routing table.
version
Dampening enabled Displayed if dampening has been enabled for the routes in this BGP routing
table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address
family and subaddress family.
RecvTblVer Last version used in the BGP database for received routes.
bRIB/RIB Last version of the local BGP database that was injected into the main routing
table.
LabelVer Label version used in the BGP database for label allocation.
ImportVer Last version of the local BGP database for importing routes.
SendTblVer Latest version of the local BGP database that is ready to be advertised to
neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
452
BGP Commands
show bgp summary
Field Description
Some configured eBGP Some external neighbors exist that do not have both an inbound and outbound
neighbors do not have any policy configured for every address family, using the route-policy (BGP)
policy command. In this case, no prefixes are accepted and advertised to those
neighbors.
AS Autonomous system.
TblVer Last version of the BGP database that was sent to a neighbor.
Up/Down Length of time in (hh:mm:ss) that the BGP session has been in Established
state, or the time since the session left Established state, if it is not established.
St/PfxRcd If the BGP session is not established, the current state of the session. If the
session is established, the number of prefixes the router has received from
the neighbor.
If the number of prefixes received exceeds the maximum allowed (as set by
the maximum-prefix command), “(PfxRcd)” appears.
If the connection has been shut down using the shutdown command,
“(Admin)” appears.
If the neighbor is external and it does not have an inbound and outbound
policy configured for every address family, an exclamation mark (!) is inserted
at the end of the state when using the route-policy ( BGP ) command.
If the connection has been shut down due to out of memory (OOM), “(OOM)”
appears.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
453
BGP Commands
show bgp summary nsr
show bgp summary [{ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast
| multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4
unicast | vrf {vrf-name | all} [{ipv4 {unicast | labeled-unicast} | ipv6 unicast}] | vpvn6 unicast}] nsr
[standby]
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
454
BGP Commands
show bgp summary nsr
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
Examples The following is sample output from the show bgp summary nsr command:
node0_1_CPU0 Speaker
Current BGP NSR state - NSR Ready achieved at: Feb 3 14:22:49
NSR State READY notified to Redcon at: Feb 4 07:44:43
The following example shows sample output from the show bgp summary nsr command with the
standby keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
455
BGP Commands
show bgp summary nsr
node0_0_CPU0 Speaker
Field Description
BGP generic scan interval Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP main routing table version Last version of the BGP database that was injected into the main routing
table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address
family and subaddress family.
Entered mode The successive transition of various states of TCP and BGP, leading to the
NSR ready state.
Note This is used for monitoring and debugging purposes.
SyncVer The version which has synced to standby for this neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
456
BGP Commands
show bgp summary nsr
Field Description
nsr (BGP), on page 222 Activates Border Gateway Protocol (BGP) nonstop routing (NSR)
show bgp nsr, on page 402 Displays Border Gateway Protocol (BGP) nonstop routing (NSR) information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
457
BGP Commands
show bgp table
show bgp table [{ipv4 {mdt | multicast | mvpn | rt-filter | tunnel | unicast} | ipv6 {multicast | mvpn
| unicast} | l2vpn {evpn | vpls | vpws} | standby | vpnv4 unicast | vpnv6 unicast}]
Syntax Description ipv4 mdt (Optional) Specifies IPv4 multicast distribution tree (MDT) neighbors.
ipv4 mvpn (Optional) Specifies the IPv4 mvpn address family neighbors.
ipv4 rt-filter (Optional) Specifies the IPv4 RT Constraint address family neighbors.
ipv6 mvpn (Optional) Specifies the IPv6 mvpn address family neighbors.
ipv6 unicast (Optional) Specifies the IPv6 Tunnel address family neighbors.
l2vpn evpn (Optional) Specifies the L2VPN EVPN address family neighbors.
l2vpn vpls (Optional) Specifies the L2VPN VPLS address family neighbors.
l2vpn vpws (Optional) Specifies the L2VPN VPWS address family neighbors.
standby (Optional) Specifies the IPv4 Unicast address family neighbor on the standby processor.
vpnv4 unicast (Optional) Specifies VPN Version 4 (VPNv4) unicast address family neighbors.
vpnv6 unicast (Optional) Specifies VPN Version 6 (VPNv6) unicast address family neighbors.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Release 4.3.2, 5.1.0, 5.1.1, 5.1.2 and 5.2.0 The L2VPN Address Family was added.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
458
BGP Commands
show bgp table
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See Cisco ASR 9000
Series Aggregation Services Router System Management Command Reference for detailed information and
syntax for the set default-afi and set default-safi commands. If you do not specify a default address family,
the default address family is IPv4. If you do not specify a default subaddress family, the default subaddress
family is unicast.
Use the show bgp table command to display a brief summary of the neighbors for which the specified address
family (AFI) and subaddress family (SAFI) are enabled. If the AFI and/or SAFI is not enabled, the command
will only display the column headings.
bgp read
Examples The following is sample output from the bgp table vpnv4 unicast command in EXEC mode:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
459
BGP Commands
show bgp table
Field Description
VRF The VRF which each neighbor belongs to; either the default VRF or a specified VRF.
AS Autonomous system.
TblVer Last version of the BGP database that was sent to a neighbor.
St/PfxRcd If the BGP session is not established, the current state of the session. If the session is established,
the number of prefixes the router has received from the neighbor.
If the number of prefixes received exceeds the maximum allowed (as set by the maximum-prefix
command), “(PfxRcd)” appears.
If the connection has been shut down using the shutdown command, “(Admin)” appears.
If the neighbor is external and it does not have an inbound and outbound policy configured for
every address family, an exclamation mark (!) is inserted at the end of the state when using the
route-policy (BGP) command.
If the connection has been shut down due to out of memory (OOM), “(OOM)” appears.
show bgp neighbor-group, on page 362 Displays information about the Border Gateway Protocol (BGP)
configuration for neighbor groups.
show bgp neighbors, on page 366 Displays information about Border Gateway Protocol (BGP)
connections to neighbors.
show bgp summary, on page 450 Displays the status of all Border Gateway Protocol (BGP)
connections.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
460
BGP Commands
show bgp truncated-communities
show bgptruncated-communities
all (Optional) For subaddress families, specifies prefixes for all subaddress
families.
all (Optional) For address family, specifies prefixes for all address families.
ipv4 { unicast | labeled-unicast (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
} families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
461
BGP Commands
show bgp truncated-communities
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
BGP contains a separate routing table for each address family and subaddress family combination that has
been configured. The address family and subaddress family options specify the routing table to be examined.
If the all keyword is specified for the address family or subaddress family, each matching routing table is
examined.
Use the show bgp truncated-communities command to display those routes in the specified BGP routing
table in which the buffers used to store communities or extended communities have overflowed. An overflow
occurs if an attempt is made to associate more communities or extended communities with the route than fits
in a BGP update message. This can happen due to modification of communities or extended communities
during aggregration or when inbound policy is applied.
bgp read
Examples The following is sample output from the show bgp truncated-communities command:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
462
BGP Commands
show bgp truncated-communities
Field Description
BGP main routing table Last version of the BGP database that was installed into the main routing table.
version
Dampening enabled Displayed if dampening is enabled for the routes in this BGP routing table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address family
and subaddress family.
Status codes Status of the table entry. The status is displayed as a three-character field at the
beginning of each line in the table. The first character may be (in order of
precedence):
S—Path is stale, indicating that a graceful restart is in progress with the peer from
which the route was learned.
s—Path is more specific than a locally sourced aggregate route and has been
suppressed.
*—Path is valid.
The second character may be (in order of precedence):
>—Path is the best path to use for that network.
d—Path is dampened.
h—Path is a history entry, representing a route that is currently withdrawn, but that
is being maintained to preserve dampening information. Such routes should never
be marked as valid.
The third character may be:
i—Path was learned by an internal BGP (iBGP) session.
Origin codes Origin of the path. The origin code is displayed at the end of each line in the table.
It can be one of the following values:
i—Path originated from an Interior Gateway Protocol (IGP) and was advertised
with a network or aggregate-address command.
e—Path originated from an Exterior Gateway Protocol (EGP).
?—Origin of the path is not clear. Usually, this is a route that is redistributed into
BGP from an IGP.
Next Hop IP address of the next system that is used when a packet is forwarded to the
destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP
route to this network.
Metric Value of the interautonomous system metric, otherwise known as the Multi Exit
Discriminator (MED) metric.
LocPrf Local preference value. This is used to determine the preferred exit point from the
local autonomous system. It is propagated throughout the local autonomous system.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
463
BGP Commands
show bgp truncated-communities
Field Description
Weight Path weight. Weight is used in choosing the preferred path to a route. It is not
advertised to any neighbor.
Path Autonomous system path to the destination network. At the end of the path is the
origin code for the path.
network (BGP), on page 208 Specifies a local network that the BGP routing process should originate
and advertise to its neighbors.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a BGP
neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current session.
show bgp, on page 281 Displays entries in the BGP routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
464
BGP Commands
show bgp update-group
show bgp [{ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast
| all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf
{vrf-name | all} [{ipv4 {unicast | labeled-unicast} | ipv6 unicast}] | vpnv6 unicast}] update-group
[{neighbor ip-address | process-id.index [{summary | performance-statistics}]}]
ipv4 { unicast | (Optional) For VRF, specifies IPv4 unicast or labeled-unicast address
labeled-unicast } families.
ipv6 unicast (Optional) For VRF, specifies IPv6 unicast address families.
process-id.index (Optional) Update group index. Process ID range is 0 to 254. Index range
is 0 to 4294967295.
The process id.index argument is specified as follows: process ID (dot)
index. In standalone mode, the process ID is always 0.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
465
BGP Commands
show bgp update-group
Command Default If no address family or subaddress family is specified, the default address family and subaddress family
specified using the set default-afi and set default-safi commands are used.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 5.1.1 The command output was modified to include the status of advertised permanent paths.
Release 6.1.2 The command output was modified to include the BGP optimal route reflector (ORR) feature
information.
Usage Guidelines
Note The set default-afi command is used to specify the default address family for the session, and the set
default-safi command is used to specify the default subaddress family for the session. See the System
Management Command Reference for Cisco ASR 9000 Series Routers for detailed information and syntax
for the set default-afi and set default-safi commands. If you do not specify a default address family, the
default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family
is unicast.
Every BGP neighbor is automatically assigned to an update group for each address family that is enabled on
the neighbor. Neighbors that have similar outbound policy, such that they are sent the same updates, are placed
in the same update group.
Use the show bgp update-group command to display the update groups and a list of the neighbors that
belong to the update group.
Use the show bgp update-group neighbor command to display details about the update group to which a
neighbor belongs for the specified address family.
Use the summary keyword to display a summary of the neighbors belonging to the specified update group.
The display format is the same as for the show bgp summary, on page 450 command.
Use the performance-statistics keyword to display information about the number of prefixes processed and
the time taken to generate updates for the specified update group.
Note Update group indexes are not necessarily persistent over a process restart. If a BGP process restarts, the index
of the update group to which a particular neighbor is assigned may be different, though the set of neighbors
belonging to the update group is the same.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
466
BGP Commands
show bgp update-group
bgp read
Examples This sample output from the show bgp update-group command shows that router R2 with IP
192.0.2.2 is in update-group 0.1:
RP/0/RSP0/CPU0:router# show bgp update-group
Update group for IPv4 Unicast, index 0.1:
Attributes:
Neighbor sessions are IPv4
Internal
Common admin
First neighbor AS: 65000
Send communities
Send GSHUT community if originated
Send extended communities
Route Reflector Client
ORR root (configured): g1; Index: 0
4-byte AS capable
Non-labeled address-family capable
Send AIGP
Send multicast attributes
Minimum advertisement interval: 0 secs
Update group desynchronized: 0
Sub-groups merged: 0
Number of refresh subgroups: 0
Messages formatted: 5, replicated: 5
All neighbors are assigned to sub-group(s)
Neighbors in sub-group: 0.2, Filter-Groups num:1
Neighbors in filter-group: 0.2(RT num: 0)
192.0.2.2
The following is sample output from the show bgp update-group command:
Field Description
Update group for Address family to which updates in this update group apply.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
467
BGP Commands
show bgp update-group
Field Description
Unsuppress map Unsuppress route map used to selectively unsuppress more specific routes
of locally generated aggregates for members of this update group.
Outbound policy Route policy applied to outbound updates generated for members of this
update group.
ORF Receive enabled Members of this update group are capable of receiving an outbound route
filter.
Route Reflector Client Local system is acting as a route reflector for members of this update group.
Remove private AS numbers Members of this update group have private AS numbers stripped from
outbound updates.
Next-hop-self enabled Next- Next hop for members of the update group is set to the local router.
Directly connected IPv6 EBGP Members of this update group are directly connected external
BGP IPv6-based peers.
Configured Local AS Local autonomous system (AS) used for members of this update group.
Common admin Peers in this update group are under common administration (internal or
confederation peers).
Send extended communities Extended communities is sent to neighbors in this update group.
Minimum advertisement interval Minimum advertisement interval for members of this update group.
Messages formatted Number of update messages generated for this update group.
Neighbors in this update group List of neighbors that use this update group for the given address family.
Update group desynchronized Number of times an update group has been split to accommodate the slower
peer. This option is disabled.
Sub-groups merged Number of times an update group has been split and merged.
Neighbors not in any sub-group BGP neighbor that does not belong to any subgroup.
The following is sample output from the show bgp update-group command with the ipv4 , unicast
, and summary keywords and the process id.index argument:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
468
BGP Commands
show bgp update-group
This is sample output from the show bgp ipv4 unicast update-group command showing the status
of advertised permanent paths:
Field Description
local AS number Autonomous system number set by the router bgp, on page 263 command.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format
is 1 to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format
is 1.0 to 65535.65535.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
469
BGP Commands
show bgp update-group
Field Description
BGP generic scan interval Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP main routing table Last version of the BGP database that was injected into the main routing
version table.
Dampening enabled Displayed if dampening has been enabled for the routes in this BGP routing
table.
BGP scan interval Interval (in seconds) between scans of the BGP table specified by the address
family and subaddress family.
RecvTblVer Last version used in the BGP database for received routes.
bRIB/RIB Last version of the local BGP database that was injected into the main routing
table.
LabelVer Label version used in the BGP database for label allocation.
ImportVer Last version of the local BGP database for importing routes.
SendTblVer Latest version of the local BGP database that is ready to be advertised to
neighbors.
Some configured eBGP Some external neighbors that exist do not have both an inbound and outbound
neighbors do not have any policy configured for every address family, using the route-policy (BGP)
policy command. In this case, no prefixes are accepted or advertised to those
neighbors.
AS Autonomous system.
TblVer Last version of the BGP database that was sent to a neighbor.
Up/Down Length of time (in hh:mm:s) that the BGP session has been in Established
state, or the time since the session left Established state, if it is not established.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
470
BGP Commands
show bgp update-group
Field Description
St/PfxRcd If the BGP session is not established, the current state of the session. If the
session is established, the number of prefixes the router has received from
the neighbor.
If the number of prefixes received exceeds the maximum allowed (as set by
the maximum-prefix command), “(PfxRcd)” appears.
If the connection has been shut down using the shutdown command,
“(Admin)” appears.
If the neighbor is external and it does not have an inbound and outbound
policy configured for every address family, an exclamation mark (!) is inserted
at the end of the state when using the route-policy ( BGP ) command.
maximum-prefix (BGP), on page 194 Limits the number of prefixes that can be received from a neighbor.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from a
BGP neighbor.
set default-afi Sets the default Address Family Identifier (AFI) for the current session.
set default-safi Sets the default Subaddress Family Identifier (SAFI) for the current
session.
show bgp summary, on page 450 Displays the status of all BGP connections.
shutdown (BGP), on page 484 Disables a neighbor without removing its configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
471
BGP Commands
show bgp vrf
ipv4-address/length [ detail ] (Optional) Displays detailed output for the specified IPv4-address.
vrf source-vrf-name (Optional) Displays routes imported from the specified source VRF.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 5.3.2 The show command output is updated to display Data Center Interconnect (DCI) Gateway
related fields and details.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show bgp vrf imported-routes command to display all paths imported into a specified VRF from
the default VRF. Use the neighbor neighbor-address keyword and argument to display all imported paths
and which paths were learned from the specified neighbor. Use the vrf source-vrf-name keyword and
argument to display all imported routes that belong to the specified source VRF. The neighbor
neighbor-address and vrf source-vrf-name cannot coexist.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
472
BGP Commands
show bgp vrf
bgp read
Examples The following is sample output from the show bgp vrf imported-routes command:
The following is sample output from the show bgp vrf vrf-name ipv4 unicast ipv4-address/length
detail command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
473
BGP Commands
show bgp vrf
This table describes the significant fields shown in the display output for show bgp vrf command.
Field Description
BGP Route Distinguisher: Unique identifier for the BGP routing instance.
local AS number Autonomous system number set by the router bgp, on page 263 command.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain
format is 1 to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format
is 1.0 to 65535.65535.
BGP main routing table version Last version of the BGP database that was injected into the main routing
table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
474
BGP Commands
show lpts punt excessive-flow-trap bgp
Usage Guidelines You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
lpts read
basic-services read-write
Examples This example shows to the details of bad actor identified for bgp protocol:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
475
BGP Commands
show protocols (BGP)
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show protocols command to get information about the protocols running on the router and to quickly
determine which protocols are active. The command is designed to summarize the important characteristics
of the running protocol, and command output varies depending on the specific protocol selected. For BGP,
the command output lists the protocol ID, peers with elapsed time since last reset, and miscellaneous
information, such as external and internal local distances and sourced routes.
bgp read
rib read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
476
BGP Commands
show protocols (BGP)
Examples The following example shows the display for the show protocols command using the bgp keyword:
Field Description
Routing Protocol: Identifies BGP as the running protocol and displays the BGP AS number.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format
is 1 to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format
is 1.0 to 65535.65535.
Address Family Specifies the address family. This can be IPv4 Unicast, IPv4 Multicast, or IPv6
Unicast.
Distance: external Specifies the distance BGP sets when installing eBGP routes into the RIB.
eBGP routes are routes received from eBGP peers. The RIB uses the distance
as a tiebreaker when several protocols install a route for the same prefix.
Distance: internal Specifies the distance BGP sets for routes received from iBGP peers.
Distance: local Specifies the distance BGP sets for locally generated aggregates and backdoor
routes.
Sourced Networks List of locally sourced networks. These are networks sourced using the
network command.
State/Last update received State of each neighbor and the time since the last update was received from
the neighbor if it is established.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
477
BGP Commands
show running-config lpts punt excessive-flow-trap
basic-services read,
write
The show running-config output for the above show lpts punt excessive-flow-trap command is:
Field Description
penalty-rate The penalty policing rate for the ARP protocol. For ARP, the value is 10.
penalty-timeout The penalty timeout value for the ARP protocol. For ARP, the value is 20.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
478
BGP Commands
show svd role
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The show svd role command output displays name of the line card and role for each address-family in a table.
This example displays the different nodes in a line card and corresponding IPv4, and IPv6 SVD role
information:
show svd state, on page 480 Displays Selective VRF Download (SVD) state information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
479
BGP Commands
show svd state
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows the SVD configuration state and the SVD operational state in a line card:
show svd role, on page 479 Displays Selective VRF Download (SVD) role information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
480
BGP Commands
show tcp brief
Syntax Description location node-id (Optional) Specifies location information for the specified node ID. The node ID variable
is mentioned in the rack/slot/module notation.
Example
The following is a sample output from the show tcp brief command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
481
BGP Commands
show tcp pcb
Syntax Description pcb-value Specifies PCB hexadecimal address. The valid range is from 0x0 to 0xFFFFFFFF.
Example
The following is a sample output from the show tcp pcb command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
482
BGP Commands
show tcp pcb
ACK hold time: 200 ms, Keepalive time: 0 sec, SYN waittime: 30 sec
Giveup time: 0 ms, Retransmission retries: 0, Retransmit forever: FALSE
Connect retries remaining: 30, connect retry interval: 30 secs
Datagrams (in bytes): MSS 500, peer MSS 1460, min MSS 500, max MSS 1460
PDU information:
#PDU's in buffer: 0
FIB Lookup Cache: IFH: 0x200 PD ctx: size: 0 data:
Num Labels: 0 Label Stack:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
483
BGP Commands
shutdown (BGP)
shutdown (BGP)
To disable a neighbor without removing its configuration, use the shutdown command in an appropriate
configuration mode. To re-enable the neighbor and reestablish a Border Gateway Protocol (BGP) session,
use the no form of this command.
shutdown [inheritance-disable]
no shutdown [inheritance-disable]
Syntax Description inheritance-disable (Optional) Overrides the value of a shutdown command inherited from a neighbor
group or session group.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the shutdown command to terminate any active session for the specified neighbor and remove all
associated routing information. Use of the shutdown command with a neighbor group or session group may
suddenly terminate a large number of BGP neighbor sessions because all neighbors using the neighbor group
or session group may be affected.
Use the show bgp summary command to display a summary of BGP neighbors. Neighbors that are idle due
to the shutdown command are displayed with the “Idle (Admin)” state.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit
the configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Examples The following example shows that any active session for neighbor 192.168.40.24 is disabled:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
484
BGP Commands
shutdown (BGP)
In the following example, the session remains active for neighbor 192.168.40.24 because the inherited
shutdown command has been overridden:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
show bgp summary, on page 450 Displays the status of all BGP connections.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
485
BGP Commands
shutdown (rpki-server)
shutdown (rpki-server)
To shutdown RPKI cache-server, use the shutdown command in rpki-server configuration mode. To set that
the RPKI cache be active, use the no form of this command.
shutdown
no shutdown
This command has no keywords or arguments.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command shows how to configure no shutdown of the RPKi cache configuration after other
RPKI cache parameters are configured:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#username rpki-user
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#password rpki-ssh-pass
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#preference 1
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#purge-time 30
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#refresh-time 30
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#response-time 30
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#no shutdown
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
486
BGP Commands
signalling disable
signalling disable
To disable BGP or LDP signaling protocol to neighbors, use the signalling disable command in neighbor
address family (l2vpn vpls-vpws) configuration mode. To restore the system to its default condition, use the
no form of this command.
Command Default Both BGP and LDP signaling protocols are enabled.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
The following example shows how to disable BGP signaling protocol for neighbor 10.2.3.4:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
487
BGP Commands
site-of-origin (BGP)
site-of-origin (BGP)
To attach a site-of-origin extended community attribute to each route received from the specified peer, use
the site-of-origin command in VRF neighbor address family configuration mode. To restore the system to
its default condition, use the no form of this command.
• nn —32-bit number
ip-address:nn IP address.
• ip-address —32-bit IP address
• nn —16-bit number
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When routes are advertised to the peer, routes whose extended communities list contain the site of origin
(SoO) are filtered out and not advertised to the peer. Site-of-origin uniquely identifies the site from which the
provide edge (PE) router learned routes, thus filtering based on the extended community helps prevent transient
routing loops from occurring in complex and mixed network topologies.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
488
BGP Commands
site-of-origin (BGP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
489
BGP Commands
socket receive-buffer-size
socket receive-buffer-size
To set the size of the receive buffers for all Border Gateway Protocol (BGP) neighbors, use the socket
receive-buffer-size command in an appropriate configuration mode. To set the size of the receive buffers to
the default size, use the no form of this command.
Syntax Description socket-size Size (in bytes) of the receive-side socket buffers. Range is 512 to 131072.
bgp-size (Optional) Size (in bytes) of the receive buffers in BGP. Range is 512 to 131072.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the socket receive-buffer-size command to increase the buffer size when receiving updates from a
neighbor. Using larger buffers can improve convergence time because the software can process more packets
simultaneously. However, allocating larger buffers uses more memory on your router.
Note Increasing the socket buffer size uses more memory only when more messages are waiting to be processed
by the software. In contrast, increasing the BGP buffer size uses extra memory indefinitely.
Use the receive-buffer-size command on individual neighbors to change the values set by the socket
receive-buffer-size command.
bgp read,
write
Examples The following example shows how to set the receive buffer sizes for all neighbors to 65,536 bytes
for the socket buffer and 8192 bytes for the BGP buffer:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
490
BGP Commands
socket receive-buffer-size
receive-buffer-size, on page 240 Sets the size of the receive buffers for a BGP neighbor.
socket send-buffer-size, on page 492 Sets the size of the send buffers for all BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
491
BGP Commands
socket send-buffer-size
socket send-buffer-size
To set the size of the send buffers for all Border Gateway Protocol (BGP) neighbors, use the socket
send-buffer-size command in an appropriate configuration mode. To set the size of the send buffers to the
default size, use the no form of this command.
Syntax Description socket-size Size (in bytes) of the send-side socket buffers. Range is 4096 to 131072.
bgp-size (Optional) Size (in bytes) of the send buffers in BGP. Range is 4096 to 131072.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the socket send-buffer-size command to increase the buffer size when sending updates to neighbors.
Using larger buffers can improve convergence time because the software can process more packets
simultaneously. However, allocating larger buffers uses more memory on your router.
Note Increasing the socket buffer size uses more memory only when more messages are waiting to be sent by the
software. In contrast, increasing the BGP buffer size uses extra memory indefinitely.
Use the send-buffer-size command on individual neighbors to change the values set by the socket
send-buffer-size command.
bgp read,
write
Examples The following example shows how to set the send buffer sizes for all neighbors to 8192 bytes for
the socket buffer and the BGP buffer:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
492
BGP Commands
socket send-buffer-size
send-buffer-size, on page 269 Sets the size of the send buffers for a BGP neighbor.
socket receive-buffer-size, on page 490 Sets the size of the receive buffers for all BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
493
BGP Commands
soft-reconfiguration inbound
soft-reconfiguration inbound
To configure the software to store updates received from a neighbor, use the soft-reconfiguration inbound
command in an appropriate configuration mode. To disable storing received updates, use the no form of this
command.
Syntax Description always (Optional) Always performs a soft inbound clear using stored updates, even if the
neighbor supports the route refresh capability.
inheritance-disable (Optional) Overrides configuration for this command that may be inherited from a
neighbor group or address family group.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
To filter or modify some of the updates received from a neighbor, you configure an inbound policy using the
route-policy (BGP) command. Configuring soft reconfiguration inbound causes the software to store the
original unmodified route beside a route that is modified or filtered. This allows a “soft clear” to be performed
after the inbound policy is changed. To perform a soft clear, use the clear bgp soft command with the
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
494
BGP Commands
soft-reconfiguration inbound
in keyword specified. The unmodified routes are then passed through the new policy and installed in the BGP
table.
Note If an address family group, neighbor group, or session group is configured, the configuration inside these
configuration groups will not be effective unless it is applied directly or indirectly to one or more neighbors.
Note The bgp auto-policy-soft-reset is enabled by default. A soft clear is done automatically when the inbound
policy configured with the route-policy (BGP) command is changed. This behavior can be changed by
disabling the auto-policy-soft-reset using the bgp auto-policy-soft-reset disable command.
If the neighbor supports the route refresh capability, then the original routes are not stored because they can
be retrieved from the neighbor through a route refresh request. However, if the always keyword is specified,
the original routes are stored even when the neighbor supports the route refresh capability.
If the soft-reconfiguration inbound command is not configured and the neighbor does not support the route
refresh capability, then an inbound soft clear is not possible. In that case, the only way to rerun the inbound
policy is to use the clear bgp ip-address command to reset the neighbor BGP session.
Note If there is an existing BGP session with a neighbor that does not support the route refresh capability, the
session is terminated and a new one is initiated.
Note The extra routes stored as a result of configuring this command use more memory on the router.
If you configure this command for a neighbor group or neighbor address family group, all neighbors using
the group inherit the configuration. Values of commands configured specifically for a neighbor override
inherited values.
bgp read,
write
Examples The following example shows inbound soft reconfiguration enabled for IP Version 4 (IPv4) unicast
routes received from neighbor 10.108.1.1. The software stores all routes received in their unmodified
form so that when an inbound soft clear is performed later, the stored information can then be used
to generate a new set of modified routes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
495
BGP Commands
soft-reconfiguration inbound
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# exit
af-group, on page 27 Creates an address family group for BGP neighbors and enters
address family group configuration mode.
bgp auto-policy-soft-reset disable, on Disables an automatic soft reset of BGP peers when the configured
page 53 inbound route policy is modified.
clear bgp, on page 118 Resets a BGP connection using a soft or hard reset.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration
mode.
rd, on page 238 Applies a prefix list to filter updates received from a neighbor.
route-policy (BGP), on page 257 Applies a routing policy to updates advertised to or received from
a BGP neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
496
BGP Commands
speaker-id
speaker-id
To allocate a speaker process to a neighbor, use the speaker-id command in the appropriate configuration
mode. To remove the speaker process from a neighbor, use the no form of this command.
speaker-id id
no speaker-id [id]
Release 4.2.0 Removed support for this command in neighbor configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
Examples The following example shows how to allocate speaker process 3 to neighbor 192.168.40.24:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
497
BGP Commands
svd platform enable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
After upgrading to Cisco IOS XR Release 4.3.1 or later, the default setting for SVD is disabled and routes or
labels are not selectively downloaded to the line cards. All routes are be available on all line cards. This may
lead to out of resource conditions, if the line card hardware scale limits are exceeded because routes were
conserved by downloading selectively earlier. To resolve the out of resource condition, turn on SVD using
the svd platform enable command.
Ensure that the total number of routes (sum of all unique routes on core facing line cards and edge facing line
cards ) fits on the line card hardware, before upgrading to Cisco IOS XR Release 4.3.1 or later.
To enable selective VRF download on Cisco ASR 9000 Series Aggregation Services Router, reload the chassis
using the reload location all command after configuring the svd platform enable command.
Note After enabling SVD using svd platform enable, do not use the selective-vrf-download disable command to
turn off SVD.
Selective VRF download is disabled by default. Once SVD is enabled, use the no svd platform enable
command followed by a reload of the router using the reload location all command to disable SVD.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
498
BGP Commands
svd platform enable
This example shows how to enable selective VRF download for Cisco ASR 9000 Series Aggregation
Services Router:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#svd platform enable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
499
BGP Commands
table-policy
table-policy
To apply a routing policy to routes being installed into the routing table, use the table-policy command in
an appropriate configuration mode. To disable applying a routing policy when installing routes into the routing
table, use the no form of this command.
table-policy policy-name
no table-policy [policy-name]
Command Default No policy is applied when routes are installed into the routing table.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note Table policy provides users with the ability to drop routes from the RIB based on match criteria. This feature
can be useful in certain applications and should be used with caution as it can easily create a routing ‘black
hole’ where BGP advertises routes to neighbors that BGP does not install in its global routing table and
forwarding table.
Use the table-policy command to modify route attributes as the routes are installed into the routing table by
Border Gateway Protocol (BGP). Commonly, it is used to set the traffic index attribute.
bgp read,
write
Examples The following example shows how to apply the set-traffic-index policy to IPv4 unicast routes being
installed into the routing table:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
500
BGP Commands
table-policy
route-policy (RPL) Defines a route policy and enters route policy configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
501
BGP Commands
tcp mss
tcp mss
To configure TCP Maximum Segment Size (MSS) under per neighbor or neighbor group, use the tcp mss
command in the appropriate configuration mode. To remove the TCP MSS configuration use the no form of
this command.
Syntax Description segment-size Configures the TCP MSS value. The range is 68 to 10000.
Usage Guidelines The configurable range for TCP MSS is from 68 to 10000. The BGP notifier rejects the configuration if you
try to configure outside this range.
If the TCP MSS value is not configured, the default value is 1460.
Example
The following example shows how to configure TCP MSS under neighbor-group:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 10
RP/0/RSP0/CPU0:router(config-bgp)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#exit
RP/0/RSP0/CPU0:router(config-bgp)#neighbor-group n1
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)#tcp mss 500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
502
BGP Commands
tcp mss inheritance-disable
Example
The following example shows how to disable TCP MSS under a specific neighbor:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 10
RP/0/RSP0/CPU0:router(config-bgp)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#exit
RP/0/RSP0/CPU0:router(config-bgp)#neighbor-group n1
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)#tcp mss 500
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)#address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)#exit
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)#exit
RP/0/RSP0/CPU0:router(config-bgp)#neighbor 10.0.0.2
RP/0/RSP0/CPU0:router(config-bgp-nbr)#remote-as 1
RP/0/RSP0/CPU0:router(config-bgp-nbr)#use neighbor-group n1
RP/0/RSP0/CPU0:router(config-bgp-nbr)#tcp mss inheritance-disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
503
BGP Commands
timers (BGP)
timers (BGP)
To set the timers for a specific Border Gateway Protocol (BGP) neighbor, use the timers command in an
appropriate configuration mode. To set the timers to the default values, use the no form of this command.
Syntax Description keepalive Frequency (in seconds) with which the software sends keepalive messages to a neighbor. Range
is 0 to 65535.
hold-time Interval (in seconds) after not receiving a keepalive message from the neighbor that the software
terminates the BGP session for the neighbor. Values are 0 or a number in the range from 3 to
65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The timers actually used in connection with the neighbor may not be the same as those configured with this
command. The actual timers are negotiated with the neighbor when establishing the session. The negotiated
hold time is the minimum of the configured time and the hold time received from the neighbor. If the negotiated
hold time is 0, keepalives are disabled.
The configured value for the keepalive must not exceed one-third of the negotiated hold time. If it does, a
value of one-third of the negotiated hold time is used.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the
group inherit the configuration. Values of commands configured specifically for a neighbor override inherited
values.
In cases where mechanisms such as Bi-directional Forwarding Detection (BFD), BGP fast-external-failover
or Next-hop Tracking cannot be employed to detect and react to changes in the network in a faster manner,
BGP Keepalive and Hold-timer values can be configured to use smaller values than the default (60 and 180
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
504
BGP Commands
timers (BGP)
seconds respectively). When using aggressive values, consider the router's profile and scale, particularly in
respect to the number of BGP neighbours that will be using sessions with the non-default timers.
Sessions using very aggressive values will be more susceptible to flap during events that cause the
Route-Processor's CPU utilization levels to increase. Such events include component OIR, Route-Processor
Failover, network instability, excessive churn in routing protocols etc. It is therefore recommended that the
desired scale and profile of the router be tested with the non-default timer values, subjecting the router to
CPU-intensive events in order to determine the timer threshold values that are appropriate for the router before
configuring the values in an operational network.
The BGP Non-Stop Routing (NSR) is able to sustain sessions with more aggressive timer values than BGP
Graceful Restart (GR) since in the event of a Route-Processor Failover, Graceful Restart (GR) requires the
re-establishment of the TCP session over which the BGP session takes place. When using Non-Stop Routing
(NSR), both the underlying TCP session and BGP session are maintained during Route-Processor failover.
bgp read,
write
Examples The following example shows how to change the keepalive timer to 70 seconds and the hold-time
timer to 210 seconds for the BGP peer 192.168.40.24:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
timers bgp, on page 506 Adjusts BGP network timers for all BGP neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
505
BGP Commands
timers bgp
timers bgp
To change the default timer values for Border Gateway Protocol (BGP) neighbors, use the timers bgp
command in an appropriate configuration mode. To set the default timers to the default values, use the no
form of this command.
Syntax Description keepalive Frequency (in seconds) with which the software sends keepalive messages to a neighbor. Range
is 0 to 65535.
hold-time Interval (in seconds) after not receiving a keepalive message from the neighbor that the software
terminates the BGP session for the neighbor. Values are 0 or a number in the range from 3 to
65535.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the timers bgp command to adjust the default timer times used by all BGP neighbors. The values can
be overridden on particular neighbors using the timers command in the neighbor configuration mode.
The timers actually used in connection with the neighbor may not be the same as those configured with this
command. The actual timers are negotiated with the neighbor when establishing the session. The negotiated
hold time is the minimum of the configured time and the hold time received from the neighbor. If the negotiated
hold time is 0, keepalives are disabled.
The configured value for the keepalive must not exceed one-third of the negotiated hold time. If it does, a
value of one-third of the negotiated hold time is used.
In cases where mechanisms such as Bi-directional Forwarding Detection (BFD), BGP fast-external-failover
or Next-hop Tracking cannot be employed to detect and react to changes in the network in a faster manner,
BGP Keepalive and Hold-timer values can be configured to use smaller values than the default (60 and 180
seconds respectively). When using aggressive values, consider the router's profile and scale, particularly in
respect to the number of BGP neighbors that will be using sessions with the non-default timers.
Sessions using very aggressive values will be more susceptible to flap during events that cause the
Route-Processor's CPU utilization levels to increase. Such events include component OIR, Route-Processor
Failover, network instability, excessive churn in routing protocols etc. It is therefore recommended that the
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
506
BGP Commands
timers bgp
desired scale and profile of the router be tested with the non-default timer values, subjecting the router to
CPU-intensive events in order to determine the timer threshold values that are appropriate for the router before
configuring the values in an operational network.
The BGP Non-Stop Routing (NSR) is able to sustain sessions with more aggressive timer values than BGP
Graceful Restart (GR) since in the event of a Route-Processor Failover, Graceful Restart (GR) requires the
re-establishment of the TCP session over which the BGP session takes place. When using Non-Stop Routing
(NSR), both the underlying TCP session and BGP session are maintained during Route-Processor failover.
bgp read,
write
Examples The following example shows how to configure a default keepalive time of 30 seconds and a default
hold time of 90 seconds:
timers (BGP), on page 504 Adjusts BGP network timers for a BGP neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
507
BGP Commands
transport (rpki-server)
transport (rpki-server)
To choose a transport mechanism for the RPKI cache-server configuration, establish and manage transport
connections, and send or receive byte streams from the network, use the transport command in rpki-server
configuration mode. To disable the transport connection, use the no form of this command.
Syntax Description port Specifies to choose a port number for the RPKI cache transport.
port-number Specifies the port number for the RPKI cache transport. For tcp, the range of supported port
number is 1 to 65535. For ssh, use port number 22.
Note Do not specify a custom port number for RPKI cache transport over SSH is not
supported. You must use port 22 for RPKI over SSH.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The transport can be set to either TCP or SSH. An SSH transport session with port number 22 is the
recommended transport between router and RPKI cache for security reasons.
The transport method (TCP or SSH) can be configured on a per-RPKI-server basis: once server can be TCP
port 980, another can be SSH port 22, for example. This can be changed by configuration. Changing the
transport method will cause the cache session to flap (cleanup its existing transport related data and initialize
the new transport related data).
This example shows how to configure SSH as the transport mechanism and to use port 22 for SSH
communication:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
508
BGP Commands
transport (rpki-server)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
509
BGP Commands
ttl-security
ttl-security
To configure a router to check the time-to-live (TTL) field in incoming IP packets for the specified external
Border Gateway Protocol (eBGP) peer, use the ttl-security command in an appropriate configuration mode.
To disable TTL verification, use the no form of this command.
ttl-security [inheritance-disable]
no ttl-security [inheritance-disable]
Syntax Description inheritance-disable (Optional) Prevents the ttl-security command from being inherited from a session
group or neighbor group.
Release 3.9.0 The disable keyword was replaced with the inheritance-disable keyword.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the ttl-security command to enable a lightweight security mechanism to protect eBGP peering sessions
from CPU utilization-based and other resource exhaustion-based attacks. These types of attacks are typically
brute-force Denial of Service (DoS) attacks that attempt to disable the network by flooding devices in the
network with IP packets that contain forged source and destination IP addresses in the packet headers.
This command leverages existing behavior in IP packets. For a given IP packet, the TTL count of the packet
always is equal to or less than the TTL count when the packet originated, a behavior that is considered
impossible to circumvent. Therefore, a packet received with a TTL count equal to the maximum TTL value
of 255 can be sent only by a directly adjacent peer. When the ttl-security command is configured for an
eBGP neighbor that is directly adjacent, the router accepts only IP packets with a TTL count that is equal to
the maximum TTL value.
The ttl-security command secures the eBGP session in the incoming direction only. In the outbound direction,
it causes packets to be sent only with the maximum TTL value so that the BGP neighbor can also verify the
TTL value of incoming packets. When this command is enabled, BGP establishes or maintains a session only
if the TTL value in the IP packet header is equal to the maximum TTL value. If the value is less than the
maximum TTL value, the packet is discarded and an Internet Control Message Protocol (ICMP) message is
not generated. This behavior is designed because a response to a forged packet is not necessary.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
510
BGP Commands
ttl-security
Note The ttl-security command must be configured on each participating router. Failure to configure this command
on both ends of the BGP session results in the session progressing as far as the OpenSent or OpenConfirm
state, remaining there until the hold time expires.
Note If the ttl-security command is configured on a neighbor to which the router has an established connection
or the router is in the process of establishing a connection, the session must be cleared using the clear bgp
command.
bgp read,
write
Examples The following example shows how to enable TTL security for eBGP neighbor 192.168.223.7:
The following example shows how to enable TTL security for multiple eBGP neighbors using a
session group:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
511
BGP Commands
ttl-security
ebgp-multihop, on page 156 Accepts and attempts BGP connections to external peers residing on networks
that are not directly connected.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
show lpts flows Displays information about locally terminated packet flows, including the
minimum TTL value expected.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
512
BGP Commands
update limit
update limit
To set upper bound on transient memory usage for update generation, use the update limit command in router
configuration mode. To return the bounds to the default value, use the no form of this command.
Syntax Description update-limit-MB Sets the update limit in megabytes (MB). Range is 16 to 2048 MB.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the update limit command to configure a global limit on the size of messages the software queues when
updating peers. Increasing the limit can result in faster Border Gateway Protocol (BGP) convergence, but also
may result in higher memory usage during convergence.
This example shows how to set the update limit as 1024 MB:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
513
BGP Commands
update limit address-family
Syntax Description update-limit-MB Sets the update limit in megabytes (MB). Range is 4 MB to 2048 MB.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the update limit address-family command to configure a global limit on the size of messages the software
queues when updating peers. Increasing the limit can result in faster Border Gateway Protocol (BGP)
convergence, but also may result in higher memory usage during convergence.
This example shows how to set the update limit as 512 MB for address family IPv4 unicast:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#address-family ipv4 unicast
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
514
BGP Commands
update limit address-family
update limit sub-group, on page 516 Sets upper bound on transient memory usage for update generation
for eBGP or iBGP sub-groups.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
515
BGP Commands
update limit sub-group
Syntax Description ebgp Specifies the update limit for eBGP sub-groups.
update-limit-MB Sets the update limit in megabytes (MB). Range is 1 MB to 512 MB.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the update limit sub-group command to configure a global limit on the size of messages the software
queues when updating peers. Increasing the limit can result in faster Border Gateway Protocol (BGP)
convergence, but also may result in higher memory usage during convergence.
This example shows how to set the update limit as 256 MB for eBGP sub-group under address family
IPV4 unicast:
RP/0/RSP0/CPU0:router#configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
516
BGP Commands
update limit sub-group
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
517
BGP Commands
update in error-handling basic disable
Syntax Description ebgp Specifies inbound update message basic error handling for eBGP neighbors.
ibgp Specifies inbound update message basic error handling for iBGP neighbors.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to disable inbound update message basic error handling for eBGP neighbors:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#update in error-handling basic ebgp disable
This example shows how to disable inbound update message basic error handling for iBGP neighbors:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#update in error-handling basic ibgp disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
518
BGP Commands
update in error-handling extended
Syntax Description ebgp Specifies to enable inbound update message extended error handling for eBGP neighbors.
ibgp specifies to enable inbound update message extended error handling for iBGP neighbors.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable inbound update message extended error handling for eBGP
neighbors:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#update in error-handling extended ebgp
This example shows how to enable inbound update message extended error handling for iBGP
neighbors:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#update in error-handling extended ibgp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
519
BGP Commands
update out logging
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#update out logging
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
520
BGP Commands
update-source
update-source
To allow internal Border Gateway Protocol (iBGP) sessions to use the primary IP address from a particular
interface as the local address when forming an iBGP session with a neighbor, use the update-source command
in an appropriate configuration mode. To set the chosen local IP address to the nearest interface to the neighbor,
use the no form of this command.
Syntax Description type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The update-source command is commonly used with the loopback interface feature for iBGP sessions. The
loopback interface is defined, and the interface address is used as the endpoint for a BGP session through the
update-source command. This mechanism allows a BGP session to remain up even if the outbound interface
goes down, provided there is another route to the neighbor.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit
the configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
521
BGP Commands
update-source
Examples The following example shows how to configure this router to use the IP address from the Loopback0
interface when trying to open a session with neighbor 172.20.16.6:
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
522
BGP Commands
update wait-install
update wait-install
To configure BGP to wait for feedback from RIB indicating that the routes that BGP installed in RIB have
been installed in FIB, before BGP send out updates to neighbors, use the update wait-install command in an
appropriate configuration mode.
update wait-install
no update wait-install
This command has no keywords or arguments.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable the update wait-install configuration under VPNv4 unicast
address family:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 65500
RP/0/RSP0/CPU0:router(config-bgp)#address-family vpnv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)#update wait-install
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
523
BGP Commands
use
use
To inherit configuration from a neighbor group, session group, or address family group, use the use command
in an appropriate configuration mode. To discontinue inheritance from a group, use the no form of this
command.
group-name Name of the neighbor group, session group, or address family group from which you want
to inherit configuration.
Neighbor configuration
Neighbor configuration
Session-group configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
524
BGP Commands
use
The use command configures inheritance of configuration from an address family group, neighbor group,
or session group, which means that any configuration for the group also takes effect for the user of the group.
The configuration inherited depends on the type of group that is specified. The group types are described in
the following sections:
Address Family Group
An address family group can specify a configuration for only a single address family. The address family
specified when the address family group was defined (through the af-group command) must match the
address family from which the group is used.
Neighbor Group
A neighbor group (like a neighbor) can have address family-independent configuration and address
family-specific configuration. All of these configurations could be inherited.
Session Group
A session group can have only address family-independent configuration and thus only address
family-independent configuration is inherited from it.
The following rules govern inheritance to resolve possible conflicting configuration:
1. If a command is configured directly on the neighbor that is using group configuration, the command
overrides the value that would be normally inherited from the group.
2. If the neighbor is configured to use a session group (for address family-independent configuration) or an
address family group (for address family-specific configuration) and the command is configured for the
session group or address family group, that configuration is used.
3. The neighbor group configuration is used:
• If the command is not configured directly on the neighbor and the neighbor is not using a session
group (for address family-independent configuration) or an af-group (for address family-specific
configuration).
• The neighbor is using a neighbor group and the command is configured on the neighbor group.
Typically, all configuration for a neighbor group is inherited, but some characteristics may be masked by a
session group or address family group. For an example of this configuration, see the “Examples” section.
If the neighbor is using both a session group and a neighbor group and a specific command is configured for
the neighbor group but not for the session group, then the configuration for the neighbor group does not take
effect. The session group “hides” all address family-independent configuration on the neighbor group and
prevents it from being inherited. Similarly, the use of an address family group hides any address family-specific
configuration that may otherwise be inherited from a neighbor group for that address family.
In addition to neighbors using groups, it is possible to build a hierarchy by having groups use other groups.
The following hierarchical groups are permitted:
• Session groups may use other session groups.
• Address family groups may use other address family groups.
• Neighbor groups may use other neighbor groups.
• Neighbor groups may use session groups and address family groups.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
525
BGP Commands
use
Note Within the Cisco IOS XR system configuration architecture, do not combine the remote-as command and
the no use neighbor-group command in the same commit, or the remote-as command and the no use
session-group command in the same commit.
bgp read,
write
Examples The following example shows how to define a session group session1 and configure neighbor
172.168.40.24 to use session1. As a result, the session1 configuration takes effect on the neighbor
also.
The following example is similar to the previous example, but in this case the timers command on
the session group does not take effect on the neighbor because it is overridden by a timers command
directly configured for the neighbor.
The following example shows an address family group, family1, for IPv4 multicast and a neighbor
group, neighbor1, that have IPv4 unicast and IPv4 multicast enabled. In this case, the neighbor
inherits IPv4 unicast (and address family-independent) configuration from the neighbor group, but
inherits IPv4 multicast configuration from the address family group. In this example, the neighbor
group also has a remote autonomous system configured, so there is no need to configure a remote
autonomous system for the neighbor because it inherits the remote autonomous system from the
neighbor group:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
526
BGP Commands
use
RP/0/RSP0/CPU0:router(config-bgp-afgrp)# exit
RP/0/RSP0/CPU0:router(config-bgp)# neighbor-group neighbor1
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)# remote-as 2
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 in
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 out
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)# exit
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 multicast
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 in
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 out
RP/0/RSP0/CPU0:router(config-bgp-nbrgrp-af)# exit
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 172.168.40.24
RP/0/RSP0/CPU0:router(config-bgp-nbr)# use neighbor-group neighbor1
RP/0/RSP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# use af-group family1
RP/0/RSP0/CPU0:router(config-bgp-nbr-af)# exit
In the previous example, the neighbor uses the policy1 route policy for inbound and outbound IPv4
unicast routes, but uses the mcast-in route policy for inbound IPv4 multicast routes and no policy
for outbound IPv4 multicast routes.
The following example shows a neighbor inheriting configuration from a session group that likewise
inherits configuration from another session group. The configuration from both session groups take
effect on the neighbor:
af-group, on page 27 Creates an address family group for BGP neighbors and enters
address family group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration
mode.
remote-as (BGP), on page 248 Creates a BGP neighbor and begins the exchange of routing
information.
show bgp af-group, on page 317 Displays information about BGP configuration for address family
groups.
show bgp neighbor-group, on page 362 Displays information about the BGP configuration for neighbor
groups.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
527
BGP Commands
use
Command Description
show bgp neighbors, on page 366 Displays information about BGP neighbors.
show bgp session-group, on page 444 Displays information about the BGP configuration for session
groups.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
528
BGP Commands
username (rpki-server)
username (rpki-server)
To specify a SSH username for the RPKI cache-server, use the username command in rpki-server configuration
mode. To remove the username, use the no form of this command.
username user-name
no username user-name
Syntax Description user-name Enters a username to be used for the SSH transport mechanism.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The username configuration applies only if the SSH transport mechanism is active.
This example shows how to configure a username (rpki-user) for the RPKI cache-server SSH transport
mechanism:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router bgp 100
RP/0/RSP0/CPU0:router(config-bgp)#rpki server 172.168.35.40
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)# transport ssh port 22
RP/0/RSP0/CPU0:router(config-bgp-rpki-server)#username rpki-user
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
529
BGP Commands
vrf (BGP)
vrf (BGP)
To configure a VPN routing and forwarding (VRF) instance and enter VRF configuration mode, use the vrf
command in router configuration mode. To remove the VRF instance from the configuration file and restore
the system to its default condition, use the no form of this command.
vrf vrf-name
no vrf vrf-name
Syntax Description vrf-name Name of the VRF instance. The following names cannot be used: all, default, and global.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vrf command to configure a VRF instance. A VRF instance is a collection of VPN routing and
forwarding tables maintained at the provider edge (PE) router.
bgp read,
write
Examples The following example shows how to configure a VRF instance and enter VRF configuration mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
530
BGP Commands
weight
weight
To assign a weight to routes received from a neighbor, use the weight command in an appropriate configuration
mode. To remove the weight command from the configuration file and restore the system to its default
condition in which the software assigns the default weight to routes, use the no form of this command.
weight weight-value
no weight [weight-value]
Command Default Routes learned through another Border Gateway Protocol (BGP) peer have a default weight of 0 and routes
sourced by the local router have a default weight of 32768.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The weight of a route is a Cisco-specific attribute. It is used in the best-path selection process (as the strongest
tie-breaker). See the Implementing BGP on Cisco ASR 9000 Series Router module of the Routing Configuration
Guide for Cisco ASR 9000 Series Routers for information on best path. If there are two BGP routes with the
same network layer reachability information (NLRI), the route with the higher weight is always chosen no
matter what the value of other BGP attributes. Weight only has significance on the local router. Weight is
assigned locally to the router, is a value that only makes sense to the specific router, is not propagated or
carried through any route updates, and never is sent between BGP peers (even within the same AS).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
531
BGP Commands
weight
Note If an address family group, neighbor group, or session group is configured, the configuration inside these
configuration groups will not be effective unless it is applied directly or indirectly to one or more neighbors.
The weight assigned to individual routes can be further manipulated in the inbound route policy of a neighbor
using the set weight command. The set weight command sets the weight directly. If you have particular
neighbors that you want to prefer for most of your outbound traffic, you can assign a higher weight to all
routes learned from that neighbor.
The weight assigned to individual routes may be modified by using an inbound routing policy.
Note For weight changes to take effect, you may need to use the clear bgp soft, on page 138 command.
If this command configures a neighbor group or neighbor address family group, all neighbors using the group
inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
bgp read,
write
Examples The following example shows how to assign a weight of 50 to all IP Version 4 (IPv4) unicast routes
learned through 172.20.16.6:
af-group, on page 27 Creates an address family group for BGP neighbors and enters address family
group configuration mode.
neighbor-group, on page 205 Creates a neighbor group and enters neighbor group configuration mode.
session-group, on page 276 Creates a session group and enters session group configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
532
BGP Flowspec Commands
This module provides command line interface (CLI) commands for configuring BGP Flowspec on the
Cisco ASR 9000 Series Router.
• class-map type traffic (BGP-flowspec), on page 534
• class type traffic, on page 535
• destination prefix, on page 536
• drop (BGP-flowspec), on page 538
• flowspec, on page 539
• flowspec disable, on page 540
• local-install, on page 541
• match destination-address, on page 542
• match destination-port, on page 543
• match dscp, on page 544
• match fragment-type, on page 547
• match icmp code, on page 548
• match icmp type, on page 549
• match packet length, on page 550
• match protocol, on page 551
• match source-address, on page 553
• match source-port, on page 554
• match tcp flag, on page 555
• policy-map, on page 556
• redirect (BGP Flowspec), on page 558
• service-policy, on page 559
• show flowspec, on page 560
• source prefix, on page 561
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
533
BGP Flowspec Commands
class-map type traffic (BGP-flowspec)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to specify class305 as the name of a class and defines a class map for this
class.
RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# class-map type traffic match-all class305
RP/0/RSP0/CPU0:router(config-cmap)# match destination-address ipv4 59.2.1.2 255.255.255.0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
534
BGP Flowspec Commands
class type traffic
Syntax Description class-name Name of the class for the class map. The class name is used for the class map and to configure
policy for the class in the policy map.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to associate a class map with the policy map:
RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# policy-map type pbr p1
RP/0/RSP0/CPU0:router(config-pmap)# class type traffic c1
RP/0/RSP0/CPU0:router(config-pmap-c)# set dscp 34
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
535
BGP Flowspec Commands
destination prefix
destination prefix
To filter flowspec based on destination in flowspec network-layer reachability information (NLRI) using RPL,
and apply on neighbor attach point, use the destination prefix command in route-policy configuration mode.
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
parameter
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the destination prefix command as a conditional expression within an if statement.
Note • For a list of all conditional expressions available within an if statement, see the if command.
• This command takes either a named prefix set or an inline prefix set value as an argument. The condition
returns true if the destination entry matches any entry in the prefix set or inline prefix set. An attempt to
match a destination using a prefix set that is defined but contains no elements returns false.
• The routing policy language (RPL) provides the ability to test destinations for a match to a list of prefix
match specifications using the in operator. The destination prefix command is protocol-independent.
• In Border Gateway Protocol (BGP), the destination of a route is also known as its network-layer
reachability information (NLRI). It comprises a prefix value and a mask length.
• RPL supports both 32-bit IPv4 prefixes, specified in dotted-decimal format, and 128-bit IPv6 prefixes,
specified in colon-separated hexadecimal format.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
536
BGP Flowspec Commands
destination prefix
Examples In this example, prefix filtering is done based on flowspec destination address:
route-policy ipv4_dest_pass
if destination-prefix in ipv4_flow2 then
pass
else
drop
endif
end-policy
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
537
BGP Flowspec Commands
drop (BGP-flowspec)
drop (BGP-flowspec)
To configure a traffic class to discard packets belonging to a specific class, use the drop command in policy-map
class configuration mode. To disable the packet discarding action in a traffic class, use the no form of this
command.
drop
no drop
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
538
BGP Flowspec Commands
flowspec
flowspec
To enter BGP flowspec configuration mode, use the flowspec command in Global configuration mode.
flowspec
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
539
BGP Flowspec Commands
flowspec disable
flowspec disable
To disable flowspec configuration on all interfaces, use the flowspec disable command in interface
configuration mode.
ipv4 | ipv6
flowspec disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples This example shows how to disable flowspec configuration on all interfaces.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet 0/2/0/2
RP/0/RSP0/CPU0:router(config-if)# ipv4 flowspec disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
540
BGP Flowspec Commands
local-install
local-install
To apply local installation of flowspec policy on all interfaces, use the local-install command in appropriate
command mode.
local-install interface-all
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples This example show how to install flowspec policy on all interfaces under flowspec subaddress family
configuration mode.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# flowspec
RP/0/RSP0/CPU0:router(config-flowspec)# address-family ipv4
RP/0/RSP0/CPU0:router(config-flowspec-af)# local-install interface-all
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
541
BGP Flowspec Commands
match destination-address
match destination-address
To identify a specific destination IP address explicitly as a match criterion in a class map, use the match
destination-address command in the class map configuration mode. To remove a specific destination IP
address from the matching criteria for a class map, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
542
BGP Flowspec Commands
match destination-port
match destination-port
To identify a specific destination port as the match criterion for a class map, use the match destination-port
command in class map configuration mode. To remove destination port-based match criteria from a class
map, use the no form of this command.
min-value Lower limit of destination port range to match. Value range is 0 to 65535.
max-value Upper limit of destination port range to match. Value range is 0 to 65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
543
BGP Flowspec Commands
match dscp
match dscp
To identify specific IP differentiated services code point (DSCP) values as match criteria for a class map, use
the match dscp command in class map configuration mode. To remove a DSCP value from a class map,
use the no form of this command.
match dscp {[{ipv4 | | ipv6}] dscp-value [dscp-value1 ... dscp-value7] | [min-value - max-value]}
no match dscp {[{ipv4 | | ipv6}] dscp-value [dscp-value1 ... dscp-value7] | [min-value -
max-value]}
dscp-value IP DSCP value identifier that specifies the exact value or a range of values. Range is 0 - 63. Up
to eight IP DSCP values can be specified to match packets. Reserved keywords can be specified
instead of numeric values. Table 46: IP DSCP Reserved Keywords, on page 545 describes the
reserved keywords.
Command Default Matching on IP Version 4 (IPv4) and IPv6 packets is the default.
Usage Guidelines The match dscp command specifies a DSCP value that is used as the match criteria against which packets
are checked to determine if they belong to the class specified by the class map.
To use the match dscp command, you must first enter the class-map command to specify the name of the
class whose match criteria you want to establish. If you specify more than one match dscp command in a
class map, only the last command entered applies.
The match dscp command examines the higher-order six bits in the type of service (ToS) byte of the IP
header. Only one of the eight values is needed to yield a match (OR operation).
The command supports only eight IP DSCP values. If you try to configure more match statements after all
the eight values are matched, the statements get rejected.
The IP DSCP value is used as a matching criterion only. The value has no mathematical significance. For
instance, the IP DSCP value 2 is not greater than 1. The value simply indicates that a packet marked with the
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
544
BGP Flowspec Commands
match dscp
IP DSCP value of 2 should be treated differently than a packet marked with an IP DSCP value of 1. The
treatment of these marked packets is defined by the user through the setting of policies in policy map class
configuration mode.
DSCP Reserved
Value Keyword
0 default
10 AF11
12 AF12
14 AF13
18 AF21
20 AF22
22 AF23
26 AF31
28 AF32
30 AF33
34 AF41
36 AF42
38 AF43
46 EF
8 CS1
16 CS2
24 CS3
32 CS4
40 CS5
48 CS6
56 CS7
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
545
BGP Flowspec Commands
match dscp
qos read,
write
Examples This example shows how to configure the service policy called policy1 and attach service policy
policy1 to an interface. In this example, class map dscp14 evaluates all packets entering
Packet-over-SONET/SDH (POS) interface 0/1/0/0for an IP DSCP value of 14. If the incoming packet
has been marked with the IP DSCP value of 14, the packet is queued to the class queue with the
bandwidth setting of 300 kbps.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
546
BGP Flowspec Commands
match fragment-type
match fragment-type
To identify a fragment-type as the match criterion for a class map, use the match fragment-type command
in class map configuration mode. To remove fragment-type match criteria from a class map, use the no form
of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
547
BGP Flowspec Commands
match icmp code
min-value Lower limit of ICMP type range to match. Value range is 0 to 255.
max-value Upper limit of ICMP type range to match. Value range is 0 to 255.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
548
BGP Flowspec Commands
match icmp type
min-value Lower limit of ICMP type range to match. Value range is 0 to 255.
max-value Upper limit of ICMP type range to match. Value range is 0 to 255.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
549
BGP Flowspec Commands
match packet length
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
550
BGP Flowspec Commands
match protocol
match protocol
To identify a specific protocol as the match criterion for a class map, use the match protocol command in
class map configuration mode. To remove protocol-based match criteria from a class map, use the no form
of this command.
protocol-value A protocol identifier. A single value for protocol-value (any combination of numbers and
names) can be matched in one match statement.
Usage Guidelines Definitions of traffic classes are based on match criteria, including protocols, access control lists (ACLs),
input interfaces, QoS labels, and experimental (EXP) field values. Packets satisfying the match criteria for a
class constitute the traffic for that class.
The match protocol command specifies the name of a protocol to be used as the match criteria against which
packets are checked to determine if they belong to the class specified by the class map. Available protocol
names are listed in the table that follows.
The protocol-value argument supports a range of protocol numbers. After you identify the class, you may use
the match protocol command to configure its match criteria.
Name Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
551
BGP Flowspec Commands
match protocol
Name Description
ipinip IP in IP tunneling
qos read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
552
BGP Flowspec Commands
match source-address
match source-address
To identify a specific source IP address explicitly as a match criterion in a class map, use the match
source-address command in the class map configuration mode. To remove a specific source IP address from
the matching criteria for a class map, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
553
BGP Flowspec Commands
match source-port
match source-port
To identify a specific source port as the match criterion for a class map, use the match source port command
in class map configuration mode. To remove source port-based match criteria from a class map, use the no
form of this command.
min-value Lower limit of source port range to match. Value range is 0 to 65535.
max-value Upper limit of source port range to match. Value range is 0 to 65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
554
BGP Flowspec Commands
match tcp flag
Syntax Description value TCP flag value. Range is from 1 to 4095 (hexadecimal).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
555
BGP Flowspec Commands
policy-map
policy-map
To create or modify a policy map that can be attached to one or more interfaces to specify a service policy,
use the policy-map command in Global Configuration mode mode. To delete a policy map, use the no form
of this command.
Syntax Description type qos (Optional) Specifies type of the service policy.
Command Default A policy map does not exist until one is configured. Because a policy map is applied to an interface, no
restrictions on the flow of data are applied to any interface until a policy map is created.
Type is QoS when not specified.
Usage Guidelines Use the policy-map command to specify the name of the policy map to be created, added to, or modified
before you can configure policies for classes whose match criteria are defined in a class map. Entering the
policy-map command enables policy map configuration mode in which you can configure or modify the
class policies for that policy map.
You can configure class policies in a policy map only if the classes have match criteria defined for them. Use
the class-map and match commands to configure the match criteria for a class. Because you can configure
a maximum of 1024 classes in one policy map, no policy map can contain more than 1024 class policies. The
maximum number of 1024 classes per policy includes the implicit default class and its child policies.
A single policy map can be attached to multiple interfaces concurrently.
The maximum number of policy maps supported is 2000.
Note When a policy map is applied on a physical port, all subinterfaces under the same physical port inherit the
same policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
556
BGP Flowspec Commands
policy-map
qos read,
write
Examples These examples show how to create a policy map called policy1 and configures two class policies
included in that policy map. The policy map is defined to contain policy specification for class1 and
the default class (called class-default) to which packets that do not satisfy configured match criteria
are directed. Class1 specifies policy for traffic that matches access control list 136.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
557
BGP Flowspec Commands
redirect (BGP Flowspec)
Syntax Description default-route Forwards to the default nexthop for this packet
AS-number: index Enter 2-byte or 4-byte autonomous system number (AS) and index in hexa decimal
or decimal format.
IPv4-address: index Enter IPv4 address and index in hexa decimal or decimal format.
Usage Guidelines You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
The example shows how to redirect PBR traffic to virtual routing and forwarding (VRF) instance:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# policy-map type pbr test1
RP/0/RSP0/CPU0:router(config-pmap)# class type traffic test1
RP/0/RSP0/CPU0:router(config-pmap-c)# redirect nexthot vrf vrf1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
558
BGP Flowspec Commands
service-policy
service-policy
To configure service policy on a flowspec subaddress family interface, use the service-policy command in
appropriate command mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
559
BGP Flowspec Commands
show flowspec
show flowspec
To display flowspec policy information for an interface, use the show flowspec command in EXEC mode.
Syntax Description afi-all Displays flowspec policy applied on IPv4 and IPv6
interfaces.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples This example shows sample output from show flowspec command when vrf, ipv4 and summary
keywords are used.
RP/0/RSP0/CPU0:router# show flowspec vrf vrf1 ipv4 summary
Mon May 19 12:59:41.226 PDT
Flowspec VRF+AFI table summary:
VRF: vrf1
AFI: IPv4
Total Flows: 3
Total Service Policies: 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
560
BGP Flowspec Commands
source prefix
source prefix
To filter flowspec based on source in flowspec network-layer reachability information (NLRI) using RPL,
and apply on neighbor attach point, use the source prefix command in route-policy configuration mode.
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the source prefix command as a conditional expression within an if statement. A comparison that
references a prefix set with zero elements in it returns false.
Note • For a list of all conditional expressions available within an if statement, see the if command.
• The source of a BGP route is the IP peering address of the neighboring router from which the route was
received.
• The prefix set can contain both IPv4 and IPv6 prefix specifications.
route-policy read,
write
Examples In this example, prefix filtering is done based on flowspec source address:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
561
BGP Flowspec Commands
source prefix
prefix-set, on page 1593 Enters a prefix set configuration mode and defines a prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
562
BFD Commands
This module provides command line interface (CLI) commands for configuring Bidirectional Forwarding
Detection (BFD) on the Cisco ASR 9000 Series Router.
• address-family ipv4 unicast (BFD), on page 565
• bfd, on page 567
• bfd address-family ipv4 destination, on page 569
• bfd address-family ipv4 echo minimum-interval, on page 570
• bfd address-family ipv4 fast-detect, on page 572
• bfd address-family ipv4 minimum-interval, on page 573
• bfd address-family ipv4 multiplier, on page 576
• bfd address-family ipv4 timers, on page 579
• bundle coexistence bob-blb, on page 581
• bfd dampening, on page 583
• bfd dampening disable, on page 586
• bfd echo ipv4 bundle-per-member minimum-interval, on page 587
• bfd encap-mode, on page 589
• bfd fast-detect, on page 590
• bfd minimum-interval, on page 593
• bfd mode, on page 597
• bfd multipath include location, on page 598
• bfd multiplier, on page 600
• show bundle , on page 603
• clear bfd counters, on page 604
• clear bfd dampening, on page 606
• echo disable, on page 608
• echo ipv4 source, on page 610
• echo latency detect, on page 612
• echo startup validate, on page 614
• hw-module bfd-hw-offload, on page 616
• interface (BFD), on page 618
• ipv6 checksum, on page 621
• multihop ttl-drop-threshold, on page 623
• show bfd, on page 625
• show bfd client, on page 628
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
563
BFD Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
564
BFD Commands
address-family ipv4 unicast (BFD)
address-family ipv4 unicast address nexthop bfd fast-detect [minimum interval interval] [multiplier
multiplier]
no address-family ipv4 unicast address nexthop bfd fast-detect [minimum interval interval]
[multiplier multiplier]
Syntax Description address Specifies the IPv4 unicast destination address and prefix on which to enable
BFD fast-detection.
bfd fast-detect Enables BFD fast-detection on the specified IPV4 unicast destination address
prefix and on the forwarding next-hop address.
minimum interval interval (Optional) Ensures that the next hop is assigned with the same hello interval.
Replace interval with a number that specifies the interval in milliseconds. Range
is from 10 through 10000.
multiplier multiplier (Optional) Ensures that the next hop is assigned with the same detect multiplier.
Replace multiplier with a number that specifies the detect multiplier. Range is
from 1 through 10.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If the multiplier is changed using the bfd multiplier command, the new parameter is used to update all existing
BFD sessions for the protocol (BGP, IS-IS, MPLS-TE, or OSPF).
static read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
565
BFD Commands
address-family ipv4 unicast (BFD)
Examples The following example shows how to enable BFD on a static route. In this example, BFD sessions
are established with the next-hop 3.3.3.3 when it becomes reachable.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router static
RP/0/RSP0/CPU0:router (config-static)# address-family ipv4 unicast 2.2.2.0/24 3.3.3.3 bfd
fast-detection
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
566
BFD Commands
bfd
bfd
To enter Bidirectional Forwarding Detection (BFD) configuration mode, use the bfd command in global
configuration mode. To exit BFD configuration mode and return to global configuration mode, use the no
form of this command.
bfd
no bfd
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When you issue the bfd command in global configuration mode, the CLI prompt changes to “config-bfd,”
indicating that you have entered BFD configuration mode. In the following sample output, the question mark
(?) online help function displays all the commands available under BFD configuration mode:
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# ?
bgp read,
write
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
567
BFD Commands
bfd
Task Operations
ID
isis read,
write
mpls-te read,
write
Examples The following example shows how to enter BFD configuration mode:
RP/0/RSP0/CPU0:router # configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
568
BFD Commands
bfd address-family ipv4 destination
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is supported on bundle interfaces only.
bundle read,
write
Examples The following example specifies the IPv4 address of 10.20.20.1 as the destination address for the
BFD session on an Ethernet bundle interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 destination 10.20.20.1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
569
BFD Commands
bfd address-family ipv4 echo minimum-interval
Note The interface configuration of the echo timer value takes precedence over the global echo timer value.
Syntax Description milliseconds Shortest interval between sending BFD echo packets to a neighbor. The range is 15 to 2000
milliseconds.
Command Default The default value is the product of the async and multiplier values.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is supported on only on BFD over Bundle Per-Member Link Mode using Cisco standard.
This command allows to configure an echo interval to a value greater than async x bfd multiplier value.
bundle read,
write
Examples The following example specifies that echo packets will be sent at a minimum interval of 900 ms for
IPv4 BFD sessions on member links of an Ethernet bundle:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 minimum-interval 200
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 echo minimum-interval
900
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
570
BFD Commands
bfd address-family ipv4 echo minimum-interval
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
571
BFD Commands
bfd address-family ipv4 fast-detect
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is supported on bundle interfaces only.
bundle read,
write
Examples The following example enables IPv4 BFD sessions on member links of an Ethernet bundle:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 fast-detect
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
572
BFD Commands
bfd address-family ipv4 minimum-interval
Syntax Description milliseconds Shortest interval between sending BFD control packets to a neighbor. The range is 15 to 30000
milliseconds.
Note Although the command allows you to configure a minimum of 15 ms, the supported
minimum is 50 ms.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is supported on bundle interfaces only.
The BFD minimum interval is used with a configurable multiplier (bfd address-family ipv4 multiplier
command) to determine the intervals and failure detection times for both control and echo packets in
asynchronous mode on bundle member links.
For example, with a session interval of I and a multiplier of M, the following packet intervals and failure
detection times apply for BFD asynchronous mode:
• Value of I—Minimum period between sending of BFD control packets.
• Value of I x M
• BFD control packet failure detection time. This is the maximum amount of time that can elapse
without receipt of a BFD control packet before the session is declared down.
• Minimum period between sending of BFD echo packets.
• Value of (I x M) x M—BFD echo packet failure detection time. This is the maximum amount of time
that can elapse without receipt of a BFD echo packet before the session is declared down.
When used with bundled VLANs, the following restrictions apply:
• The command specifies control packet intervals only because echo packets are not supported.
• The minimum interval is 250 ms.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
573
BFD Commands
bfd address-family ipv4 minimum-interval
The bfd address-family ipv4 minimum-interval command in bundle interface configuration overrides the
minimum intervals specified by the bfd minimum-interval command in other areas of BFD configuration.
Note When multiple applications share the same BFD session, the application with the most aggressive timer is
used locally. Then, the result is negotiated with the peer router.
Keep the following router-specific rules in mind when configuring the minimum BFD interval:
• The maximum rate in packets-per-second (pps) for BFD sessions is linecard-dependent. If you have
multiple linecards supporting BFD, then the maximum rate for BFD sessions per system is the supported
linecard rate multiplied by the number of linecards.
• The maximum rate for BFD sessions per linecard is 9600 pps.
To calculate the rate for BFD sessions on bundle members running in asynchronous mode with echo:
• Determine the echo interval, which is the value of the minimum interval (specified by the bfd
address-family ipv4 minimum-interval command) multiplied by the multiplier value (specified by the
bfd address-family ipv4 multiplier command).
Echo interval = (Min-interval x Multiplier)
• Calculate the overall rate supported for all members on the bundle:
Ethernet bundle rate = (1000 / Echo interval) x 64
• Add the asynchronous base rate per bundle member to find the total rate for all bundle links:
Total bundle rate = Ethernet bundle rate + (Base asynchronous rate x Number of links)
bundle read,
write
Examples The following example specifies that control packets will be sent at a minimum interval of 200 ms
for IPv4 BFD sessions on member links of an Ethernet bundle:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 minimum-interval 200
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
574
BFD Commands
bfd address-family ipv4 minimum-interval
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
575
BFD Commands
bfd address-family ipv4 multiplier
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is supported on bundle interfaces only.
The BFD multiplier is used with a configurable minimum interval (bfd address-family ipv4 minimum-interval
command) to determine the intervals and failure detection times for both control and echo packets in
asynchronous mode on bundle member links.
For example, with a session interval of I and a multiplier of M, the following packet intervals and failure
detection times apply for BFD asynchronous mode:
• Value of I—Minimum period between sending of BFD control packets.
• Value of I x M
• BFD control packet failure detection time. This is the maximum amount of time that can elapse
without receipt of a BFD control packet before the session is declared down.
• Minimum period between sending of BFD echo packets.
Note The maximum echo packet interval for BFD on bundle member links is the
minimum of either 30 seconds or the asynchronous control packet failure detection
time.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
576
BFD Commands
bfd address-family ipv4 multiplier
• Value of (I x M) x M—BFD echo packet failure detection time. This is the maximum amount of time
that can elapse without receipt of a BFD echo packet before the session is declared down.
Keep the following router-specific rules in mind when configuring the minimum BFD interval:
• The maximum rate in packets-per-second (pps) for BFD sessions is linecard-dependent. If you have
multiple linecards supporting BFD, then the maximum rate for BFD sessions per system is the supported
linecard rate multiplied by the number of linecards.
• The maximum rate for BFD sessions per linecard is 9600 pps.
To calculate the rate for BFD sessions on bundle members running in asynchronous mode with echo:
• Determine the echo interval, which is the value of the minimum interval (specified by the bfd
address-family ipv4 minimum-interval command) multiplied by the multiplier value (specified by the
bfd address-family ipv4 multiplier command).
Echo interval = (Min-interval x Multiplier)
• Calculate the overall rate supported for all members on the bundle:
Ethernet bundle rate = (1000 / Echo interval) x 64
• Add the asynchronous base rate per bundle member to find the total rate for all bundle links:
Total bundle rate = Ethernet bundle rate + (Base asynchronous rate x Number of links)
bundle read,
write
Task ID
Examples The following example specifies the following packet intervals and failure detection times for IPv4
BFD sessions on member links with asynchronous echo mode on an Ethernet bundle:
• 200 ms control packet interval
• 600 ms control packet failure detection interval
• 600 ms echo packet interval
• 1800 ms echo packet failure detection interval
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
577
BFD Commands
bfd address-family ipv4 multiplier
bfd minimum-interval, on page 593 Specifies the minimum control packet interval for BFD sessions for
the corresponding BFD configuration scope.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
578
BFD Commands
bfd address-family ipv4 timers
Note BFD session flaps when the show tech-support { bfd | cef | spp } command is executed on the system with
30 millisecond timer configured. This occurs only when Cisco ASR 9000 Series Ethernet Line Card is installed
in the system.
Syntax Description start seconds Number of seconds after startup of a BFD member link session to wait for the expected
notification from the BFD peer to be received, so that the session can be declared up. If
the SCN is not received after that period of time, the BFD session is declared down. The
range is 60 to 3600.
Note In Cisco IOS XR Releases 4.0 and 4.0.1, the available minimum is 30, but is
not recommended.
nbr-unconfig Number of seconds to wait after receipt of notification that the BFD configuration has
seconds been removed by a BFD neighbor, so that any configuration inconsistency between the
BFD peers can be fixed. If the BFD configuration issue is not resolved before the specified
timer is reached, the BFD session is declared down. The range is 60 to 3600.
Note In Cisco IOS XR Releases 4.0 and 4.0.1, the available minimum is 30, but is
not recommended.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command is supported on bundle interfaces only.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
579
BFD Commands
bfd address-family ipv4 timers
bundle read,
write
Examples The following example configures a timer for members of the specified Ethernet bundle that allows
up to 1 minute (60 seconds) after startup of a BFD member link session to wait for receipt of the
expected notification from the BFD peer to declare the session up:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 timers start 60
The following example configures a timer for members of the specified Ethernet bundle that allows
up to 1 minute (60 seconds) to wait after receipt of notification that the BFD configuration has been
removed by a BFD neighbor, before declaring a BFD session down:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd address-family ipv4 timers nbr-unconfig 60
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
580
BFD Commands
bundle coexistence bob-blb
Command Default No coexistence configuration is enabled. The BLB configuration behaves the same as the BVLAN configuration.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The default behavior for BLB without any coexistence configuration behaves exactly as the BVLAN
configuration.
When the "inherited" coexistence mode is configured, the BLB session always uses the inherited mode. It
always creates a virtual session, and never a BFD session with real packets. This mode prevents the automatic
conversion between BLB and the inherited mode, which could happen in default mode, depending on the
sequence in which the configuration is applied. The "inherited" session is in "Down" state when BoB is not
enabled.
The "logical" mode always creates BFD session with real packets.
ospf read,
write
isis read,
write
mpls-te read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
581
BFD Commands
bundle coexistence bob-blb
This example shows how to configure the coexistence mechanism between BFD over Bundle (BoB)
and BFD over Logical Bundle (BLB) as being "inherited":
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#bfd
RP/0/RSP0/CPU0:router(config-bfd)#bundle coexistence bob-blb inherit
This example shows how to configure the coexitence mechanism between BFD over Bundle (BoB)
and BFD over Logical Bundle (BLB) as being "logical":
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#bfd
RP/0/RSP0/CPU0:router(config-bfd)#bundle coexistence bob-blb logical
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
582
BFD Commands
bfd dampening
bfd dampening
To configure a device to dampen a flapping Bidirectional Forwarding Detection (BFD) session, use the bfd
dampening command in global configuration mode. To restore the values of the dampening timers to their
default values, use the no form of this command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
583
BFD Commands
bfd dampening
Release 4.2.0 The l3-only-mode keyword was added to the other dampening options.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note The initial-wait, maximum-wait, and secondary-wait keywords are dampening timers.
You do not have to configure the BFD startup timers. If you do configure the initial wait startup timer (using
the initial-wait keyword), then it must be less than the value of the maximum-wait timer.
By default, BFD dampening is applied to all sessions in the following manner:
• If a session is brought down, then dampening is applied before a session is allowed to transition to
initial/up states.
• Length of time a session is dampened grows exponentially with continuous session flap.
• If a session remains up for minimum two minutes, then the length of time a session dampens with the
next session flap is reset to the initial dampening value.
BFD on bundle member applies dampening, only if the detected failure is specific to layer 3. BFD dampening
is not invoked for L1 or L2 failures. BFD is started after Layer 1 and Layer 2 (LACP) is up to prevent a race
condition and false triggers. BFD is notified to stop/ignore when L1 or L2 goes down and must be notified
to start/resume when L1 or L2 recovers for a given/affected link/member.
BFD applies dampening till the session transitions from up to down state and the session is not removed.
Whenever there is a failure detected at L1 or L2 , the bundle manager removes BFD session on a member.
When dampening is removed a syslog message ‘Exponential backoff dampening for BFD session has been
cleared for specified BFD session. When/if same session gets created by application(s), only calculated initial
wait time will be applied’ is generated. If this is the desired behavior, then dampening can be enabled by
configuring the BFD configuration, by using the command bfd dampening bundle-member l3-failure-only.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
584
BFD Commands
bfd dampening
Task Operation
ID
isis read,
write
mpls-te read,
write
This example shows how to configure BFD dampening by specifying an initial and maximum delay
for BFD session startup on BFD bundle members:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd dampening bundle-member initial-wait 1000
RP/0/RSP0/CPU0:router(config)# bfd dampening bundle-member maximum-wait 3000
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd dampening initial-wait 1000
RP/0/RSP0/CPU0:router(config)# bfd dampening maximum-wait 3000
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
585
BFD Commands
bfd dampening disable
ospf read,
write
isis read,
write
mpls-te read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd dampening disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
586
BFD Commands
bfd echo ipv4 bundle-per-member minimum-interval
Syntax Description milliseconds Shortest interval between sending BFD echo packets to a neighbor. The range is 15 to 2000
milliseconds.
Command Default The default value is the product of the async and multiplier values.
Usage Guidelines This command allows you to globally configure an echo interval to a value greater than async*bfd multiplier
value. When the value of echo configured is lesser than the I*M1, where I is the Minimum period between
sending of BFD Async packets and M1 is the remote multiplier, then the echo value is taken as I*M1 and
echo detection time is taken as I*M1*M2 where M2 is the local Multiplier.
This command is supported on only on BFD over Bundle Per-Member Link mode using Cisco standard.
bundle read,
write
Examples The following example specifies that echo packets will be sent globally at a minimum interval of
500 ms for IPv4 BFD sessions on bundle member links:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd echo ipv4 bundle-per-member minimum-interval
500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
587
BFD Commands
bfd echo ipv4 bundle-per-member minimum-interval
Command Description
bfd address-family ipv4 Specifies the minimum interval for asynchronous mode control
minimum-interval, on page 573 packets on IPv4 BFD sessions on bundle member links.
bfd address-family ipv4 echo Specifies the minimum interval for asynchronous mode control
minimum-interval, on page 570 packets on IPv4 BFD sessions on bundle member links.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
588
BFD Commands
bfd encap-mode
bfd encap-mode
To enable continuity check for MPLS LSPs via BFD over Generic Associated Channel Label (GAL) (Label
13), use the bfd encap-mode command in MPLS Traffic Engineering Tunnel (TE) interface configuration
mode. To disable continuity check for MPLS LSPs via BFD running over GAL channel, use the no form of
this command.
Syntax Description gal Specifies the use of BFD over Generic Associated
Channel Label (GAL) (Label 13) for MPLS LSPs.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, BFD is enabled over an IP channel. This command enables BFD over GAL channel.
mpls-te read,
write
Examples This example shows how to enable continuity check for MPLS LSPs via BFD over GAL channel:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface tunnel-te 1
RP/0/RSP0/CPU0:router(config-if)# bfd
RP/0/RSP0/CPU0:router(config-if-tunte-bfd)# encap-mode gal
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
589
BFD Commands
bfd fast-detect
bfd fast-detect
To enable Bidirectional Forwarding Detection (BFD) to detect failures in the path between adjacent forwarding
engines, use the bfd fast-detect command in the appropriate configuration mode. To return the software to
the default state in which BFD is not enabled, use the no form of this command.
Syntax Description disable Disables the detection of failures in the path between adjacent forwarding engines for a specified
entity, such as a BGP neighbor or OSPF interface.
Note The disable keyword is available in the following modes only: BGP configuration,
OSPF area configuration, OSPF area interface configuration, OSPFv3 area
configuration, and OSPFv3 area interface configuration .
ipv4 Enables Intermediate System-to-Intermediate System (IS-IS) BFD detection of failures in the
path between adjacent forwarding engines.
Note The ipv4 keyword is available in IS-IS router configuration mode only.
Command Default BFD detection of failures in the path between adjacent forwarding engines is disabled.
Interface configuration
Interface configuration
Router configuration
Area configuration
Router configuration
Area configuration
Interface configuration
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
590
BFD Commands
bfd fast-detect
Release Modification
Release 4.0.0 The bfd fast-detect command was supported in the following modes: OSPFv3 router
configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
Release 5.3.2 The bfd fast-detect strict-mode command was supported in the following modes: OSPFv3
router configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
Usage Guidelines
Note BFD can support multihop for internal and external BGP peers.
Use the bfd fast-detect command to provide protocol- and media-independent, short-duration failure detection
of the path between adjacent forwarding engines, including the interfaces and data links.
BFD must be configured on directly connected neighbors for a BFD session to be established between the
neighbors.
When MPLS-TE tunnels are protected by backup tunnels, BFD failure triggers fast reroute on affected tunnels.
In OSPF and OSPFv3 environments, the setting of the bfd fast-detect command is inherited from the
highest-level configuration mode in which the command was configured. From the lowest to the highest
configuration modes, the inheritance rules are as follows:
• If you enable BFD in area interface configuration mode, it is enabled on the specified interface only.
• If you enable BFD in area configuration mode, it is enabled on all interfaces in the specified area.
• If you enable BFD in router configuration mode, it is enabled on all areas and all associated interfaces
in the specified routing process.
The disable keyword is available in the following modes: BGP configuration, OSPF area configuration, OSPF
area interface configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration . In OSPF
and OSPFv3 environments, the disable option enables you to override the inheritance rules described previously.
For example, if you enable BFD in an OSPF area, BFD is enabled on all interfaces in that area. If you do not
want BFD running on one of the interfaces in that area, you must specify the bfd fast-detect disable command
for that interface only.
To disable BFD or return the software to the default state in which BFD is not enabled in IS-IS router
configuration mode and MPLS-TE configuration mode, you must enter the no bfd fast-detect command.
bgp read,
write
isis read,
write
mpls-te read,
write
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
591
BFD Commands
bfd fast-detect
Task ID Operations
multicast read,
write
Examples The following example shows how to configure BFD on a BGP router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router bgp 65000
RP/0/RSP0/CPU0:router(config-bgp)# neighbor 192.168.70.24
RP/0/RSP0/CPU0:router(config-bgp-nbr)# remote-as 2
RP/0/RSP0/CPU0:router(config-bgp-nbr)# bfd fast-detect
The following example shows the configuration of an OSPFv3 routing process named san_jose. The
example shows two areas, each of which includes Gigabit Ethernet interfaces. In area 0, BFD is
enabled at the area level, which means that by virtue of the inheritance rules, BFD is enabled on all
interfaces within the area except those on which BFD is explicitly disabled. Given this rule, BFD is
enabled on Gigabit Ethernet interfaces 1/0/0/0 and 2/0/0/0 and is disabled on interface 3/0/0/0.
In area 1, BFD is enabled on Gigabit Ethernet interface 5/0/0/0 only. Because BFD is not enabled
at the area level nor explicitly enabled on interface 4/0/0/0, it is disabled on this interface.
bfd minimum-interval, on page 593 Specifies the minimum control packet interval for BFD sessions
for the corresponding BFD configuration scope.
bfd multiplier, on page 600 Sets the BFD multiplier.
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
592
BFD Commands
bfd minimum-interval
bfd minimum-interval
To specify the minimum control packet interval for BFD sessions for the corresponding BFD configuration
scope, use the bfd minimum-interval command in the appropriate configuration mode. To return the router
to the default setting, use the no form of this command.
Syntax Description milliseconds Interval between sending BFD hello packets to the neighbor. The range is 15 to 30000
milliseconds. For MPLS-TE, the range is 15 to 200 milliseconds. For GRE tunnel, the range
is 150 to 30000 milliseconds. The default is 150 milliseconds.
Interface configuration
MPLS TE configuration
Router configuration
Area configuration
Router configuration
Area configuration
Interface configuration
Tunnel configuration
Release 4.0.0 The bfd minimum-interval command was supported in the following modes: OSPFv3
router configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
Release 6.5.1 The bfd minimum-interval command was supported in the tunnel configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
593
BFD Commands
bfd minimum-interval
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In OSPF and OSPFv3 environments, the setting of the bfd minimum-interval command is inherited from
the highest-level configuration mode in which the command was configured. From the lowest to the highest
configuration modes, the inheritance rules are as follows:
• If you configure the minimum interval in area interface configuration mode, the updated interval affects
the BFD sessions on the specified interface only.
• If you configure the minimum interval in area configuration mode, the updated interval affects the BFD
sessions on all interfaces in the specified area.
• If you configure the minimum interval in router configuration mode, the updated interval affects the BFD
sessions in all areas and all associated interfaces in the specified routing process.
If desired, you can override these inheritance rules by explicitly configuring the bfd minimum-interval
command for a specific area interface or area.
Note When multiple applications share the same BFD session, the application with the most aggressive timer wins
locally. Then, the result is negotiated with the peer router.
Keep the following router-specific rules in mind when configuring the minimum BFD interval:
• The maximum rate in packets-per-second (pps) for BFD sessions is linecard-dependent. If you have
multiple linecards supporting BFD, then the maximum rate for BFD sessions per system is the supported
linecard rate multiplied by the number of linecards.
The maximum rate for BFD sessions per linecard is 9600 pps.
• If a session is running in asynchronous mode without echo, then PPS used for this session is (1000 /
asynchronous interval in milliseconds).
• If a session is running in asynchronous mode with echo, then PPS used for this session is (1000 / echo
interval in milliseconds).
This is calculated as: 1000 / value of the bfd minimum-interval command.
Note The rate for BFD sessions on bundle member links is calculated differently. For more information, see the
bfd address-family ipv4 minimum-interval command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
594
BFD Commands
bfd minimum-interval
• When asynchronous mode is available, the minimum interval must be greater than or equal to 15
milliseconds for up to 100 sessions on the line card. If you are running the maximum of 1440 sessions,
the failure detection interval must be greater than or equal to 150 milliseconds.
• When echo mode is available, the minimum interval must be greater than or equal to 15 milliseconds for
up to 100 sessions on the line card. If you are running the maximum of 1024 sessions, the failure detection
interval must be less than or equal to 150 milliseconds.
• When echo mode is available, the minimum interval must be 50 milliseconds with a multiplier of 3.
• When echo mode is available, the minimum interval must be greater than or equal to 15 milliseconds for
up to 100 sessions on the line card. If you are running the maximum of 1440 sessions, the failure detection
interval must be less than or equal to 150 milliseconds.
bgp read,
write
isis read,
write
mpls-te read,
write
ospf read,
write
multicast read,
write
Examples The following example shows how to set the BFD minimum interval for a BGP routing process:
The following example shows the configuration of an OSPFv3 routing process named san_jose. The
example shows two areas, each of which includes Gigabit Ethernet interfaces. In area 0, the minimum
interval is set to 200 at the area level, which means that by virtue of the inheritance rules, the same
value is set on all interfaces within the area except those on which a different value is explicitly
configured. Given this rule, Gigabit Ethernet interface 1/0/0/0 uses the interval of 200, which is
inherited from the area, while interface 2/0/0/0 uses the explicitly configured value of 300.
In area 1, the minimum interval is not configured at the area or interface levels, which means that
interfaces 3/0/0/0 and 4/0/0/0 use the default interval of 150.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
595
BFD Commands
bfd minimum-interval
bfd fast-detect, on page 590 Enables BFD to detect failures in the path between adjacent
forwarding engines.
bfd multiplier, on page 600 Sets the BFD multiplier.
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
596
BFD Commands
bfd mode
bfd mode
To enable the option to use Cisco or IETF mode for BFD over bundle, use the bfd mode command in interface
configuration mode. To disable the option to use Cisco or IETF mode for BFD over bundle, use the no form
of this command.
no bfd mode
Syntax Description cisco Specifies the use of Cisco mode for BFD over bundle.
ietf Specifies the use of IETF mode for BFD over bundle.
Usage Guidelines If the BFD mode is configured when the bundle is being created, the configuration goes through. This is
because, both the BFD state as well as the bundle state are 'down' during bundle creation. To apply the mode
change for existing sessions, bring down and then recreate the BFD sessions for that bundle.
A BFD session on the member interfaces can belong to only one mode (Cisco or IETF mode). Mix of the
modes within the same bundle is not supported. This command is supported on bundle interfaces only.
bundle read,
write
Examples This example shows how to enable ietf mode for the BFD session on an Ethernet bundle interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface bundle-ether 1
RP/0/RSP0/CPU0:router(config-if)# bfd mode ietf
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
597
BFD Commands
bfd multipath include location
Syntax Description location node-id Configures BFD multipath on the specified location. The node-id variable is mentioned
in the rack/slot/module notation.
Release This command was supported for BFD IPv6 Multihop (BFDv6Mhop) configuration.
4.3.0
Release Support for this command was removed on ASR 9000 Ethernet Line Card.
4.3.1
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
isis read,
write
mpls-te read,
write
Example
This example shows how to run the bfd multipath include location command on a specific location:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
598
BFD Commands
bfd multipath include location
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd multipath include location 0/5/CPU0
show bfd multipath, on page 638 Displays information regarding BFD multipath sessions.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
599
BFD Commands
bfd multiplier
bfd multiplier
To set the Bidirectional Forwarding Detection (BFD) multiplier, use the bfd multiplier command in the
appropriate configuration mode. To return the router to the default setting, use the no form of this command.
Syntax Description multiplier Number of times a packet is missed before BFD declares the neighbor down. The ranges are as
follows:
• BGP—2 to 16
• IS-IS—2 to 50
• MPLS-TE—2 to 10
• OSPF and OSPFv3—2 to 50
• PIM—2 to 50
• GRE tunnel—3 to 50
Interface configuration
MPLS-TE configuration
Router configuration
Area configuration
Area configuration
Interface configuration
Tunnel configuration
Release 4.0.0 The bfd multiplier command was supported in the following modes: OSPFv3 router
configuration, OSPFv3 area configuration, and OSPFv3 area interface configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
600
BFD Commands
bfd multiplier
Release Modification
Release 6.5.1 The bfd multiplier command was supported in tunnel configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In OSPF and OSPFv3 environments, the setting of the bfd multiplier command is inherited from the
highest-level configuration mode in which the command was configured. From the lowest to the highest
configuration modes, the inheritance rules are as follows:
• If you configure a multiplier in area interface configuration mode, the updated multiplier affects the BFD
sessions on the specified interface only.
• If you configure a multiplier in area configuration mode, the updated multiplier affects the BFD sessions
on all interfaces in the specified area.
• If you configure a multiplier in router configuration mode, the updated multiplier affects the BFD sessions
in all areas and all associated interfaces in the specified routing process.
If desired, you can override these inheritance rules by explicitly configuring the bfd multiplier command for
a specific area interface or area.
If the multiplier is changed using the bfd multiplier command, the new value is used to update all existing
BFD sessions for the protocol (BGP, IS-IS, MPLS-TE, OSPF, or OSPFv3) .
bgp read,
write
isis read,
write
mpls-te read,
write
ospf read,
write
multicast read,
write
Examples The following example shows how to set the BFD multiplier in a BGP routing process:
The following example shows the configuration of an OSPFv3 routing process named san_jose. The
example shows two areas, each of which includes Gigabit Ethernet interfaces. In area 0, the multiplier
is set to 5 at the area level, which means that by virtue of the inheritance rules, the same value is set
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
601
BFD Commands
bfd multiplier
on all interfaces within the area except those on which a different value is explicitly configured.
Given this rule, Gigabit Ethernet interface 1/0/0/0 uses a multiplier of 5, which is inherited from the
area, while interface 2/0/0/0 uses the explicitly configured multiplier of 2.
In area 1, a multiplier is not configured at the area or interface levels, which means that interfaces
3/0/0/0 and 4/0/0/0 use the default value of 3.
bfd fast-detect, on page 590 Enables BFD to detect failures in the path between adjacent
forwarding engines.
bfd minimum-interval, on page 593 Specifies the minimum control packet interval for BFD sessions for
the corresponding BFD configuration scope.
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
602
BFD Commands
show bundle
show bundle
To display the IPV6 BFD configured, use the show bundle command in the EXEC mode.
Example
This example shows the output of the show bundle bundle-ether command with IPv6 Bfd configured:
bundle-ether1
Status: Down
Local links <active/standby/configured>: 0 / 0 / 1
Local bandwidth <effective/available>: 0 (0) kbps
MAC address (source): 000a.000b.000c (Configured)
Inter-chassis link: No
Minimum active links / bandwidth: 1 / 1 kbps
Maximum active links: 64
Wait while timer: 2000 ms
Load balancing:
Link order signaling: Not configured
Hash type: Default
Locality threshold: None
LACP: Operational
Flap suppression timer: Off
Cisco extensions: Disabled
Non-revertive: Enabled
mLACP: Not configured
IPv4 BFD: Not configured
IPv6 BFD: Operational
State: Down
Mode: Not configured
Fast detect: Enabled
Start timer: Off
Neighbor-unconfigured timer: Off
Preferred min interval: 150 ms
Preferred multiple: 3
Destination address: 1::1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
603
BFD Commands
clear bfd counters
clear bfd counters {ipv4 | [{singlehop | multihop}] | ipv6 | [{singlehop | multihop}] | all | label} [packet]
[timing] [interface type interface-path-id] location node-id
Syntax Description ipv4 (Optional) Clears BFD over IPv4 information only.
all (Optional) Clears both BFD over IPv4 and BFD over IPv6 information.
interface (Optional) Specifies the interface from which the BFD packet counters are cleared.
type Specifies the interface type. For more information, use the question mark ( ? ) online help
function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
location node-id Clears BFD counters from the specified location. The node-id argument is entered in the
rack/slot/module notation.
Command Default The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or
IPv6.
Release 4.2.0 Support for the singlehop and multihop keywords were added.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
604
BFD Commands
clear bfd counters
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
For the interface-path-id argument, use the following guidelines:
• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values
is required as part of the notation. An explanation of each component of the naming notation is as follows:
• rack: Chassis number of the rack.
• slot: Physical slot number of the line card.
• module: Module number. A physical layer interface module (PLIM) is always 0.
• port: Physical port number of the interface.
• If specifying a virtual interface, the number range varies, depending on interface type.
Both IPv4 and IPv6 BFD sessions can run simultaneously on the same line card.
Examples The following example shows how to clear the BFD IPv6 packet counters on a POS interface:
RP/0/RSP0/CPU0:router# clear bfd counters packet ipv6 interface POS 0/1/0/0 location 0/1/cpu0
The following example shows how to clear the BFD IPv4 timing counters:
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
605
BFD Commands
clear bfd dampening
clear bfd dampening {[interface type interface-path-id] | location node-id all | type [{bundle-logical
| bundle-per-member}]}
Syntax Description interface Specifies the interface from which the BFD dampening
sessions are cleared.
Usage Guidelines For the interface-path-id argument, use the following guidelines:
• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values
is required as part of the notation. An explanation of each component of the naming notation is as follows:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
606
BFD Commands
clear bfd dampening
• If specifying a virtual interface, the number range varies, depending on interface type.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
607
BFD Commands
echo disable
echo disable
To disable echo mode on a router or on an individual interface or bundle, use the echo disable command in
Bidirectional Forwarding Detection (BFD) configuration mode. To return the router to the default configuration
where echo mode is enabled, use the no form of this command.
echo disable
no echo disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you are using BFD with Unicast Reverse Path Forwarding (uRPF), you need to use the echo disable
command to disable echo mode; otherwise, echo packets are rejected.
Note To enable or disable IPv4 uRPF checking on an IPv4 interface, use the [no] ipv4 verify unicast source
reachable-via command in interface configuration mode. To enable or disable loose IPv6 uRPF checking on
an IPv6 interface, use the [no] ipv6 verify unicast source reachable-via any command in interface
configuration mode.
bgp read,
write
ospf read,
write
isis read,
write
mpls-te read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
608
BFD Commands
echo disable
Examples The following example shows how to disable echo mode on a router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo disable
The following example shows how to disable echo mode on an individual interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface gigabitethernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)# echo disable
ipv4 verify unicast source reachable-via Enables and disables IPv4 uRPF checking on an IPv4
interface.
ipv6 verify unicast source reachable-via any Enables and disables loose IPv6 uRPF checking on an IPv6
interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
609
BFD Commands
echo ipv4 source
Command Default The IP address of the output interface, or the IP address in the router-id command (if configured), is the
default address used for an echo packet when the echo ipv4 source command is not configured.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you do not configure the IPv4 source address for echo packets, then BFD uses the IP address of the output
interface or the address in the router-id command if specified.
You can override the default address for BFD echo packets by specifying an IPv4 source address for echo
packets globally for all BFD sessions on the router and at an individual interface. Specifying the IP address
at an individual interface will override any value specified globally for BFD on the router.
bgp read,
write
ospf read,
write
isis read,
write
mpls-te read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
610
BFD Commands
echo ipv4 source
Examples The following example shows how to specify the IP address 10.10.10.1 as the source address for
BFD echo packets for all BFD sessions on the router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo ipv4 source 10.10.10.1
The following example shows how to specify the IP address 10.10.10.1 as the source address for
BFD echo packets on an individual Gigabit Ethernet interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface gigabitethernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)# echo ipv4 source 10.10.10.1
The following example shows how to specify the IP address 10.10.10.1 as the source address for
BFD echo packets on an individual Packet-over-SONET (POS) interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface pos 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)# echo ipv4 source 10.10.10.1
echo disable, on page 608 Disables echo mode on a router or on an individual interface or
bundle.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
611
BFD Commands
echo latency detect
Syntax Description percentage percent-value (Optional) Percentage of the echo failure detection time to be detected as bad
latency. The range is 100 to 250. The default is 100.
count packet-count (Optional) Number of consecutive packets received with the detected bad latency
that will take down a BFD session. The range is 1 to 10. The default is 1.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note Latency detection is only valid where echo mode is supported for BFD. However, it is not supported on bundle
interfaces.
Without latency detection, standard BFD echo failure detection tracks only the absence of receipt of echo
packets within a period of time based on a counter. However, this standard echo failure detection does not
address latency between transmission and receipt of any specific echo packet, which can build beyond desired
tolerances over the course of the BFD session.
When latency detection is enabled, a percentage is multiplied to the echo failure detection value (I x M x %),
and the roundtrip delay is computed for the echo packet. If this delay is greater than (I x M x %), then the
BFD session is taken down.
If you have specified a packet count, then the system tracks the number of packets received back-to-back with
bad latency before taking down the session.
bgp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
612
BFD Commands
echo latency detect
Task Operations
ID
ospf read,
write
isis read,
write
mpls-te read,
write
Examples In the following examples, consider that the BFD minimum interval is 50 ms, and the multiplier is
3 for the BFD session.
The following example shows how to enable echo latency detection using the default values of 100%
of the echo failure period (I x M) for a packet count of 1. In this example, when one echo packet is
detected with a roundtrip delay greater than 150 ms, the session is taken down:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo latency detect
The following example shows how to enable echo latency detection based on 200% (two times) of
the echo failure period for a packet count of 1. In this example, when one packet is detected with a
roundtrip delay greater than 300 ms, the session is taken down:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo latency detect percentage 200
The following example shows how to enable echo latency detection based on 100% of the echo
failure period for a packet count of 3. In this example, when three consecutive echo packets are
detected with a roundtrip delay greater than 150 ms, the session is taken down:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo latency detect percentage 100 count 3
bfd minimum-interval, on page 593 Specifies the minimum control packet interval for BFD sessions
for the corresponding BFD configuration scope.
bfd multiplier, on page 600 Sets the BFD multiplier.
echo startup validate, on page 614 Enables verification of the echo packet path before starting a
BFD session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
613
BFD Commands
echo startup validate
Syntax Description force (Optional) Ignores the remote 'Required Min Echo RX Interval' setting.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note Echo validation is only valid where echo mode is supported for BFD. However, it is not supported on bundle
interfaces.
When a BFD session is down and the echo startup validate command is configured, an echo packet is
periodically transmitted on the link while it is down to verify successful transmission within the configured
latency before allowing the BFD session to change state.
Without the force option, the echo validation test only runs if the last received control packet contains a
non-zero “Required Min Echo RX Interval” value. When the force keyword is configured, the echo validation
test runs regardless of this value.
bgp read,
write
ospf read,
write
isis read,
write
mpls-te read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
614
BFD Commands
echo startup validate
Examples The following example shows how to enable echo startup validation for BFD sessions on non-bundle
interfaces if the last received control packet contains a non-zero “Required Min Echo RX Interval”
value:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo startup validate
The following example shows how to enable echo startup validation for BFD sessions on non-bundle
interfaces regardless of the “Required Min Echo RX Interval” value in the last control packet:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# echo startup validate force
echo latency detect, on page 612 Enables latency detection for BFD echo packets.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
615
BFD Commands
hw-module bfd-hw-offload
hw-module bfd-hw-offload
To enable BFD hardware offload mode, use the hw-module bfd-hw-offload command in admin mode. To
disable BFD hardware offload mode, use the no form of this command.
Note • The BFD hardware offload mode is supported on Cisco ASR 9000 Enhanced Ethernet Line Card and
Cisco ASR 9000 High Density 100GE Ethernet Line Card.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
BFD hardware offload mode is disabled by default. You can enable it in admin mode.
You must reload the line cards after enabling or disabling BFD hardware offload mode for the configuration
to take effect.
root read,
write
Examples The below example shows how to enable BFD hardware offload mode on the ASR 9000 Enhanced
Ethernet Line Card in the location 0/0/CPU0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
616
BFD Commands
hw-module bfd-hw-offload
RP/0/RSP0/CPU0:router# admin
RP/0/RSP0/CPU0:router(admin)# hw-module bfd-hw-offload enable location 0/0/CPU0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
617
BFD Commands
interface (BFD)
interface (BFD)
To enter Bidirectional Forwarding Detection (BFD) interface configuration mode, where you can disable echo
mode on an interface, use the interface command in BFD configuration mode. To return to BFD configuration
mode, use the no form of this command.
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online help
function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
For the interface-path-id argument, use the following guidelines:
• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values
is required as part of the notation. An explanation of each component of the naming notation is as follows:
• rack: Chassis number of the rack.
• slot: Physical slot number of the line card.
• module: Module number. A physical layer interface module (PLIM) is always 0.
• port: Physical port number of the interface.
• If specifying a virtual interface, the number range varies, depending on interface type.
If you are using BFD with Unicast Reverse Path Forwarding (uRPF) on a particular interface, then you need
to use the echo disable command in BFD interface configuration mode to disable echo mode on that interface;
otherwise, echo packets are rejected by the interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
618
BFD Commands
interface (BFD)
Note To enable or disable IPv4 uRPF checking on an IPv4 interface, use the [no] ipv4 verify unicast source
reachable-via command in interface configuration mode. To enable or disable loose IPv6 uRPF checking on
an IPv6 interface, use the [no] ipv6 verify unicast source reachable-via any command in interface
configuration mode.
bgp read,
write
ospf read,
write
isis read,
write
mpls-te read,
write
Examples The following example shows how to enter BFD interface configuration mode for a Gigabit Ethernet
interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface gigabitethernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)#
The following example shows how to enter BFD interface configuration mode for a
Packet-over-SONET/SDH (POS) interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface pos 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)#
echo disable, on page 608 Disables echo mode on an individual interface or on the
entire router.
ipv4 verify unicast source reachable-via Enables and disables IPv4 uRPF checking on an IPv4
interface.
ipv6 verify unicast source reachable-via any Enables and disables loose IPv6 uRPF checking on an IPv6
interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
619
BFD Commands
interface (BFD)
Command Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
620
BFD Commands
ipv6 checksum
ipv6 checksum
To enable and disable IPv6 checksum calculations on BFD UDP packets globally or on a BFD interface, use
the ipv6 checksum command in Bidirectional Forwarding Detection (BFD) or BFD interface configuration
mode. To return to the default, use the no form of this command.
BFD Configuration
ipv6 checksum disable
no ipv6 checksum disable
Syntax Description disable (Optional for BFD interface configuration only) Disables IPv6 checksum calculations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
IPv6 checksum calculations for UDP packets are disable by default for BFD sessions. You can enable IPv6
checksum support either globally for all BFD sessions, or on an individual interface.
bgp read,
write
ospf read,
write
isis read,
write
mpls-te read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
621
BFD Commands
ipv6 checksum
Examples The following example shows how to enable IPv6 checksum calculations for UDP packets for all
BFD sessions on the router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# no ipv6 checksum disable
The following example shows how to disable IPv6 checksum calculations for UDP packets for all
BFD sessions on the router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# ipv6 checksum disable
The following example shows how to enable echo mode for BFD sessions on an individual interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface gigabitethernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)# ipv6 checksum
The following example shows how to disable echo mode for BFD sessions on an individual interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd
RP/0/RSP0/CPU0:router(config-bfd)# interface gigabitethernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-bfd-if)# ipv6 checksum disable
interface (BFD), on page 618 Enters BFD interface configuration mode, where you can disable
echo mode on an interface.
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
622
BFD Commands
multihop ttl-drop-threshold
multihop ttl-drop-threshold
To specify the maximum time to live (TTL) value for multihop sessions per system, use the multihop
ttl-drop-threshold command in the BFD configuration mode. To return to the default, use the no form of
this command.
Syntax Description value Specifies the configurable range of values for TTL. It ranges from 0 to 254.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If the TTL of a BFD packet received on the router is less than the configured ttl-drop-threshold, the packet
will be dropped. If the TTL of a BFD packet received on the router is greater than or equal to the configured
ttl-drop-threshold, the packet will be processed.
Note This configuration command is only applicable for BFD multihop sessions.
ospf read,
write
isis read,
write
mpls-te read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
623
BFD Commands
multihop ttl-drop-threshold
Example
This example shows how to set the maximum TTL value as 2 using the multihop ttl-drop-threshold
command:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# bfd multihop ttl-drop-threshold 2
show bfd multipath, on page 638 Displays information regarding BFD multipath sessions.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
624
BFD Commands
show bfd
show bfd
To display Bidirectional Forwarding Detection (BFD) information for a specific location, use the show bfd
command in EXEC mode.
Syntax Description ipv4 (Optional) Displays BFD over IPv4 information only.
all (Optional) Displays both BFD over IPv4 and BFD over IPv6 information.
location Displays BFD information for the specified location. The node-id argument is entered in
node-id the rack/slot/module notation.
Command Default The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or
IPv6.
Release 5.1.1 The command output was modified to include hardware offload info.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
625
BFD Commands
show bfd
bgp read
ospf read
isis read
mpls-te read
Examples The following example shows the output from the show bfd command:
The following example shows the output from the show bfd all command:
IPv4:
-----
IPV4 Sessions Up: 20, Down: 0, Unknown/Retry: 2, Total: 22
IPv6:
-----
IPV6 Sessions Up: 128, Down: 2, Unknown/Retry: 1, Total: 131
Label:
-----
Label Sessions Up: 10, Down: 0, Unknown/Retry: 1, Total: 11
The following example shows the output from the show bfd ipv4 command:
The following example shows the output from the show bfd ipv6 command:
The following example shows the output from the show bfd ipv4 location command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
626
BFD Commands
show bfd
Platform Info:
NPU ID: 0
Async RTC ID : 1 Echo RTC ID : 0
Async Feature Mask : 0x8 Echo Feature Mask : 0x0
Async Session ID : 0x3c07 Echo Session ID : 0x0
Async Tx Key : 0x3c070801 Echo Tx Key : 0x0
Async Tx Stats addr : 0x3f69e800 Echo Tx Stats addr : 0x0
Async Rx Stats addr : 0x4069e800 Echo Rx Stats addr : 0x0
The following example shows the output from the show bfd ipv6 session detail interface tenGigE
0/0/0/0.100 command displaying BFD hardware offload information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
627
BFD Commands
show bfd client
Syntax Description detail (Optional) Specifies detailed client information including number of sessions and client reconnects.
Command Default Enter the show bfd client command without specifying the detail keyword to display summarized BFD client
information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read
ospf read
isis read
mpls-te read
Examples The following example shows the output from the show bfd client command:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
628
BFD Commands
show bfd client
Field Description
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
629
BFD Commands
show bfd counters
show bfd counters [{ipv4 | [{singlehop | multihop}] | ipv6 [{singlehop | multihop}]| all| label}]
packet [interface type interface-path-id] location node-id
Syntax Description ipv4 (Optional) Displays BFD over IPv4 information only.
all (Optional) Displays both BFD over IPv4 and BFD over IPv6 information.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online help
function.
location node-id Displays BFD counters from the specified location. The node-id argument is entered in
the rack/slot/module notation.
Command Default The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or
IPv6.
Release 4.2.0 Support for the singlehop and multihop keywords were added.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
630
BFD Commands
show bfd counters
• If specifying a virtual interface, the number range varies, depending on interface type.
bgp read
ospf read
isis read
mpls-te read
Examples The following example shows the output from the show bfd counters packet command for both
IPv4 and IPv6:
RP/0/RSP0/CPU0:router# show bfd counters packet all interface POS 0/1/0/0 location
0/1/cpu0
Mon Nov 5 08:49:51.950 UTC
IPv4:
-----
POS 0/1/0/0 Recv Xmit Recv Xmit
Async: 520 515 Echo: 9400 9400
IPv6:
-----
POS 0/1/0/0 Recv Xmit Recv Xmit
Async: 237 237 Echo: 0 0
The following example shows the output from the show bfd counters packet command for IPv4:
IPv4 Singlehop:
GigabitEthernet0/0/1/2 Recv Xmit Recv Xmit
Async: 4148 4137 Echo: ( 47136) 80192
GigabitEthernet0/1/1/2 Recv Xmit Recv Xmit
Async: 116876 125756 Echo: ( 2268192) 2301312
Bundle-Ether10 Recv Xmit Recv Xmit
Async: 2 0 Echo: 0 0
Bundle-Ether20 Recv Xmit Recv Xmit
Async: 91 0 Echo: 0 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
631
BFD Commands
show bfd counters
Field Description
Async Number of asynchronous mode (control) packets that were received or transmitted on the specified
interface.
Echo Number of echo packets that were received or transmitted on the specified interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
632
BFD Commands
show bfd hw-offload
Syntax Description state Displays if BFD hardware offload is enabled or disabled on the line card.
summary Displays total number of sessions configured for each timer interval on the line card and network
processor unit.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This is the sample output from the show bfd hw-offload command when state is used:
0/0/CPU0
-----------------
Configuration State: Enabled
Operational State: Enabled
This is the sample output from the show bfd hw-offload command when summary is used:
0/2/CPU0
==========
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
633
BFD Commands
show bfd hw-offload
---------------------------------------------------------------------
LC:
----
Tx Used 0 0 8000 0 0 0 0
Rx Used 0 0 8000 0 0 0 0
Tx Avail 0 0 0 0 0 0 0
Rx Avail 0 0 0 0 0 0 0
NP0:
-----
Tx Used 0 0 3000 0 0 0 0
Rx Used 0 0 3000 0 0 0 0
Tx Avail 0 0 0 0 0 0 0
Rx Avail 0 0 0 0 0 0 0
NP1:
-----
Tx Used 0 0 3000 0 0 0 0
Rx Used 0 0 3000 0 0 0 0
Tx Avail 0 0 0 0 0 0 0
Rx Avail 0 0 0 0 0 0 0
NP2:
-----
Tx Used 0 0 0 0 0 0 0
Rx Used 0 0 0 0 0 0 0
Tx Avail 0 0 0 0 0 0 0
Rx Avail 0 0 0 0 0 0 0
NP3:
-----
Tx Used 0 0 2000 0 0 0 0
Rx Used 0 0 2000 0 0 0 0
Tx Avail 0 0 0 0 0 0 0
Rx Avail 0 0 0 0 0 0 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
634
BFD Commands
show bfd mib session
Syntax Description location (Optional) Displays all IPv4 and IPv6 BFD MIB session information stored on the specified
node-id node. The node-id argument is entered in the rack/slot/module notation.
Command Default When node-id is not specified, information for all IPv4 and IPv6 BFD MIB sessions, stored on the route
processor node, is displayed.
Release 4.0.0 Support for the display of IPv6 BFD MIB session information was added.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When node-id is not specified, information for all IPv4 and IPv6 BFD MIB sessions, stored on the route
processor node, is displayed, and this information is populated and updated only after SNMP operations for
those BFD MIB sessions are performed.
When node-id is specified, information for all IPv4 and IPv6 BFD MIB sessions, stored on the specified node
(linecard), is displayed, and this information is updated automatically without SNMP operations being
performed.
bgp read
ospf read
isis read
mpls-te read
Examples The following example displays all IPv4 and IPv6 BFD MIB session information stored on the RP
node:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
635
BFD Commands
show bfd mib session
The following example displays all IPv4 and IPv6 BFD MIB session information stored on 0/1/CPU0:
Field Description
date and timestamp Date and time stamp during which a snapshot of the BFD MIB session
information is taken.
Local Discr Local discriminator (in decimal and hexadecimal) that uniquely identifies
the BFD MIB session.
Remote Discr Session discriminator (in decimal and hexadecimal) that was chosen by the
remote system for the BFD MIB session.
BFD session Index of interface upon which the BFD MIB session is running. Also,
neighboring IP address that is monitored with the BFD MIB session.
Number of Times UP Number of times the BFD MIB session has gone into the up state since the
router was last rebooted.
Running Version BFD protocol version number in which the BFD MIB session is running.
Last Down Diag Diagnostic value associated with the last time the BFD MIB session went
down.
Last Up Time (s.ns) Value of sysUpTime, in seconds.nanoseconds, during which the BFD MIB
session last came up. If such an event does not exist, a zero is displayed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
636
BFD Commands
show bfd mib session
Field Description
Last Down Time (s.ns) Value of sysUpTime, in seconds.nanoseconds, during which communication
was last lost with the neighbor. If such an event does not exist, a zero is
displayed.
Desired Min TX Interval Minimum interval, in microseconds, preferred by the local system when
transmitting BFD control packets.
Required Min RX Interval Minimum interval, in microseconds, that the local system supports between
received BFD control packets.
Required Min RX Echo Interval Minimum interval, in microseconds, that the local system supports between
received BFD echo packets.
Packets in/out Total number of BFD messages received and transmitted for the BFD MIB
session.
Current Trap Bitmap Bits that control the trap for the BFD MIB session. A nonzero value
indicates that the trap is generated when the next trap event is triggered.
Last Time Cached When information for the BFD MIB session was last cached. Typically,
the information is cached when SNMP operations for the BFD MIB session
are performed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
637
BFD Commands
show bfd multipath
all Displays both BFD over IPv4 and BFD over IPv6
information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
isis read
mpls-te read
Example
This example shows the sample output for show bfd multipath command:
RP/0/RSP0/CPU0:routershow bfd multipath location 0/5/cpu0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
638
BFD Commands
show bfd multipath
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
639
BFD Commands
show bfd neighbor
dampened Displays dampening information about the BFD sessions which are currently dampened.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example displays the sample output of show bfd neighbor detail
IPv4 Sessions
NeighAddr LD/RD RH/RS State Int
10.0.0.2 1/0 Down Down Et0/0
Session Host: Software
OurAddr: 10.0.0.1
Handle: 1
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 1000000, MinRxInt: 1000000, Multiplier: 3
Received MinRxInt: 0, Received Multiplier: 0
Holddown (hits): 0(0), Hello (hits): 1000(0)
Rx Count: 0, Rx Interval (ms) min/max/avg: 0/0/0 last: 1257099 ms ago
Tx Count: 0, Tx Interval (ms) min/max/avg: 0/0/0 last: 1257099 ms ago
Elapsed time watermarks: 0 0 (last: 0)
Dampening: penalty: 0 - not dampened
flap count: 0 - halflife: 2 sec
reuse threshold: 2000 - suppress threshold: 3000
max suppress time: 6 sec
Registered protocols: Stub CEF
Last packet: Version: 1 - Diagnostic: 0
State bit: AdminDown - Demand bit: 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
640
BFD Commands
show bfd neighbor
This example displays the sample output of show bfd neighbor dampening
This example displays the sample output of show bfd neighbor dampened
IPv4 Sessions
NeighAddr[vrf] LD/RD RH/RS State
20.0.0.1 1/0 Down Down
Dampening: penalty: 4500 - dampened
flap count: 10 - halflife: 2 sec
reuse threshold: 2000 - suppress threshold: 3000
max suppress time: 6 sec
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
641
BFD Commands
show bfd session
show bfd [{ipv4 | [{singlehop | multihop}] | ipv6 | [{singlehop | multihop}] | all | label}] session
[interface type interface-path-id [destination ip-address] [detail][in-label]] location node-id
Syntax Description ipv4 (Optional) Displays BFD over IPv4 information only.
all (Optional) Displays both BFD over IPv4 and BFD over IPv6 information.
label (Optional) Displays the MPLS Transport Profile (MPLS-TP) label BFD information
only.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
destination ip-address (Optional) Displays the BFD session destined for the specified IP address.
detail (Optional) Displays detailed session information, including statistics and number of
state transitions.
in-label (Optional) Displays the BFD session with a specific incoming MPLS-TP label.
location node-id (Optional) Displays BFD sessions hosted from the specified location. The node-id
argument is entered in the rack/slot/module notation.
Command Default The default is the default address family identifier (AFI) that is set by the set default-afi command, IPv4 or
IPv6.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
642
BFD Commands
show bfd session
Release Modification
Release 4.2.0 Support for the singlehop and multihop keywords were added.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
For the interface-path-id argument, use the following guidelines:
• If specifying a physical interface, the naming notation is rack/slot/module/port. The slash between values
is required as part of the notation. An explanation of each component of the naming notation is as follows:
• rack: Chassis number of the rack.
• slot: Physical slot number of the line card.
• module: Module number. A physical layer interface module (PLIM) is always 0.
• port: Physical port number of the interface.
• If specifying a virtual interface, the number range varies, depending on interface type.
Note Only VRF ID is displayed in the summary CLI (such as show bfd multiple-path, show bfd all session, show
bfd counters) and VRF name and VRF ID is displayed in the detailed CLI (such as show bfd all session
detail, show bfd all session status).
bgp read
ospf read
isis read
mpls-te read
Examples The following example shows the output from the show bfd session command with the detail
keyword and IPv4 as the default:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
643
BFD Commands
show bfd session
Transmitted parameters:
Version:1, desired tx interval:2 s, required rx interval:2 s
Required echo rx interval:1 ms, multiplier:3, diag:None
My discr:590028, your discr:589830, state UP, D/F/P/C/A:0/0/0/1/0
Timer Values:
Local negotiated async tx interval:2 s
Remote negotiated async tx interval:2 s
Desired echo tx interval:250 ms, local negotiated echo tx interval:250 ms
Echo detection time:750 ms(250 ms*3), async detection time:6 s(2 s*3)
Local Stats:
Intervals between async packets:
Tx:Number of intervals=100, min=952 ms, max=2001 ms, avg=1835 ms
Last packet transmitted 606 ms ago
Rx:Number of intervals=100, min=1665 ms, max=2001 ms, avg=1828 ms
Last packet received 1302 ms ago
Intervals between echo packets:
Tx:Number of intervals=100, min=250 ms, max=252 ms, avg=250 ms
Last packet transmitted 188 ms ago
Rx:Number of intervals=100, min=250 ms, max=252 ms, avg=250 ms
Last packet received 187 ms ago
Latency of echo packets (time between tx and rx):
Number of packets:100, min=1 ms, max=2 ms, avg=1 ms
Desired Adjusted
Client Interval Multiplier Interval Multiplier
-------------------- --------------------- ---------------------
ipv4_static 500 ms 3 500 ms 3
bgp-default 1500 ms 3 1500 ms 3
The following example shows the output from the show bfd session command with the all keyword,
which displays both IPv4 and IPv6 information:
IPv6:
-----
Interface Dest Addr
Local det time(int*mult) State
Echo Async
------------------- ----------------------------------------------
PO0/1/0/0 abcd::2
0s(0s*0) 15s(5s*3) UP
Field Description
Location Location of the node that hosts the local endpoint of the connection, in the rack/slot/module
notation
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
644
BFD Commands
show bfd session
Field Description
State Current state of the connection, and the number of days, hours, minutes, and seconds that
this connection has been active.
number of times Number of times this connection has been brought up.
UP
Received Provides information on the last transmitted control packet for the session:
parameters
• Version—Version number of the BFD protocol.
• desired tx interval—Desired transmit interval.
• required rx interval—Required receive interval.
• Required echo rx interval—Required echo receive interval.
• multiplier— Number of times a packets is missed before BFD declares the neighbor
down.
• diag—diagnostic code specifying the peer system's reason for the last transition of
the session from Up to some other state.
• My discr—unique, nonzero discriminator value generated by the transmitting system,
used to demultiplex multiple BFD sessions between the same pair of systems.
• your discr— discriminator received from the corresponding remote system. This field
reflects back the received value of My discr, or is zero if that value is unknown.
Transmitted Provides information on the last transmitted control packet for the session:
parameters
• Version—Version number of the BFD protocol.
• desired tx interval—Desired transmit interval.
• required rx interval—Required receive interval
• Required echo rx interval—Required echo receive interval
• multiplierNumber of times a packets is missed before BFD declares the neighbor
down.
• diag—diagnostic code specifying the local system's reason for the last transition of
the session from Up to some other state.
• My discr—unique, nonzero discriminator value generated by the transmitting system,
used to demultiplex multiple BFD sessions between the same pair of systems.
• your discr— discriminator received from the corresponding remote system. This field
reflects back the received value of My discr, or is zero if that value is unknown.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
645
BFD Commands
show bfd session
Field Description
Timer Values Provides information on the timer values used by the local and remote ends, as follows:
• Local negotiated async tx interval—interval at which control packets are being
transmitted by the local end.
• Remote negotiated async tx interval—interval at which control packets should be
transmitted by the remote end.
• Desired echo tx interval—interval at which the local end would like to transmit echo
packets.
• local negotiated echo tx interval—interval at which echo packets are being transmitted
by the local end.
• Echo detection time—local failure detection time of echo packets. It is the product
of the local negotiated echo tx interval and the local multiplier.
• async detection time—local failure detection time of the asynchronous mode (control
packets). It is the product of the remote negotiated async tx interval and the remote
multiplier.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
646
BFD Commands
show bfd session
Field Description
Session owner Provides the following information about the session owner.
information
• Client—name of the client application process.
• Desired interval—desired interval provided by the client, in milliseconds.
• Multiplier—multiplier value provided by the client.
show bfd mib session, on page 635 Displays BFD MIB session information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
647
BFD Commands
show bfd summary
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
isis read
mpls-te read
Example
This example shows the sample output from the show bfd summary command for a specified
location:
RP/0/RSP0/CPU0:routershow bfd summary location 0/1/cpu0
This example shows the sample output from the show bfd summary command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
648
BFD Commands
show bfd summary
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
649
BFD Commands
show bfd summary
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
650
IS-IS Commands on Cisco ASR 9000 Series
RouterCisco IOS XR Software
• address-family (IS-IS), on page 654
• address-family multicast topology (IS-IS), on page 656
• adjacency-check disable, on page 658
• adjacency stagger, on page 660
• attached-bit receive ignore, on page 662
• attached-bit send, on page 663
• circuit-type, on page 665
• clear isis process, on page 667
• clear isis route, on page 668
• clear isis statistics, on page 670
• csnp-interval, on page 672
• default-information originate (IS-IS), on page 674
• disable (IS-IS), on page 676
• distance (IS-IS), on page 677
• fast-reroute per-link (IS-IS), on page 679
• fast-reroute per-prefix (IS-IS), on page 681
• fast-reroute per-link priority-limit (IS-IS), on page 683
• fast-reroute per-prefix load-sharing disable (IS-IS), on page 685
• fast-reroute per-prefix tiebreaker (IS-IS), on page 686
• hello-interval (IS-IS), on page 688
• hello-multiplier, on page 690
• hello-padding, on page 692
• hello-password, on page 694
• hello-password keychain, on page 696
• hello-password accept, on page 698
• hostname dynamic disable, on page 700
• ignore-lsp-errors, on page 701
• instance-id, on page 702
• interface (IS-IS), on page 703
• ipfrr lfa, on page 705
• ipfrr lfa exclude interface, on page 707
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
651
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
652
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
653
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
address-family (IS-IS)
address-family (IS-IS)
To enter address family configuration mode for configuring Intermediate System-to-Intermediate System
(IS-IS) routing that use standard IP Version 4 (IPv4) and IP Version 6 (IPv6) address prefixes, use the
address-family command in router configuration or interface configuration mode. To disable support for an
address family, use the no form of this command.
Command Default An address family is not specified. The default subaddress family (SAFI) is unicast.
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the address family command to place the router or interface in address family configuration mode. In
router address family configuration mode, you can configure routing that uses standard IPv4 or IPv6 address
prefixes. An address family must be specified in interface configuration mode. In interface address family
configuration mode, you can alter interface parameters for IPv4or IPv6.
You must specify an address family in order to configure parameters that pertain to a single address family.
isis read,
write
Examples The following example shows how to configure the IS-IS router process with IPv4 unicast address
prefixes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
654
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
address-family (IS-IS)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
655
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
address-family multicast topology (IS-IS)
maximum prefix Specifies maximum number of prefixes that a routing table can have.
Command Default An address family for multicast topology is not specified. The default subaddress family (SAFI) is unicast.
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the address family multicast topology command to place the router or interface in address family
configuration mode. In router address family configuration mode, you can associate an IS-IS topology ID
with the topology you have created to add connected and local routes to a specific routing table.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
656
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
address-family multicast topology (IS-IS)
Examples The following example shows how to configure the IS-IS router topology with an IPv4 multicast
address prefix:
or
topology-id, on page 857 Associates a topology ID with a named IS-IS topology to differentiate topologies
in the domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
657
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
adjacency-check disable
adjacency-check disable
To suppress Intermediate System-to-Intermediate System (IS-IS) IP Version 4 (IPv4) or IP Version 6 (IPv6)
protocol-support consistency checks that are performed prior to forming adjacencies on hello packets, use the
adjacency-check disable command in address family configuration mode. To remove this function, use the
no form of this command.
adjacency-check disable
no adjacency-check disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
IS-IS performs consistency checks on hello packets and forms an adjacency only with a neighboring router
that supports the same set of protocols. A router running IS-IS for both IPv4 and IPv6 does not form an
adjacency with a router running IS-IS for IPv4 only.
Use the adjacency-check disable command to suppress the consistency checks for IPv6 IS-IS and allow an
IPv4 IS-IS router to form an adjacency with a router running IPv4 IS-IS and IPv6. IS-IS never forms an
adjacency between a router running IPv4 IS-IS only and a router running IPv6 only.
In addition, the adjacency-check disable command suppresses the IPv4 or IPv6 subnet consistency check
and allows IS-IS to form an adjacency with other routers regardless of whether they have an IPv4 or IPv6
subnet in common.
isis read,
write
Examples The command in the following example disables the adjacency checks:
The following example shows how the network administrator introduces IPv6 into an existing IPv4
IS-IS network and ensures that the checking of hello packet checks from adjacent neighbors is disabled
until all neighbor routers are configured to use IPv6:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
658
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
adjacency-check disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
659
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
adjacency stagger
adjacency stagger
To configure staggering of IS-IS adjacency during reload, process restart, and process clear, use the adjacency
stagger command in router configuration mode. To turn off adjacency staggering, either use the disable
keyword or use the no form of this command.
initial-num-nbr The initial number of simultaneous neighbors allowed to form adjacency to FULL in any
area to bring up to FULL after a router reload, IS-IS process restart, or IS-IS process clear.
Range is 1-65535. Default is 2.
max-num-nbr The subsequent number of simultaneous neighbors allowed to form adjacency, per IS-IS
instance, after the initial set of IS-IS neighbors have become FULL. Range is 1-65535.
Default is 64.
Release Modification
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Staggering of the IS-IS adjacency during reload, process restart (without NSR or graceful-restart), and process
clear reduces the overall adjacency convergence time.
Initially, allow 2 (configurable) neighbors to form adjacency to FULL per area. After the first adjacency
reaches FULL, up to 64 (configurable) neighbors can form adjacency simultaneously for the IS-IS instance
(all areas). However, areas without any FULL adjacency is restricted by the initial area limit.
Note Adjacency stagger and IS-IS nonstop forwarding (NSF) are mutually exclusive. Adjacency stagger is not
activated if nonstop forwarding (NSF) is configured in the router along with IS-IS configuration.
Task ID Operations
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
660
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
adjacency stagger
The following example shows how to configure adjacency stagger for a 2 neighbors initially and for
a maximum of 32 neighbors:
Router# configure
Router(config)# router isis 1
Router(config-isis)# adjacency stagger 2 32
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
661
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
attached-bit receive ignore
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to configure to ignore the attached bit in a received LSP:
attached-bit send, on page 663 Configures an Intermediate System-to-Intermediate System (IS-IS) instance
with an attached bit in the Level 1 link-state packet (LSP).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
662
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
attached-bit send
attached-bit send
To configure an Intermediate System-to-Intermediate System (IS-IS) instance with an attached bit in the Level
1 link-state packet (LSP), use the attached-bit send command in address family configuration mode. To
remove the attached-bit send command from the configuration file and restore the system to its default
condition, use the no form of this command.
Syntax Description always-set Specifies to always set the attached bit in the LSP.
Command Default The attached bit is not forced to be set or unset in the LSP.
Release 3.8.0 This command was introduced and replaces the set-attached-bit, on page 782 command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the attached-bit send command to set an IS-IS instance with an attached bit in the Level 1 LSP that
allows another IS-IS instance to redistribute Level 2 topology. The attached bit is used when the Level 2
connectivity from another IS-IS instance is advertised by the Level 1 attached bit.
Cisco IOS XR software does not support multiple Level 1 areas in a single IS-IS routing instance; however
the equivalent functionality is achieved by redistribution of routes between two IS-IS instances by using the
redistribute (IS-IS), on page 770 command.
The attached bit is configured for a specific address family only if the single-topology command is not
configured.
Note If connectivity for the Level 2 instance is lost, the attached bit in the Level 1 instance LSP continues sending
traffic to the Level 2 instance and causes the traffic to be dropped.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
663
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
attached-bit send
Examples The following example shows how to configure an Intermediate System-to-Intermediate System
(IS-IS) instance with an attached bit:
redistribute (IS-IS), on page 770 Redistribute routes from one routing protocol into Intermediate
System-to-Intermediate System (IS-IS).
single-topology, on page 847 Configures the link topology for IPv4 when IPv6 is configured.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
664
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
circuit-type
circuit-type
To configure the type of adjacency used for the Intermediate System-to-Intermediate System (IS-IS) protocol,
use the circuit-type command in interface configuration mode. To reset the circuit type to Level l and Level
2, use the no form of this command.
Command Default Default adjacency types are Level 1 and Level 2 adjacencies.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Adjacencies may not be established even if allowed by the circuit-type command. The proper way to establish
adjacencies is to configure a router as a Level 1, Level 1 and Level 2, or Level 2-only system using the is-type,
on page 710 command. Only on networking devices that are between areas (Level 1 and Level 2 networking
devices) should you configure some interfaces to be Level 2-only to prevent wasting bandwidth by sending
out unused Level 1 hello packets. Remember that on point-to-point interfaces, the Level 1 and Level 2 hello
packets are in the same packet.
isis read,
write
Examples The following example shows how to configure a Level 1 adjacency with its neighbor on
GigabitEthernetinterface 0/2/0/0 and Level 2 adjacencies with all Level 2-capable routers on
GigabitEthernet interface 0/5/0/2:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
665
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
circuit-type
RP/0/RSP0/CPU0:router(config-isis-if)# exit
RP/0/RSP0/CPU0:router(config-isis)# interface GigabitEthernet 0/5/0/2
RP/0/RSP0/CPU0:router(config-isis-if)# circuit-type level-2-only
In this example, only Level 2 adjacencies are established because the is-type command is configured:
is-type, on page 710 Configures the routing level for an instance of the IS-IS routing process.
net, on page 755 Configures an IS-IS NET for the routing process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
666
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
clear isis process
Syntax Description instance instance-id (Optional) Specifies IS-IS sessions for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear isis process command without any keyword to clear all the IS-IS instances. Add the instance
instance-id keyword and argument to clear the specified IS-IS instance.
isis read,
write
Examples The following example shows the IS-IS LSP database and adjacency sessions being cleared for
instance 1:
RP/0/RSP0/CPU0:router# clear isis instance 1 process
show isis database, on page 796 Displays the IS-IS link-state database.
show isis neighbors, on page 819 Displays information about IS-IS neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
667
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
clear isis route
clear isis [instance instance-id] {afi-all | ipv4 | ipv6} {unicast | multicast | safi-all} [topology
topo-name] route
Syntax Description instance instance-id (Optional) Specifies IS-IS sessions for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
topology topo-name (Optional) Specifies topology table information and name of the topology table.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear isis route command to clear the routes from the specified topology or all routes in all topologies
if no topology is specified.
isis execute
rib read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
668
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
clear isis route
Task ID Operations
basic-services read,
write
Examples The following example shows how to clear the routes with IPv4 unicast address prefixes:
RP/0/RSP0/CPU0:router# clear isis ipv4 unicast route
show isis database, on page 796 Displays the IS-IS link-state database.
show isis neighbors, on page 819 Displays information about IS-IS neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
669
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
clear isis statistics
Syntax Description instance instance-id (Optional) Clears IS-IS sessions for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined by
the router isis command.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?)
online help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear isis statistics command to clear the information displayed by the show isis statistics command.
isis execute
rib read,
write
basic-services read,
write
Examples The following example shows the IS-IS statistics for a specified interface being cleared:
RP/0/RSP0/CPU0:router# clear isis instance 23 statistics
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
670
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
clear isis statistics
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
671
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
csnp-interval
csnp-interval
To configure the interval at which periodic complete sequence number PDU (CSNP) packets are sent on
broadcast interfaces, use the csnp-interval command in interface configuration mode. To restore the default
value, use the no form of this command.
Syntax Description seconds Interval (in seconds) of time between transmission of CSNPs on multiaccess networks.
This interval applies only for the designated router. Range is 0 to 65535 seconds.
level { 1 | 2 } (Optional) Specifies the interval of time between transmission of CSNPs for Level 1 or
Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The csnp-interval command applies only to the designated router (DR) for a specified interface. Only DRs
send CSNP packets to maintain database synchronization. The CSNP interval can be configured independently
for Level 1 and Level 2.
Use of the csnp-interval command on point-to-point subinterfaces makes sense only in combination with
the IS-IS mesh-group feature.
isis execute
rib read,
write
basic-services read,
write
Examples The following example shows how to set the CSNP interval for Level 1 to 30 seconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
672
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
csnp-interval
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
673
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
default-information originate (IS-IS)
Command Default A default route is not generated into an IS-IS routing domain.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If a router configured with the default-information originate command has a route to 0.0.0.0 in the routing
table, IS-IS originates an advertisement for 0.0.0.0 in its link-state packets (LSPs).
Without a route policy, the default is advertised only in Level 2 LSPs. For Level 1 routing, there is another
process to find the default route, which is to look for the closest Level 1 and Level 2 router. The closest Level
1 and Level 2 router can be found by looking at the attached-bit (ATT) in Level 1 LSPs.
A route policy can be used for two purposes:
• To make the router generate the default route in its Level 1 LSPs.
• To advertise 0.0.0.0/0 conditionally.
isis read,
write
Examples The following example shows how to generate a default external route into an IS-IS domain:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
674
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
default-information originate (IS-IS)
redistribute (IS-IS), on page 770 Redistributes routes from one routing protocol into Intermediate
System-to-Intermediate System (IS-IS).
show isis database, on page 796 Displays the IS-IS link-state database.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
675
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
disable (IS-IS)
disable (IS-IS)
To disable the Intermediate System-to-Intermediate System (IS-IS) topology on a specified interface, use the
disable command in interface address family configuration mode. To remove this function, use the no form
of this command.
disable
no disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to disable the IS-IS protocol for IPv4 unicast on GigabitEthernet
interface 0/1/0/1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
676
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
distance (IS-IS)
distance (IS-IS)
To define the administrative distance assigned to routes discovered by the Intermediate System-to-Intermediate
System (IS-IS) protocol, use the distance command in address family configuration mode. To remove the
distance command from the configuration file and restore the system to its default condition in which the
software removes a distance definition, use the no form of this command.
Syntax Description weight Administrative distance to be assigned to IS-IS routes. Range is 1 to 255.
prefix (Optional) The prefix argument specifies the IP address in four-part, dotted-decimal
notation.
/length (Optional) The length of the IP prefix. A decimal value that indicates how many of the
high-order contiguous bits of the address compose the prefix (the network portion of the
address). A slash must precede the decimal value. Range is 0 to 32 for IPv4 addresses
and 0 to 128 for IPv6 addresses.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An administrative distance is an integer from 1 to 255. In general, the higher the value, the lower the trust
rating. An administrative distance of 255 means that the routing information source cannot be trusted at all
and should be ignored. Weight values are subjective; no quantitative method exists for choosing weight values.
Use the distance command to configure the administrative distances applied to IS-IS routes when they are
inserted into the Routing Information Base (RIB), and influence the likelihood of these routes being preferred
over routes to the same destination addresses discovered by other protocols.
The address/prefix-length argument defines to which source router the distance applies. In other words, each
IS-IS route is advertised by another router, and that router advertises an address that identifies it. This source
address is displayed in the output of the show isis route detail command.
The distance command applies to the routes advertised by routers whose address matches the specified
prefix. The prefix-list-name argument can then be used to refine this further so that the distance command
affects only specific routes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
677
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
distance (IS-IS)
isis read,
write
Examples In the following example, a distance of 10 is assigned to all routes to 2.0.0.0/8 and 3.0.0.0/8 (or more
specific prefixes) that are advertised by routers whose ID is contained in 1.0.0.0/8. A distance of 80
is assigned to all other routes.
router isis, on page 778 Configures the IS-IS routing protocol and specifies an IS-IS instance.
show isis protocol, on page 822 Displays summary information about the IS-IS instance.
show isis route, on page 824 detail Displays link-state packet (LSP) details.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
678
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-link (IS-IS)
Syntax Description exclude Specifies fast-reroute (FRR ) loop-free alternate (LFA) computation exclusion information
interface Specifies an interface that needs to be either excluded from FRR LFA computation (when
used with exclude keyword) or to be included to LFA candidate list in FRR LFA
computation (when used with the lfa-candidate keyword).
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
679
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-link (IS-IS)
This example shows how to configure per-link fast-reroute LFA computation for the IPv4 unicast
topology at Level 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
680
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-prefix (IS-IS)
Syntax Description exclude Specifies fast-reroute (FRR ) loop-free alternate (LFA) computation exclusion
information
interface Specifies an interface that needs to be either excluded from FRR LFA computation
(when used with exclude keyword) or to be included to LFA candidate list in
FRR LFA computation (when used with the lfa-candidate keyword).
type Interface type. For more information, use the question mark ( ? ) online help
function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
681
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-prefix (IS-IS)
This example shows how to configure per-prefix fast-reroute LFA computation for the IPv4 unicast
topology at Level 1:
This example shows how to configure per-prefix remote-lfa prefix list. The prefix-list option filters
PQ node router ID based on prefix list.
RP/0/RP0/CPU0:router(config-isis-af)# fast-reroute per-prefix remote-lfa prefix-list
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
682
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-link priority-limit (IS-IS)
Syntax Description critical Enables LFA omputation for critical priority prefixes
only.
Command Default Fast-reroute per link priority limit LFA computation is disabled.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure fast-reroute prefix independent per-link computation for critical
priority prefixes for level 1 only:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router isis isp_lfa
RP/0/RSP0/CPU0:router(config-isis)#address-family ipv4
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
683
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-link priority-limit (IS-IS)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
684
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-prefix load-sharing disable (IS-IS)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to disable load-sharing prefixes across multiple backups for level 1 routes:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router isis isp_lfa
RP/0/RSP0/CPU0:router(config-isis)#address-family ipv4
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix load-sharing disable level 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
685
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-prefix tiebreaker (IS-IS)
Syntax Description downstream Configures to prefer backup path via downstream node, in case of tie-breaker.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
686
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
fast-reroute per-prefix tiebreaker (IS-IS)
This example shows how to configure preference of backup path via downstream node in case of a
tie-breaker for selection of backup path from multiple backup paths:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router isis isp_lfa
RP/0/RSP0/CPU0:router(config-isis)#address-family ipv4
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix tiebreaker downstream index
255
This example shows how to configure all the criterions for backup path selection:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router isis isp_lfa
RP/0/RSP0/CPU0:router(config-isis)#address-family ipv4
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix tiebreaker srlg-disjoint index
10
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix tiebreaker primary-path index
20
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix tiebreaker lowest-backup-metric
index 30
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix tiebreaker lc-disjoint index
40
RP/0/RSP0/CPU0:router(config-isis-af)#fast-reroute per-prefix tiebreaker node-protecting
index 50
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
687
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-interval (IS-IS)
hello-interval (IS-IS)
To specify the length of time between consecutive hello packets sent by the Intermediate System-to-Intermediate
System (IS-IS) protocol software, use the hello-interval command in interface configuration mode. To
restore the default value, use the no form of this command.
Syntax Description seconds Integer value (in seconds) for the length of time between consecutive hello packets. By
default, a value three times the hello interval seconds is advertised as the hold time in the
hello packets sent. (That multiplier of three can be changed by using the hello-multiplier
command.) With smaller hello intervals, topological changes are detected more quickly,
but there is more routing traffic. Range is 1 to 65535 seconds.
level { 1 | 2 } (Optional) Specifies the hello interval for Level 1 and Level 2 independently. For broadcast
interfaces only.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The hello interval can be configured independently for Level 1 and Level 2, except on serial point-to-point
interfaces. (Because only a single type of hello packet is sent on serial links, it is independent of Level 1 or
Level 2.) Configuring Level 1 and Level 2 independently is used on LAN interfaces.
Note A shorter hello interval gives quicker convergence, but increases bandwidth and CPU usage. It might also
add to instability in the network.
A slower hello interval saves bandwidth and CPU. Especially when used in combination with a higher hello
multiplier, this strategy may increase overall network stability.
For point-to-point links, IS-IS sends only a single hello for Level 1 and Level 2, making the level keyword
meaningless on point-to-point links. To modify hello parameters for a point-to-point interface, omit the level
keyword.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
688
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-interval (IS-IS)
isis read,
write
Examples The following example shows how to configure TenGigE interface 0/6/0/0 to advertise hello packets
every 5 seconds for Level 1 topology routes. This situation causes more traffic than configuring a
longer interval, but topological changes are detected more quickly.
hello-multiplier, on page 690 Specifies the number of IS-IS hello packets a neighbor must miss before the
router should declare the adjacency as down.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
689
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-multiplier
hello-multiplier
To specify the number of Intermediate System-to-Intermediate System (IS-IS) hello packets a neighbor must
miss before the router should declare the adjacency as down, use the hello-multiplier command in interface
configuration mode. To restore the default value, use the no form of this command.
Syntax Description multiplier Advertised hold time in IS-IS hello packets is set to the hello multiplier times the hello
interval. Range is 3 to 1000. Neighbors declare an adjacency to this down router after not
having received any IS-IS hello packets during the advertised hold time. The hold time
(and thus the hello multiplier and the hello interval) can be set on an individual interface
basis, and can be different between different networking devices in one area.
Using a smaller hello multiplier gives faster convergence, but can result in more routing
instability. Increase the hello multiplier to a larger value to help network stability when
needed. Never configure a hello multiplier to a value lower than the default value of 3.
level { 1 | 2 } (Optional) Specifies the hello multiplier independently for Level 1 or Level 2 adjacencies.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The “holding time” carried in an IS-IS hello packet determines how long a neighbor waits for another hello
packet before declaring the neighbor to be down. This time determines how quickly a failed link or neighbor
is detected so that routes can be recalculated.
Use the hello-multiplier command in circumstances where hello packets are lost frequently and IS-IS
adjacencies are failing unnecessarily. You can raise the hello multiplier and lower the hello interval
(hello-interval (IS-IS), on page 688 command) correspondingly to make the hello protocol more reliable
without increasing the time required to detect a link failure.
On point-to-point links, there is only one hello for both Level 1 and Level 2. Separate Level 1 and Level 2
hello packets are also sent over nonbroadcast multiaccess (NBMA) networks in multipoint mode, such as
X.25, Frame Relay, and ATM.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
690
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-multiplier
isis read,
write
Examples The following example shows how the network administrator wants to increase network stability by
making sure an adjacency goes down only when many (ten) hello packets are missed. The total time
to detect link failure is 60 seconds. This strategy ensures that the network remains stable, even when
the link is fully congested.
hello-interval (IS-IS), on page 688 Specifies the length of time between hello packets that the software sends.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
691
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-padding
hello-padding
To configure padding on Intermediate System-to-Intermediate System (IS-IS) hello protocol data units (IIH
PDUs) for all IS-IS interfaces on the router, use the hello-padding command in interface configuration
mode. To suppress padding, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You might want to suppress hello padding to conserve network resources. The lower the circuit speed, the
higher the percentage of padding overhead. Before suppressing the hello padding, you should know your
physical and data link layer configurations and have control over them, and also know your router configuration
at the network layer.
For point-to-point links, IS-IS sends only a single hello for Level 1 and Level 2, making the level keyword
meaningless on point-to-point links. To modify hello parameters for a point-to-point interface, omit the level
keyword.
isis read,
write
Examples The following example shows how to suppress IS-IS hello padding over local area network (LAN)
circuits for interface GigabitEthernet 0/2/0/1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
692
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-padding
show isis interface, on page 804 Displays information about the IS-IS interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
693
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-password
hello-password
To configure the authentication password for an Intermediate System-to-Intermediate System (IS-IS) interface,
use the hello-password command in interface configuration mode. To disable authentication, use the no
form of this command.
Syntax Description hmac-md5 (Optional) Specifies that the password use HMAC-MD5 authentication.
text (Optional) Specifies that the password use clear text password authentication.
encrypted (Optional) Specifies that the password be encrypted using a two-way algorithm.
level { 1 | 2 } (Optional) Specifies whether the password is for a Level 1 or a Level 2 protocol data unit
(PDU).
send-only (Optional) Specifies that the password applies only to protocol data units (PDUs) that are
being sent and does not apply to PDUs that are being received.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
password: encrypted text
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When a text password is configured, it is exchanged as clear text. Therefore, the hello-password command
provides limited security.
When an hmac-md5 password is configured, the password is never sent over the network and is instead
used to calculate a cryptographic checksum to ensure the integrity of the exchanged data.
For point-to-point links, IS-IS sends only a single hello for Level 1 and Level 2, making the level keyword
meaningless on point-to-point links. To modify hello parameters for a point-to-point interface, omit the level
keyword.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
694
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-password
isis read,
write
Examples The following example shows how to configure a password with HMAC-MD5 authentication for
hello packets running on GigabitEthernet 0/2/0/3 interface:
hello-password keychain, on page 696 Configures the authentication password keychain for an Intermediate
System-to-Intermediate System (IS-IS) interface.
hello-password accept, on page 698 Configures an additional authentication password for an IS-IS
interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
695
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-password keychain
hello-password keychain
To configure the authentication password keychain for an Intermediate System-to-Intermediate System (IS-IS)
interface, use the hello-password keychain command in interface configuration mode. To disable the
authentication password keychain, use the no form of this command.
Syntax Description keychain Keyword that specifies the keychain to be configured. An authentication password keychain
is a sequence of keys that are collectively managed and used for authenticating a
peer-to-peer group.
level { 1 | 2 } (Optional) Specifies whether the keychain is for a Level 1 or a Level 2 protocol data unit
(PDU).
send-only (Optional) Specifies that the keychain applies only to protocol data units (PDUs) that are
being sent and does not apply to PDUs that are being received.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
password: encrypted text
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Specify a keychain to enable keychain authentication between two IS-IS peers. Use the keychain
keychain-name keyword and argument to implement hitless key rollover for authentication.
isis read,
write
Examples The following example shows how to configure a password keychain for level 1, send only
authentication on a GigabitEthernet interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
696
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-password keychain
hello-password accept, on page 698 Configures an additional authentication password for an IS-IS interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
697
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-password accept
hello-password accept
To configure an additional authentication password for an Intermediate System-to-Intermediate System (IS-IS)
interface, use the hello-password accept command in interface configuration mode. To disable authentication,
use the no form of this command.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the hello-password accept command to add an additional password for an IS-IS interface. An
authentication password must be configured using the hello-password command before an accept password
can be configured for the corresponding level.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
698
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hello-password accept
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
699
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
hostname dynamic disable
Usage Guidelines In an IS-IS routing domain, each router is represented by a 6-byte hexadecimal system ID. When network
administrators maintain and troubleshoot networking devices, they must know the router name and
corresponding system ID.
Link-state packets (LSPs) include the dynamic hostname in the type, length, and value (TLV) which carries
the mapping information across the entire domain. Every router in the network, upon receiving the TLV from
an LSP, tries to install it in a mapping table. The router then uses the mapping table when it wants to convert
a system ID to a router name.
To display the entries in the mapping tables, use the show isis hostname command.
isis read,
write
Examples The following example shows how to disable dynamic mapping of hostnames to system IDs:
show isis hostname, on page 802 Displays the router name-to-system ID mapping table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
700
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
ignore-lsp-errors
ignore-lsp-errors
To override the default setting of a router to ignore Intermediate System-to-Intermediate System (IS-IS)
link-state packets (LSPs) that are received with internal checksum errors, use the ignore-lsp-errors disable
command in router configuration mode. To enable ignoring IS-IS LSP errors, use the no form of this command.
ignore-lsp-errors disable
no ignore-lsp-errors disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The IS-IS protocol definition requires that a received LSP with an incorrect data-link checksum be purged by
the receiver, which causes the initiator of the packet to regenerate it. However, if a network has a link that
causes data corruption and at the same time is delivering LSPs with correct data-link checksums, a continuous
cycle of purging and regenerating large numbers of packets can occur. Because this situation could render the
network nonfunctional, use this command to ignore these LSPs rather than purge the packets.
The receiving network devices use link-state packets to maintain their routing tables.
isis read,
write
Examples The following example shows how to instruct the router to purge LSPs that cause the initiator to
regenerate LSPs:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
701
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
instance-id
instance-id
To allow a router to share one or more circuits among multiple Intermediate System to Intermediate System
(IS-IS) routing protocol instances, use the instance-id command in router configuration mode.
instance-id identifier
Syntax Description identifier Specifies the Intermediate System to Intermediate System (IS-IS) routing protocol instance.
Range is 1-65535.
isis read,
write
Examples The following example shows how to configure multiple instances on a single router:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
702
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
interface (IS-IS)
interface (IS-IS)
To configure the Intermediate System-to-Intermediate System (IS-IS) protocol on an interface, use the
interface command in router configuration mode. To disable IS-IS routing for interfaces, use the no form
of this command.
Syntax Description type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An address family must be established on the IS-IS interface before the interface is enabled for IS-IS protocol
operation.
isis read,
write
Examples The following example shows how to enable an IS-IS multitopology configuration for IPv4 on
GigabitEthernet interface 0/3/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
703
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
interface (IS-IS)
log adjacency changes (IS-IS), on page 713 Configures the routing level for an instance of the IS-IS routing
process.
net, on page 755 Configures an IS-IS network entity title (NET) for the routing
process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
704
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
ipfrr lfa
ipfrr lfa
The ipfrr lfa commands are deprecated in Release 4.0.1, and replaced with the fast-reroute commands. For
more information, see the following:
• fast-reroute per-link priority-limit [level <1-2>]
• fast-reroute per-prefix priority-limit [level <1-2>]
• fast-reroute per-prefix tiebreaker index <1-255> [level <1-2>]
To enable the IP fast reroute (IPFRR) loop-free alternate (LFA) computation, use the ipfrr lfa command in
interface address family configuration mode. To disable this feature, use the no form of this command.
Syntax Description level { 1 | 2 } Configures IPFRR LFA for Level 1 or Level 2 independently.
Release 4.0.1 This command was deprecated and replaced with the fast-reroute commands.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
705
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
ipfrr lfa
Use the ipfrr lfa command to compute loop-free alternates for all links or neighbors in the event of a link
failure.
To enable node protection on broadcast links, IPRR and bidirectional forwarding detection (BFD) must be
enabled on the interface under IS-IS. See Cisco IOS XR Interface and Hardware Configuration Guide for
information on configuring BFD.
Note Multiprotocol Label Switching (MPLS) FRR and IPFRR cannot be configured on the same interface
simultaneously.
isis read,
write
Examples The following example shows how to configure IPFRR for the IPv4 unicast topology at Level 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
706
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
ipfrr lfa exclude interface
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the ipfrr lfa command to compute loop-free alternates for all links or neighbors in the event of a link
failure.
To enable node protection on broadcast links, IPRR and bidirectional forwarding detection (BFD) must be
enabled on the interface under IS-IS. See Cisco IOS XR Interface and Hardware Configuration Guide for
information on configuring BFD.
Note Multiprotocol Label Switching (MPLS) FRR and IPFRR cannot be configured on the same interface
simultaneously.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
707
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
ipfrr lfa exclude interface
Examples The following example shows how to configure to exclude 0/1/0/0 interface from IPFRR LFA:
ipfrr lfa, on page 705 Enable the IP fast reroute (IPFRR) loop-free alternate (LFA) computation
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
708
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
ispf
ispf
To configure the incremental shortest path first (iSPF) algorithm to calculate network topology, use the ispf
command in address family configuration mode. To disable this algorithm function, use the no form of this
command.
Syntax Description level { 1 | 2 } (Optional) Configures the iSPF algorithm for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The iSPF algorithm may be used to reduce the processor load when IS-IS needs to recalculate its topology
after minor changes.
isis read,
write
Examples The following example shows how to configure iSPF for the IPv4 unicast topology at Level 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
709
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
is-type
is-type
To configure the routing level for an Intermediate System-to-Intermediate System (IS-IS) area, use the is-type
command in router configuration mode. To set the routing level to the default level, use the no form of this
command.
Syntax Description level-1 Specifies that the router perform only Level 1 (intra-area) routing. This router learns only
about destinations inside its area. Level 2 (interarea) routing is performed by the closest Level
1-2 router.
level-1-2 Specifies that the router perform both Level 1 and Level 2 routing.
level-2-only Specifies that the routing process acts as a Level 2 (interarea) router only. This router is part
of the backbone, and does not communicate with Level 1-only routers in its own area.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the router is configured with Level 1 routing only, this router learns about destinations only inside its
area. Level 2 (interarea) routing is performed by the closest Level 1-2 router.
When the router is configured with Level 2 routing only, this router is part of the backbone, and does not
communicate with Level 1 routers in its own area.
The router has one link-state packet database (LSDB) for destinations inside the area (Level 1 routing) and
runs a shortest path first (SPF) calculation to discover the area topology. It also has another LSDB with
link-state packets (LSPs) of all other backbone (Level 2) routers, and runs another SPF calculation to discover
the topology of the backbone and the existence of all other areas.
We highly recommend that you configure the type of an IS-IS routing process to establish the proper level of
adjacencies. If there is only one area in the network, there is no need to run both Level 1 and Level 2 routing
algorithms.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
710
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
is-type
Examples The following example shows how to specify that the router is part of the backbone and that it does
not communicate with Level 1-only routers:
show isis neighbors, on page 819 Displays information about IS-IS neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
711
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
link-group
link-group
To configure an interface as a member of a link group, use the link-group command in the IS-IS interface
or address-family configuration mode. To remove an interface from a link-group, use the no form of this
command.
link-group link-group-name
no link-group link-group-name
Address-family configuration
Usage Guidelines One IS-IS interface and address-family can specify only one link-group association. The default is for both
levels regardless of current circuit-type. The link-group association can be specified for one level only if
configured.
isis read,
write
Examples The following example shows how to configure GigabitEthernet interface 0/3/0/0 as a member of a
link group:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
712
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
log adjacency changes (IS-IS)
Usage Guidelines Use the log adjacency changes command to monitor IS-IS adjacency state changes; it may be very useful
when you are monitoring large networks. Messages are logged using the system error message facility.
Messages can be in either of two forms:
Using the no form of the command removes the specified command from the configuration file and restores
the system to its default condition with respect to the command.
isis read,
write
Examples The following example shows how to configure the router to log adjacency changes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
713
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
log pdu drops
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the log pdu drops command to monitor a network when IS-IS PDUs are suspected of being dropped.
The reason for the PDU being dropped and current PDU drop statistics are recorded.
The following are examples of PDU logging output:
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
714
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp fast-flood threshold
Syntax Description lsp-number Number of LSPs to send back to back. Range is 1 to 4294967295.
level { 1 | 2 } (Optional) Specifies the LSP threshold for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the lsp fast-flood threshold command to accelerate convergence of LSP database. LSPs are sent
back-to-back over an interface up to the specified limit. Past the limit, LSPs are sent out in the next batch
window as determined by LSP pacing interval.
Duration of back-to-back window = LSP interval * LSP fast-flood threshold limit.
isis read,
write
Examples The following example shows how to configure the LSP threshold:
lsp-interval, on page 718 Configures the amount of time between consecutive LSPs sent on an IS-IS interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
715
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-gen-interval
lsp-gen-interval
To customize IS-IS throttling of link-state packet (LSP) generation, use the lsp-gen-interval command in
router configuration mode. To restore the default value, use the no form of this command.
Syntax Description initial-wait initial Specifies the initial LSP generation delay (in milliseconds). Range is 0 to
120000 milliseconds.
secondary-wait secondary Specifies the hold time between the first and second LSP generation (in
milliseconds). Range is 1 to 120000 milliseconds.
maximum-wait maximum Specifies the maximum interval (in milliseconds) between two consecutive
occurrences of an LSP being generated. Range is 1 to 120000 milliseconds.
level { 1 | 2 } (Optional) Specifies the LSP time interval for Level 1 or Level 2
independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
During prolonged periods of network instability, repeated recalculation of LSPs can cause increased CPU
load on the local router. Further, the flooding of these recalculated LSPs to the other Intermediate Systems in
the network causes increased traffic and can result in other routers having to spend more time running route
calculations.
Use the lsp-gen-interval command to reduce the rate of LSP generation during periods of instability in the
network. This command can help to reduce CPU load on the router and to reduce the number of LSP
transmissions to its IS-IS neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
716
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-gen-interval
isis read,
write
Examples The following example shows how to set the maximum interval between two consecutive occurrences
of an LSP to 15 milliseconds and the initial LSP generation delta to 5 milliseconds:
retransmit-interval (IS-IS), on page 774 Configures the amount of time between retransmission of each IS-IS
LSP on a point-to-point link.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
717
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-interval
lsp-interval
To configure the amount of time between consecutive link-state packets (LSPs) sent on an Intermediate
System-to-Intermediate System (IS-IS) interface, use the lsp-interval command in interface configuration
mode. To restore the default value, use the no form of this command.
Syntax Description milliseconds Time delay (in milliseconds) between successive LSPs. Range is 1 to 4294967295.
level { 1 | 2 } (Optional) Configures the LSP time delay for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to cause the system to send LSPs every 100 milliseconds (10
packets per second) on Level 1 and Level 2:
retransmit-interval (IS-IS), on page 774 Configures the amount of time between retransmission of each IS-IS
LSP on a point-to-point link.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
718
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-mtu
lsp-mtu
To set the maximum transmission unit (MTU) size of Intermediate System-to-Intermediate System (IS-IS)
link-state packets (LSPs), use the lsp-mtu command in router configuration mode. To restore the default,
use the no form of this command.
Syntax Description bytes Maximum packet size in bytes. The number of bytes must be less than or equal to the
smallest MTU of any link in the network. Range is 128 to 4352 bytes.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Under normal conditions, the default MTU size should be sufficient. However, if the MTU size of a link is
less than 1500 bytes, the LSP MTU size must be lowered accordingly on each router in the network. If this
action is not taken, routing becomes unpredictable.
This guideline applies to all Cisco networking devices in a network. If any link in the network has a reduced
MTU size, all devices must be changed, not just the devices directly connected to the link.
Note Do not set the lsp-mtu command (network layer) to a value greater than the link MTU size that is set with
the mtu command (physical layer).
To be certain about a link MTU size, use the show isis interface, on page 804 command to display the value.
isis read,
write
Examples The following example shows how to set the MTU size to 1300 bytes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
719
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-mtu
show isis interface, on page 804 Displays information about the IS-IS interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
720
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-password
lsp-password
To configure the link-state packet (LSP) authentication password, use the lsp-password command in router
configuration mode. To remove the lsp-password command from the configuration file and disable link-state
packet authentication, use the no form of this command.
Syntax Description hmac-md5 Specifies that the password uses HMAC-MD5 authentication.
text Specifies that the password uses clear text password authentication.
send-only (Optional) Adds passwords to LSP and sequence number protocol (SNP) data units when
they are sent. Does not check for authentication in received LSPs or sequence number
PDUs (SNPs).
snp send-only (Optional) Adds passwords to SNP data units when they are sent. Does not check for
authentication in received SNPs. This option is available when the text keyword is
specified.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines When a text password is configured, it is exchanged as clear text. Therefore, the lsp-password command
provides limited security.
When an HMAC-MD5 password is configured, the password is never sent over the network and is instead
used to calculate a cryptographic checksum to ensure the integrity of the exchanged data.
The recommended password configuration is that both incoming and outgoing SNPs be authenticated.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
721
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-password
Note To disable SNP password checking, the snp send-only keywords must be specified in the lsp-password
command.
isis read,
write
Examples The following example shows how to configure separate Level 1 and Level 2 LSP and SNP passwords,
one with HMAC-MD5 authentication and encryption and one with clear text password authentication
and no encryption:
lsp-password accept, on page 723 Configures an additional LSP password when one LSP password is already
configured for a level.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
722
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-password accept
lsp-password accept
To configure an additional link-state packet (LSP) authentication password, use the lsp-password accept
command in router configuration mode. To remove the lsp-password accept command from the configuration
file and restore the system to its default condition, use the no form of this command.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The lsp-password accept command adds an additional password for use when the system validates incoming
LSPs and sequence number PDUs (SNPs). An LSP password must be configured using the lsp-password
command before an accept password can be configured for the corresponding level.
isis read,
write
Examples The following example shows how to configure an Level 1 LSP and SNP password:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
723
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-password accept
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
724
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-refresh-interval
lsp-refresh-interval
To set the time between regeneration of link-state packets (LSPs) that contain different sequence numbers,
use the lsp-refresh-interval command in router configuration mode. To restore the default refresh interval,
use the no form of this command.
Syntax Description seconds Refresh interval (in seconds). Range is 1 to 65535 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The refresh interval determines the rate at which the software periodically sends the route topology information
that it originates. This behavior is done to keep the information from becoming too old. By default, the refresh
interval is 900 seconds (15 minutes).
LSPs must be refreshed periodically before their lifetimes expire. The refresh interval must be less than the
LSP lifetime specified with this router command. Reducing the refresh interval reduces the amount of time
that undetected link-state database corruption can persist at the cost of increased link utilization. (This event
is extremely unlikely, however, because there are other safeguards against corruption.) Increasing the interval
reduces the link utilization caused by the flooding of refreshed packets (although this utilization is very small).
isis read,
write
Examples The following example shows how to change the LSP refresh interval to 10,800 seconds (3 hours):
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
725
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
lsp-refresh-interval
max-lsp-lifetime, on page 729 Sets the maximum time that LSPs persist without being refreshed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
726
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
maximum-paths (IS-IS)
maximum-paths (IS-IS)
To configure the maximum number of parallel routes that an IP routing protocol will install in the routing
table, use the maximum-paths command in address family configuration mode. To remove the
maximum-paths command from the configuration file and restore the system default behavior, use the no
form of this command. By default up to 8 parallel ECMP paths are used by IS-IS routing protocol.
maximum-paths maximum
no maximum-paths
Syntax Description maximum Maximum number of parallel routes that IS-IS can install in a routing table. Range is 1 to 64
Command Default
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to allow a maximum of 16 paths to a destination:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
727
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
maximum-redistributed-prefixes (IS-IS)
maximum-redistributed-prefixes (IS-IS)
To specify an upper limit on the number of redistributed prefixes (subject to summarization) that the
Intermediate System-to-Intermediate System (IS-IS) protocol advertises, use the
maximum-redistributed-prefixes command in address family mode. To disable this feature, use the no
form of this command.
Syntax Description maximum Maximum number of redistributed prefixes advertised. Range is 1 to 28000.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum-redistributed-prefixes command to prevent a misconfiguration from resulting in
redistribution of excess prefixes. If IS-IS encounters more than the maximum number of prefixes, it sets a
bi-state alarm. If the number of to-be-redistributed prefixes drops back to the maximum or lower—either
through reconfiguration or a change in the redistribution source—IS-IS clears the alarm.
isis read,
write
Examples The following example shows how to specify the number of redistributed prefixes at 5000 for Level
2:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
728
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
max-lsp-lifetime
max-lsp-lifetime
To set the maximum time that link-state packets (LSPs) persist without being refreshed, use the
max-lsp-lifetime command in router configuration mode. To restore the default time, use the no form of
this command.
Syntax Description seconds Lifetime (in seconds) of the LSP. Range from 1 to 65535 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the
lsp-refresh-interval command. The maximum LSP lifetime must be greater than the LSP refresh interval.
isis read,
write
Examples The following example shows how to set the maximum time that the LSP persists to 11,000 seconds
(more than 3 hours):
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
729
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
max-link-metric
max-link-metric
max-link-metric [level 1 | 2 ]
no max-link-metric [level 1 | 2 ]
Syntax Description max-link-metric Specifies maximum metrics for NLRIs during router overload.
If specified with a level number, the maximum link metric is applied only across links
for the specified level. If specified without a level number, the maximum link metric is
applied across all levels.
Usage Guidelines When a router is configured with the IS-IS overload bit, it participates in the routing process when the overload
bit is set, but does not forward traffic (except for traffic to directly connected interfaces). By configuring the
max-metric-link statement, the overloaded router is used as a transit node of last resort.
isis read,
write
Examples The following example shows how to enable maximum metric on a router:
RP/0/0/CPU0:RouterB(config)# router isis ring
RP/0/0/CPU0:RouterB(config-isis)# max-link-metric
RP/0/0/CPU0:RouterB(config-isis)# exit
RP/0/0/CPU0:RouterB(config)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
730
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mesh-group (IS-IS)
mesh-group (IS-IS)
To optimize link-state packet (LSP) flooding in highly meshed networks, use the mesh-group command in
interface configuration mode. To remove a subinterface from a mesh group, use the no form of this command.
Syntax Description number Number identifying the mesh group of which this interface is a member. Range is 1 to 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
LSPs first received on subinterfaces that are not part of a mesh group are flooded to all other subinterfaces in
the usual way.
LSPs first received on subinterfaces that are part of a mesh group are flooded to all interfaces except those in
the same mesh group. If the blocked keyword is configured on a subinterface, then a newly received LSP is
not flooded out over that interface.
To minimize the possibility of incomplete flooding, you should allow unrestricted flooding over at least a
minimal set of links in the mesh. Selecting the smallest set of logical links that covers all physical paths results
in very low flooding, but less robustness. Ideally you should select only enough links to ensure that LSP
flooding is not detrimental to scaling performance, but enough links to ensure that under most failure scenarios,
no router is logically disconnected from the rest of the network. In other words, blocking flooding on all links
permits the best scaling performance, but there is no flooding. Permitting flooding on all links results in very
poor scaling performance.
Note See RFC 2973 for details about the mesh group specification.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
731
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mesh-group (IS-IS)
Examples In the following example, six interfaces are configured in three mesh groups. LSPs received are
handled as follows:
• LSPs first received by GigabitEthernet interface 0/1/0/0 are flooded to all interfaces except
GigabitEthernet 0/1/0/1 (which is part of the same mesh group) and GigabitEthernet 0/3/0/0
(which is blocked).
• LSPs first received by GigabitEthernet 0/2/0/1 are flooded to all interfaces except GigabitEthernet
0/2/0/0 (which is part of the same mesh group) and GigabitEthernet 0/3/0/0 (which is blocked).
• LSPs first received by GigabitEthernet 0/3/0/0 are not ignored, but flooded as usual to all
interfaces.
• LSPs received first through GigabitEthernet 0/3/0/1 are flooded to all interfaces, except
GigabitEthernet 0/3/0/0 (which is blocked).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
732
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric (IS-IS)
metric (IS-IS)
To configure the metric for an Intermediate System-to-Intermediate System (IS-IS) interface, use the metric
command in address family or interface address family configuration mode. To restore the default metric
value, use the no form of this command.
Syntax Description default-metric Metric assigned to the link and used to calculate the cost from each other router using the
links in the network to other destinations. Range is 1 to 63 for narrow metric and 1
to 16777214 for wide metric.
Note Setting the default metric under address family results in setting the same metric
for all interfaces that is associated with the address family. Setting a metric value
under an interface overrides the default metric
maximum Specifies maximum wide metric. All routers exclude this link from their shortest path first
(SPF).
level { 1 | 2 } (Optional) Specifies the SPF calculation for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Specifying the level keyword resets the metric only for the specified level. We highly recommend that you
configure metrics on all interfaces.
Set the default metric under address family to set the same metric for all interfaces that is associated with the
address family. Set a metric value under an interface to override the default metric.
We highly recommend that you configure metrics on all interfaces.
Metrics of more than 63 cannot be used with narrow metric style.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
733
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric (IS-IS)
isis read,
write
Examples The following example shows how to configure Packet-over-SONET/SDH 0/1/0/1 interface with a
default link-state metric cost of 15 for Level 1:
The following example shows how to configure a metric cost of 15 for all interfaces under address
family IPv4 unicast for level 2:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router isis isp
RP/0/RSP0/CPU0:router(config-isis)# address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-isis-af)# metric 15 level 2
metric-style narrow, on page 735 Configures a router running IS-IS so that it generates and accepts
old-style TLV objects.
metric-style transition, on page 737 Configures the software to generate and accept both old-style and
new-style TLV objects.
metric-style wide, on page 739 Configures the software to generate and accept only new-style TLV
objects objects.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
734
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric-style narrow
metric-style narrow
To configure the Intermediate System-to-Intermediate System (IS-IS) software to generate and accept old-style
type, length, and value (TLV) objects, use the metric-style narrow command in address family configuration
mode. To remove the metric-style narrow command from the configuration file and restore the system to
its default condition, use the no form of this command.
Syntax Description transition (Optional) Instructs the router to generate and accept both old-style and new-style TLV
objects. It generates only old-style TLV objects.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
IS-IS traffic engineering extensions include new-style TLV objects with wider metric fields than old-style
TLV objects. By default, the router generates old-style TLV objects only. To perform Multiprotocol Label
Switching traffic engineering (MPLS TE), a router must generate new-style TLV objects.
isis read,
write
Examples The following example shows how to configure the router to generate and accept only old-style TLV
objects on router Level 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
735
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric-style narrow
metric-style transition, on page 737 Configures a router to generate and accept both old-style and new-style
TLV objects.
metric-style wide, on page 739 Configures a router to generate and accept only new-style TLV objects.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
736
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric-style transition
metric-style transition
To configure the Intermediate System-to-Intermediate System (IS-IS) software to generate and accept both
old-style and new-style type, length, and value (TLV) objects, use the metric-style transition command in
address family configuration mode. To remove the metric-style transition command from the configuration
file and restore the system to its default condition, use the no form of this command.
Syntax Description transition Instructs the router to generate and accept both old-style and new-style TLV objects.
Command Default Old-style TLVs are generated, if this command is not configured.
Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
IS-IS traffic engineering extensions include new-style TLV objects which have wider metric fields than
old-style TLV objects. By default, the router generates old-style TLV objects only. To perform Multiprotocol
Label Switching traffic engineering (MPLS TE), a router needs to generate new-style TLV objects.
isis read,
write
Examples The following example shows how to configure the router to generate and accept both old-style and
new-style TLV objects on Level 2:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
737
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric-style transition
metric-style narrow, on page 735 Configures a router to generate and accept only old-style TLV objects.
metric-style wide, on page 739 Configures a router to generate and accept only new-style TLV objects.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
738
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric-style wide
metric-style wide
To configure the Intermediate System-to-Intermediate System (IS-IS) software to generate and accept only
new-style type, length, and value (TLV) objects, use the metric-style wide command in address family
configuration mode. To remove the metric-style wide command from the configuration file and restore the
system to its default condition, use the no form of this command.
Syntax Description transition (Optional) Instructs the router to generate and accept both old-style and new-style TLV
objects. It generates only new-style TLV objects.
Command Default Old-style TLV lengths are generated, if this command is not configured.
Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
IS-IS traffic engineering extensions include new-style TLV objects with wider metric fields than old-style
TLV objects. If you enter the metric-style wide command, a router generates and accepts only new-style
TLV objects. Therefore, the router uses less memory and fewer other resources rather than generating both
old-style and new-style TLV objects.
To perform MPLS traffic engineering, a router needs to generate new-style TLV objects.
Note This discussion of metric styles and transition strategies is oriented toward traffic engineering deployment.
Other commands and models might be appropriate if the new-style TLV objects are desired for other reasons.
For example, a network may require wider metrics, but might not use traffic engineering.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
739
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
metric-style wide
Examples The following example shows how to configure a router to generate and accept only new-style TLV
objects on Level 1:
metric-style narrow, on page 735 Configures a router to generate and accept only old-style TLV objects.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
740
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
microloop avoidance
microloop avoidance
To avoid micro-loops by delaying the convergence of all or protected prefixes, use the microloop avoidance
command. Valid triggers for microloop avoidance feature are local link-down events only, such as link down,
BFD down, and IS-IS adjacency down. Microloops caused by other triggers are not avoided by this feature.
Consider microloop avoidance segment-routing command for extended trigger coverage.
To disable this function, use the no prefix for this command.
rib-update-delay delay (Optional) Delays convergence of all prefixes and updates RIB after the configured
delay. The range is 1 to 60000 milliseconds. The default is 5000ms (for both the
flavours of uloop avoidance).
Usage Guidelines When the network converges after a link failure restoration, micro-loops can form due to inconsistencies in
the forwarding tables of different routers. By delaying the convergence of prefixes, you can avoid the formation
of micro-loops.
You can delay the convergence of all or protected prefixes by using the microloop avoidance command.
When configured, the command applies to all prefixes by default. To enable it for only protected prefixes,
use the protected option.
If another event occurs when the microloop avoidance timer is running, the microloop avoidance process is
cancelled, and RIB delay timer is cancelled and prefixes are sent to RIB immediately.
isis read,
write
Examples The following example shows how to configure micro-loop avoidance with IS-IS:
Router# configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
741
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
microloop avoidance
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
742
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
min-lsp-arrivaltime
min-lsp-arrivaltime
To control the rate of incoming LSPs (link-state packets) LSPs, use the min-lsp-arrivaltime command in
router configuration mode. To remove this function use the no form of this command.
Syntax Description initial-wait initial Initial LSP calculation delay (in milliseconds). Range is 0 to 120000.
secondary-wait secondary Hold time between the first and second LSP calculations (in milliseconds).
Range is 0 to 120000.
maximum-wait maximum Maximum interval (in milliseconds) between two consecutive LSP calculations.
Range is 0 to 120000.
level { 1 | 2 } (Optional) Enables the LSP interval configuration for Level 1 or Level 2
independently.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command can be used to protect a router against the possible instability of its neighbor's LSPs.
The command parameters are similair to lsp-gen-intervalcommand and neighbors lsp-gen-interval values
can be used to set the min-lsp-arrivaltime
Note The initial-wait of minimum-lsp-arrival has no use in computing maximum counts and maximum window
sizes of the LSP arrival time parameter.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
743
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
min-lsp-arrivaltime
Examples The following example shows how to configure min-lsp-arrival time commands:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
744
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls ldp auto-config
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the mpls ldp auto-config command to automatically configure LDP on a set of interfaces associated
with a specified IGP instance. Further, LDP IGP auto-configuration provides a means to block LDP from
being enabled on a specified interface. If you do not want an IS-IS interface to have LDP enabled, use the
igp auto-config disable command.
isis read,
write
Examples The following example shows how to enable LDP IGP auto-configuration:
igp auto-config disable Disables LDP IGP auto-configuration for a specific interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
745
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls ldp sync (IS-IS)
Syntax Description level { 1 | 2 } (Optional) Sets LDP synchronization for the specified level.
Command Default If a level is not specified, LDP synchronization is set for both levels.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
MPLS VPN traffic forwarded using LDP labels can be dropped in the following instances:
• A new link is introduced in the network and IS-IS has converged before LDP establishes labels.
• An existing LDP session goes down while IS-IS adjacency is intact over the link.
In both instances, outbound LDP labels are not available for forwarding MPLS traffic. LDP IS-IS
synchronization addresses the traffic drop. When the mpls ldp sync command is configured, IS-IS advertises
the maximum possible link metric until LDP has converged over the link. The link is less preferred and least
used in forwarding MPLS traffic. When LDP establishes the session and exchanges labels, IS-IS advertises
the regular metric over the link.
Note IS-IS advertises the maximum metric –1 (16777214) if wide metrics are configured since the maximum wide
metric is specifically used for link exclusion from the shortest path first algorithm (SPF) (RFC 3784). However,
the maximum narrow metric is unaffected by this definition.
isis read,
write
Examples The following example shows how to enable LDP IS-IS synchronization:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
746
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls ldp sync (IS-IS)
show isis interface, on page 804 Displays information about the IS-IS interfaces
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
747
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng (IS-IS)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the mpls traffic-eng command, which is part of the routing protocol tree, to flood link resource
information (such as available bandwidth) for appropriately configured links in the link-state packet (LSP)
of the router.
isis read,
write
Examples The following example shows how to turn on MPLS traffic engineering for IS-IS level 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
748
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng (IS-IS)
mpls traffic-eng router-id (IS-IS), on page Specifies that the traffic engineering router identifier for the
753 node is the IP address associated with a given interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
749
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng multicast-intact (IS-IS)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If Multiprotocol Label Switching Traffic Engineering (MPLS-TE) is configured through the IS-IS routing
domain and multicast protocols (like Protocol Independent Multicast [PIM]) are also enabled, then use the
mpls traffic-end multicast-intact command to install nontraffic engineering next hops in the Routing
Information Base (RIB) for use by multicast. The installation of IP-only next hops is in addition to the
installation of the standard set of paths for a prefix, which might be through traffic engineered tunnels.
The mpls traffic-eng multicast-intact command allows PIM to use the native hop-by-hop neighbors even
though the unicast routing is using MPLS TE tunnels.
Examples The following example shows how to enable the multicast-intact feature:
show isis route, on page 824 Displays IP reachability information for an IS-IS instance, optionally for
multicast-intact.
show isis topology, on page 839 Displays a list of connected IS-IS routers in all areas, optionally for
multicast-intact.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
750
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng path-selection ignore overload
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the IS-IS overload bit avoidance feature is activated, which means that they are still available for use
label switched paths (LSPs), all nodes with the overload bit set, including the following nodes, are ignored:
• head nodes
• mid nodes
• tail nodes
mpls-te read,
write
Examples The following example shows how to activate IS-IS overload bit avoidance:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# mpls traffic-eng path-selection ignore overload
The following example shows how to deactivate IS-IS overload bit avoidance:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# no mpls traffic-eng path-selection ignore overload
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
751
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng path-selection ignore overload
set-overload-bit, on page 780 Configures a router to signal other routers not to use it as an intermediate hop
in their shortest path first (SPF) calculations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
752
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng router-id (IS-IS)
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The identifier of the router acts as a stable IP address for the traffic engineering configuration. This IP address
is flooded to all nodes. For all traffic engineering tunnels originating at other nodes and ending at this node,
you must set the tunnel destination to the traffic engineering router ID of the destination node, because that
is the address used by the traffic engineering topology database at the tunnel head for its path calculation.
Note We recommend that loopback interfaces be used for MPLS TE, because they are more stable than physical
interfaces.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
753
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
mpls traffic-eng router-id (IS-IS)
Examples The following example shows how to specify the traffic engineering router identifier as the IP address
associated with loopback interface 0:
mpls traffic-eng (IS-IS), on page 748 Turns on flooding of MPLS traffic engineering link information in the
indicated IGP level or area.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
754
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
net
net
To configure an Intermediate System-to-Intermediate System (IS-IS) network entity title (NET) for the routing
instance, use the net command in router configuration mode. To remove the net command from the
configuration file and restore the system to its default condition, use the no form of this command.
net network-entity-title
no net network-entity-title
Syntax Description network-entity-title NET that specifies the area address and the system ID for an ISIS routing process.
Command Default No NET is configured. The IS-IS instance is not operational, because a NET is mandatory.
Usage Guidelines Under most circumstances, one and only one NET should be configured.
A NET is a network service access point (NSAP) where the last byte is always 0. On a Cisco router running
IS-IS, a NET can be 8 to 20 bytes in length. The last byte is always the n-selector and must be 0. The n-selector
indicates to which transport entity the packet is sent. An n-selector of 0 indicates no transport entity and means
that the packet is for the routing software of the system.
The six bytes directly preceding the n-selector are the system ID. The system ID length is a fixed size and
cannot be changed. The system ID must be unique throughout each area (Level 1) and throughout the backbone
(Level 2).
All bytes preceding the system ID are the area ID.
A maximum of three NETs for each router is allowed. In rare circumstances, it is possible to configure two
or three NETs. In such a case, the area this router is in has three area addresses. Only one area still exists, but
it has more area addresses.
Configuring multiple NETs can be temporarily useful in network reconfiguration in which multiple areas are
merged, or in which one area is split into more areas. Multiple area addresses enable you to renumber an area
individually as needed.
isis read,
write
Examples The following example shows how to configure a router with NET area ID 47.0004.004d.0001 and
system ID 0001.0c11.1110:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
755
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
net
log adjacency changes (IS-IS), on page 713 Configures the routing level for an instance of the IS-IS routing
process.
router isis, on page 778 Enables the IS-IS routing protocol and specifies an IS-IS
instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
756
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf (IS-IS)
nsf (IS-IS)
To enable nonstop forwarding (NSF) on the next restart, use the nsf command in router configuration mode.
To restore the default setting, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
NSF allows an Intermediate System-to-Intermediate System (IS-IS) instance to restart using checkpointed
adjacency and link-state packet (LSP) information, and to perform restart with no impact on its neighbor
routers. In other words, there is no impact on other routers in the network due to the destruction and recreation
of adjacencies and the system LSP.
isis read,
write
Examples The following example shows how to enable Cisco proprietary NSF:
nsf interface-expires, on page 759 Configures the number of resends of an an acknowledged NSF-restart
acknowledgment.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
757
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf (IS-IS)
Command Description
nsf interface-timer, on page 761 Configures the time interval after which an unacknowledged IETF NSF
restart attempt is repeated.
nsf lifetime (IS-IS), on page 763 Configures the maximum route lifetime following an NSF restart.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
758
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf interface-expires
nsf interface-expires
To configure the number of resends of an acknowledged nonstop forwarding (NSF)-restart acknowledgment,
use the nsf interface-expires command in router configuration mode. To restore the default value, use the
no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When a hello packet sent with the NSF restart flag set is not acknowledged, it is re-sent. Use the
nsf interface-expires command to control the number of times the NSF hello is re-sent. When this limit is
reached on an interface, any neighbor previously known on that interface is assumed to be down and the initial
shortest path first (SPF) calculation is permitted, provided that all other necessary conditions are met.
The total time period available for adjacency reestablishment (interface-timer * interface-expires) should be
greater than the expected total NSF restart time.
The nsf interface-expires command applies only to Internet Engineering Task Force (IETF)-style NSF. It
has no effect if Cisco-proprietary NSF is configured.
isis read,
write
Examples The following example shows how to allow only one retry attempt on each interface if an IETF NSF
restart signal is not acknowledged:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
759
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf interface-expires
hello-multiplier, on page 690 Specifies the number of IS-IS hello packets a neighbor must miss before
the router should declare the adjacency as down.
nsf interface-timer, on page 761 Configures the time interval after which an unacknowledged IETF NSF
restart attempt is repeated.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
760
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf interface-timer
nsf interface-timer
To configure the time interval after which an unacknowledged Internet Engineering Task Force (IETF) nonstop
forwarding (NSF) restart attempt is repeated, use the nsf interface-timer command in router configuration
mode. To restore the default value, use the no form of this command.
Syntax Description seconds NSF restart time interval (in seconds). Range is 3 to 20 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the IETF NSF restart process begins, hello packets send an NSF restart flag that must be acknowledged
by the neighbors of the router. Use the nsf interface-timer command to control the restart time interval after
the hello packet is re-sent. The restart time interval need not match the hello interval.
The nsf interface-timer command applies only to IETF-style NSF. It has no effect if Cisco proprietary NSF
is configured.
isis read,
write
Examples The following example shows how to ensure that a hello packet with the NSF restart flag set is sent
again every 5 seconds until the flag is acknowledged:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
761
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf interface-timer
nsf interface-expires, on page 759 Configures the number of resends of an acknowledged NSF-restart
acknowledgment.
hello-interval (IS-IS), on page 688 Specifies the length of time between hello packets that the software sends.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
762
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
nsf lifetime (IS-IS)
Syntax Description seconds Maximum route lifetime (in seconds) following an NSF restart. Range is 5 to 300 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the nsf lifetime command to set the maximum available time for the reacquisition of checkpointed
adjacencies and link-state packets (LSPs) during a Cisco proprietary NSF restart. LSPs and adjacencies not
recovered during this time period are abandoned, thus causing changes to the network topology.
isis read,
write
Examples The following example shows how to configure the router to allow only 20 seconds for the entire
NSF process:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
763
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
passive (IS-IS)
passive (IS-IS)
To suppress Intermediate System-to-Intermediate System (IS-IS) packets from being transmitted to the interface
and received packets from being processed on the interface, use the passive command in interface configuration
mode. To restore IS-IS packets coming to an interface, use the no form of this command.
passive
no passive
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to configure the router to suppress IS-IS packets on GigabitEthernet
interface 0/1/0/1:
suppressed, on page 855 Allows the IS-IS interface to participate in forming adjacencies without advertising
connected prefixes in the LSPs.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
764
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
point-to-point
point-to-point
To configure a network of only two networking devices that use broadcast media and the integrated Intermediate
System-to-Intermediate System (IS-IS) routing protocol to function as a point-to-point link instead of a
broadcast link, use the point-to-point command in interface configuration mode. To disable the point-to-point
usage, use the no form of this command.
point-to-point
no point-to-point
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the point-to-point command only on broadcast media in a network with two networking devices. The
command causes the system to issue packets point-to-point rather than as broadcasts. Configure the command
on both networking devices in the network.
isis read,
write
Examples The following example shows how to configure a 10-Gb Ethernet interface to act as a point-to-point
interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
765
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
priority (IS-IS)
priority (IS-IS)
To configure the priority of designated routers, use the priority command in interface configuration mode.
To reset the default priority, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Priorities can be configured for Level 1 and Level 2 independently. Specifying Level 1 or Level 2 resets
priority only for Level 1 or Level 2 routing, respectively. Specifying no level allows you to configure all
levels.
The priority is used to determine which router on a LAN is the designated router or Designated Intermediate
System (DIS). The priorities are advertised in the hello packets. The router with the highest priority becomes
the DIS.
In the Intermediate System-to-Intermediate System (IS-IS) protocol, there is no backup designated router.
Setting the priority to 0 lowers the chance of this system becoming the DIS, but does not prevent it. If a router
with a higher priority comes online, it takes over the role from the current DIS. For equal priorities, the higher
MAC address breaks the tie.
isis read,
write
Examples The following example shows how to give Level 1 routing priority by setting the priority level to
80. This router is now more likely to become the DIS.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
766
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
priority (IS-IS)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
767
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
propagate level
propagate level
To propagate routes from one Intermediate System-to-Intermediate System (IS-IS) level into another level,
use the propagate level command in address family configuration mode. To disable propagation, use the
no form of this command.
into Propagates from Level 1 or Level 2 routes into Level 1 or Level 2 routes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In general, route propagation from Level 1 to Level 2 is automatic. You might want to use this command to
better control which Level 1 routes can be propagated into Level 2.
Propagating Level 2 routes into Level 1 is called route leaking. Route leaking is disabled by default. That is,
Level 2 routes are not automatically included in Level 1 link-state packets (LSPs). If you want to leak Level
2 routes into Level 1, you must enable that behavior by using this command.
Propagation from Level 1 into Level 1 and from Level 2 into Level 2 is not allowed.
isis read,
write
Examples The following example shows how to redistribute Level 2 routes to Level 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
768
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
propagate level
redistribute (IS-IS), on page 770 Redistributes routes from one routing domain into a specified IS-IS instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
769
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
redistribute (IS-IS)
redistribute (IS-IS)
To redistribute routes from one routing protocol into Intermediate System-to-Intermediate System (IS-IS),
use the redistribute command in address family configuration mode. To remove the redistribute command
from the configuration file and restore the system to its default condition in which the software does not
redistribute routes, use the no form of this command.
Connected Routes
redistribute connected [{level-1 | level-2 | level-1-2}] [metric metric-value] [metric-type {internal |
external}] [route-policy route-policy-name]
no redistribute
Static Routes
redistribute static [{level-1 | level-2 | level-1-2}] [metric metric-value] [metric-type {1 | 2 }]
[route-policy route-policy-name]
no redistribute
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
770
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
redistribute (IS-IS)
Syntax Description process-id For the bgp keyword, an autonomous system number has the following ranges:
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1
to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0
to 65535.65535.
For the isis keyword, an IS-IS instance identifier from which routes are to be
redistributed.
For the ospf keyword, an OSPF process name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be entered,
but it is stored internally as a string.
For the ospfv3 keyword, an OSPFv3 process name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be entered,
but it is stored internally as a string.
level-1 (Optional) Specifies that redistributed routes are advertised in the Level-1 LSP of
the router.
level-1-2 (Optional) Specifies that redistributed routes are advertised in the Level-1-2 LSP of
the router.
level-2 (Optional) Specifies that redistributed routes are advertised in the Level-2 LSP of
the router.
metric metric-value (Optional) Specifies the metric used for the redistributed route. Range is 0 to
16777215. The metric-value must be consistent with the IS-IS metric style of the
area and topology into which the routes are being redistributed.
metric-type { (Optional) Specifies the external link type associated with the route advertised into
internal | external } the ISIS routing domain. It can be one of two values:
• external
• internal –Use the internal keyword to set IS-IS internal metric-type
• external –Use the external keyword to set IS-IS external metric-type
Any route with an internal metric (however large the metric is) is preferred over a
route with external metric (however small the metric is).
route-policy (Optional) Specifies the identifier of a configured policy. A policy is used to filter
route-policy-name the importation of routes from this source routing protocol to IS-IS.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
771
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
redistribute (IS-IS)
match { internal | (Optional) Specifies the criteria by which OSPF routes are redistributed into other
external [ 1 | 2 ] | routing domains. It can be one or more of the following:
nsaa-external [ 1 | 2
• internal —Routes that are internal to a specific autonomous system (intra- and
]}
interarea OSPF routes).
• external [ 1 | 2 ]—Routes that are external to the autonomous system, but are
imported into OSPF as Type 1 or Type 2 external routes.
• nssa-external [ 1 | 2 ]—Routes that are external to the autonomous system,
but are imported into OSPF as Type 1 or Type 2 not-so-stubby area (NSSA)
external routes.
For the external and nssa-external options, if a type is not specified, then both
Type 1 and Type 2 are assumed.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note When redistributing routes (into IS-IS) using both command keywords for setting or matching of attributes
and a route policy, the routes are run through the route policy first, followed by the keyword matching and
setting.
Use the redistribute command to control the redistribution of routes between separate IS-IS instances. To
control the propagation of routes between the levels of a single IS-IS instance, use the propagate level, on
page 768 command.
Only IPv4 OSPF addresses can be redistributed into IS-IS IPv4 address families.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
772
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
redistribute (IS-IS)
Examples In this example, IS-IS instance isp_A readvertises all of the routes of IS-IS instance isp_B in Level
2 LSP. Note that the level-2 keyword affects which levels instance isp_A advertises the routes in
and has no impact on which routes from instance isp_B are advertised. (Any Level 1 routes from
IS-IS instance isp_B are included in the redistribution.
propagate level, on page 768 Propagates routes from one IS-IS level into another level.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
773
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
retransmit-interval (IS-IS)
retransmit-interval (IS-IS)
To configure the amount of time between retransmission of each Intermediate System-to-Intermediate System
(IS-IS) link-state packet (LSP) on a point-to-point link, use the retransmit-interval command in interface
configuration mode. To restore the default value, use the no form of this command.
Syntax Description seconds Time (in seconds) between consecutive retransmissions of each LSP. It is an integer that
should be greater than the expected round-trip delay between any two networking devices
on the attached network. Range is 0 to 65535 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The retransmit-interval command has no effect on LAN (multipoint) interfaces. On point-to-point links,
the value can be increased to enhance network stability.
Because retransmissions occur only when LSPs are dropped, setting this command to a higher value has little
effect on reconvergence. The more neighbors networking devices have, and the more paths over which LSPs
can be flooded, the higher this value can be made.
isis read,
write
Examples The following example shows how to configure GigabitEthernet interface 0/2/0/1 for retransmission
of IS-IS LSPs every 60 seconds for a large serial line:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
774
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
retransmit-interval (IS-IS)
retransmit-throttle-interval, on page 776 Configures the amount of time between retransmissions of any
IS-IS LSPs on a point-to-point interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
775
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
retransmit-throttle-interval
retransmit-throttle-interval
To configure minimum interval between retransmissions of different Intermediate System-to-Intermediate
System (IS-IS) link-state packets (LSPs) on a point-to-point interface, use the retransmit-throttle-interval
command in interface configuration mode. To remove the command from the configuration file and restore
the system to its default condition, use the no form of this command.
Syntax Description milliseconds Minimum delay (in milliseconds) between LSP retransmissions on the interface. Range is
0 to 65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the retransmit-throttle-interval command to define the minimum period of time that must elapse
between retransmitting any two consecutive LSPs on an interface. The retransmit-throttle-interval command
may be useful in very large networks with many LSPs and many interfaces as a way of controlling LSP
retransmission traffic. This command controls the rate at which LSPs can be re-sent on the interface.
isis read,
write
Examples The following example shows how to configure GigabitEthernet interface 0/2/0/1 to limit the rate
of LSP retransmissions to one every 300 milliseconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
776
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
retransmit-throttle-interval
lsp-gen-interval, on page 716 Configures the minimum interval time between regenerating the
same LSP.
retransmit-interval (IS-IS), on page 774 Configures the amount of time between retransmission of each IS-IS
LSP over a point-to-point link.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
777
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
router isis
router isis
To enable the Intermediate System-to-Intermediate System (IS-IS) routing protocol and to specify an IS-IS
instance, use the router isis command in global configuration mode. To disable IS-IS routing, use the no
form of this command.
Syntax Description instance-id Name of the routing process. Maximum number of characters is 40.
Usage Guidelines Use the router isis command to create an IS-IS routing process. An appropriate network entity title (NET)
must be configured to specify the address of the area (Level 1) and system ID of the router. Routing must be
enabled on one or more interfaces before adjacencies may be established and dynamic routing is possible.
Multiple IS-IS processes can be configured. Up to eight processes are configurable. A maximum of five IS-IS
instances on a system are supported.
isis read,
write
Examples The following example shows how to configure IS-IS for IP routing:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
778
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
route source first-hop
routesourcefirst-hop
This command has no keywords or arguments.
Usage Guidelines This command replaces the originating router address with first-hop router address in the RIB table and
facilitates computing alternate paths for multicast traffic. This feature is incompatible with other IOS-XR
features, such as MPLS-TE inter-area tunnels. You must use the route source first-hop command only to
support MoFRR with multicast multipath.
isis read,
write
Examples The following example shows how to replace the originating route with first-hop:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
779
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
set-overload-bit
set-overload-bit
To configure the router to signal other routers not to use it as an intermediate hop in their shortest path first
(SPF) calculations, use the set-overload-bit command in router configuration mode. To remove the
designation, use the no form of this command.
Syntax Description on-startup (Optional) Sets the overload bit only temporarily after reboot.
delay (Optional) Time (in seconds) to advertise when the router is overloaded after reboot. Range
is 5 to 86400 seconds (86400 seconds = 1 day).
wait-for-bgp (Optional) Sets the overload bit on startup until the Border Gateway Protocol (BGP) signals
converge or time out.
level { 1 | 2 } (Optional) Specifies the overload bit for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set-overload-bit command to force the router to set the overload bit in its nonpseudonode link-state
packets (LSPs). Normally the setting of the overload bit is allowed only when a router experiences problems.
For example, when a router is experiencing a memory shortage, the reason might be that the link-state database
is not complete, resulting in an incomplete or inaccurate routing table. If the overload bit is set in the LSPs
of the unreliable router, other routers can ignore the router in their SPF calculations until it has recovered
from its problems. The result is that no paths through the unreliable router are seen by other routers in the
Intermediate System-to-Intermediate System (IS-IS) area. However, IP prefixes directly connected to this
router are still reachable.
The set-overload-bit command can be useful when you want to connect a router to an IS-IS network, but
do not want real traffic flowing through it under any circumstances.
Routers with overload bit set are:
• A test router in the lab, connected to a production network.
• A router configured as an LSP flooding server, for example, on a nonbroadcast multiaccess (NBMA)
network, in combination with the mesh group feature.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
780
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
set-overload-bit
isis read,
write
Examples The following example shows how to configure the overload bit:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
781
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
set-attached-bit
set-attached-bit
To configure an Intermediate System-to-Intermediate System (IS-IS) instance with an attached bit in the Level
1 link-state packet (LSP), use the set-attached-bit command in address family configuration mode. To
remove the set-attached-bit command from the configuration file and restore the system to its default
condition, use the no form of this command.
set-attached-bit
no set-attached-bit
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set-attached bit command to set an IS-IS instance with an attached bit in the Level 1 LSP that allows
another IS-IS instance to redistribute Level 2 topology. The attached bit is used when the Level 2 connectivity
from another IS-IS instance is advertised by the Level 1 attached bit.
Cisco IOS XR software does not support multiple Level 1 areas in a single IS-IS routing instance. But the
equivalent functionality is achieved by redistribution of routes between two IS-IS instances by using the
redistribute (IS-IS), on page 770 command.
The attached bit is configured for a specific address family only if the single-topology command is not
configured.
Note If connectivity for the Level 2 instance is lost, the attached bit in the Level 1 instance LSP continues sending
traffic to the Level 2 instance and causes the traffic to be dropped.
isis read,
write
Examples The following example shows how to set the attached bit for a Level 1 instance that allows the Level
2 instance to redistribute routes from the Level 1 instance:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
782
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
set-attached-bit
redistribute (IS-IS), on page 770 Redistributes routes from one IS-IS instance into another instance.
single-topology, on page 847 Configures the link topology for IPv4 when IPv6 is configured.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
783
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis
show isis
The show isis command displays general information about an IS-IS instance and protocol operation. If the
instance ID is not specified, the command shows information about all IS-IS instances.
Syntax Description instance instance-id (Optional) Displays the IS-IS adjacencies for the specified IS-IS instance only.
Note The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays IS-IS adjacencies for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
For each instance, the first line of output lists the IS-IS instance ID with the following lines identifying the
IS-IS system ID, supported levels (level 1, level 2, or level-1-2), configured area addresses, active area
addresses, status (enabled or not) and type (Cisco or IETF) of nonstop forwarding (NSF), and the mode in
which the last IS-IS process startup occurred.
Next, the status of each configured address family (or just IPv4 unicast if none are configured) is summarized.
For each level (level 1 or level 2), the metric style (narrow or wide) generated and accepted is listed along
with the status of incremental shortest path first (iSPF) computation (enabled or not). Then redistributed
protocols are listed, followed by the administrative distance applied to the redistributed routes.
Finally, the running state (active, passive, or disabled) and configuration state (active or disabled) of each
IS-IS interface is listed.
isis read
Examples The following is sample output from the show isis command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
784
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis
IS Levels: level-2-only
Manual area address(es):
49.1122
Routing for area address(es):
49.1122
Non-stop forwarding: Disabled
Most recent startup mode: Cold Restart
Topologies supported by IS-IS:
IPv4 Unicast
Level-2
Metric style (generate/accept): Narrow/Narrow
Metric: 10
ISPF status: Disabled
No protocols redistributed
Distance: 115
Interfaces supported by IS-IS:
Loopback0 is running passively (passive in configuration)
POS0/1/0/2 is running actively (active in configuration)
POS0/1/0/3 is running actively (active in configuration
Field Description
Routing for area address(es): Configured area addresses and active area addresses.
Non-stop forwarding Status (enabled or not) and type (Cisco or IETF) of nonstop forwarding
(NSF).
Most recent startup mode The mode in which the last IS-IS process startup occurred.
Topologies supported by IS-IS The summary of the status of each configured address family (or just IPv4
unicast if none are configured).
Redistributed protocols List of redistributed protocols, followed by the administrative distance applied
to the redistributed routes.
Metric style (generate/accept) The status of each configured address family (or just IPv4 unicast if none
are configured) is summarized. For each level (level 1 or level 2), the metric
style (narrow or wide) generated and accepted is listed along with the status
of incremental shortest path first (iSPF) computation (enabled or not).
Interfaces supported by IS-IS The running state (active, passive, or disabled) and configuration state (active
or disabled) of each IS-IS interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
785
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis adjacency
show isis [instance instance-id] adjacency [level {1 | 2}] [type interface-path-id] [detail] [systemid
system-id]
Syntax Description instance instance-id (Optional) Displays the IS-IS adjacencies for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
level { 1 | 2 } (Optional) Displays the IS-IS adjacencies for Level 1 or Level 2 independently.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
systemid system-id (Optional) Displays the information for the specified router only.
Command Default No instance ID specified displays IS-IS adjacencies for all the IS-IS instances.
Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis adjacency command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
786
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis adjacency
Field Description
System Dynamic hostname of the system. The hostname is specified using the hostname command. If
ID the dynamic hostname is not known or the hostname dynamic disable command has been
executed, the 6-octet system ID is used.
SNPA Data-link address (also known as the Subnetwork Point of Attachment [SNPA]) of the neighbor.
State Adjacency state of the neighboring interface. Valid states are Down, Init, and Up.
NSF Specifies whether the neighbor can adhere to the IETF-NSF restart mechanism.
BFD Specifies the Bidirectional Forwarding Detection (BFD) status for the interface. Valid status are
• None—BFD is not configured.
• Init—BFD session is not up. One reason is that other side is not yet enabled.
• Up—BFD session has been established.
• Down—BFD session holdtime expired.
show isis neighbors, on page 819 Displays information about IS-IS neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
787
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis adjacency-log
Syntax Description level { 1 | 2 } (Optional) Displays the IS-IS adjacency log for Level 1 or Level 2 independently.
last number (Optional) Specifies that the output is restricted to the last number of entries. Range is 1
to 100.
first number (Optional) Specifies that the output is restricted to the first number of entries. Range is 1
to 100.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis adjacency-log command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
788
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis adjacency-log
Field Description
When Elapsed time (in hh:mm:ss) since the event was logged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
789
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis checkpoint adjacency
Syntax Description instance instance-id (Optional) Displays the IS-IS checkpoint adjacencies for the specified IS-IS instance
only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays IS-IS checkpoint adjacencies for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show isis checkpoint adjacency command to display the checkpointed adjacencies. With this
information you can restore the adjacency database during a Cisco proprietary nonstop forwarding (NSF)
restart. This command, with the show isis adjacency command, can be used to verify the consistency of the
two databases.
isis read
Examples The following is sample output from the show isis checkpoint adjacency command:
RP/0/RSP0/CPU0:router# show
isis
checkpoint
adjacency
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
790
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis checkpoint adjacency
Field Description
System Dynamic hostname of the system. The hostname is specified using the hostname command. If
ID the dynamic hostname is not known or hostname dynamic disable command has been executed,
the 6-octet system ID is used.
show isis checkpoint lsp, on page 794 Displays the IS-IS checkpoint LSP database.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
791
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis checkpoint interface
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis checkpoint interface command:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
792
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis checkpoint interface
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
793
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis checkpoint lsp
Syntax Description instance instance-id (Optional) Displays the IS-IS checkpoint LSPs for the specified instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays IS-IS checkpoint LSPs for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The checkpointed LSPs displayed by this command are used to restore the LSP database during a
Cisco-proprietary nonstop forwarding (NSF) restart. The show isis checkpoint lsp command, with the show
isis database command, may be used to verify the consistency of the two databases.
isis read
Examples The following is sample output from the show isis checkpoint lsp command:
RP/0/RSP0/CPU0:router#
show isis checkpoint lsp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
794
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis checkpoint lsp
Field Description
LSPID LSP identifier. The first six octets form the system ID of the router that originated the LSP.
The next octet is the pseudonode ID. When this byte is 0 , the LSP describes links from the system.
When it is nonzero, the LSP is a so-called nonpseudonode LSP. This is similar to a router link-state
advertisement (LSA) in the Open Shortest Path First (OSPF) protocol. The LSP describes the state
of the originating router.
For each LAN, the designated router for that LAN creates and floods a pseudonode LSP, describing
all systems attached to that LAN.
The last octet is the LSP number. If there is more data than can fit in a single LSP, the LSP is
divided into multiple LSP fragments. Each fragment has a different LSP number. An asterisk (*)
indicates that the LSP was originated by the system on which this command is issued.
show isis checkpoint adjacency, on page 790 Displays the IS-IS checkpoint adjacency database.
show isis database, on page 796 Displays the IS-IS link-state database.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
795
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis database
show isis [instance instance-id] database [level {1 | 2}] [update] [summary] [detail] [verbose]
[{*lsp-id}]
Syntax Description instance instance-id (Optional) Displays the IS-IS LSP database for the specified instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
level { 1 | 2 } (Optional) Displays the IS-IS LSP database for Level 1 or Level 2 independently.
summary (Optional) Displays the LSP ID number, sequence number, checksum, hold time,
and bit information.
* | lsp-id (Optional) LSP protocol data units (PDUs) identifier. Displays the contents of a
single LSP by its ID number or may contain an * as a wildcard character.
Command Default No instance ID specified displays the IS-IS LSP database for all the IS-IS instances.
Both Level 1 and Level 2 is configured if no level is specified.
Release 5.2.0 The output of this command when verbose keyword is used is modified to display adjacency
prefix segment IDs.
Usage Guidelines Each of the options for the show isis database command can be entered in an arbitrary string within the
same command entry. For example, the following are both valid command specifications and provide the
same output: show isis database detail level 2 and show isis database level 2 detail .
The summary keyword used with this command allows you to filter through a large IS-IS database and
quickly identify problematic areas.
isis read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
796
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis database-log
Syntax Description level { 1 | 2 } (Optional) Displays the database log for Level 1 or Level 2 independently.
last number (Optional) Specifies that the output be restricted to the last number of entries. Range is 1
to 1000.
first number (Optional) Specifies that the output be restricted to the first number of entries. Range is
1 to 1000.
Command Default Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis database-log command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
797
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis database-log
Field Description
WHEN Elapsed time (in hh:mm:ss) since the event was logged.
LSPID LSP identifier. The first six octets form the system ID of the router that originated the LSP.
The next octet is the pseudonode ID. When this byte is 0 , the LSP describes links from the system.
When it is nonzero, the LSP is a so-called nonpseudonode LSP. This is similar to a router link-state
advertisement (LSA) in the Open Shortest Path First (OSPF) protocol. The LSP describes the state
of the originating router.
For each LAN, the designated router for that LAN creates and floods a pseudonode LSP, describing
all systems attached to that LAN.
The last octet is the LSP number. If there is more data than can fit in a single LSP, the LSP is
divided into multiple LSP fragments. Each fragment has a different LSP number. An asterisk (*)
indicates that the LSP was originated by the system on which this command is issued.
Seq Sequence number for the LSP that allows other systems to determine if they have received the
Num latest information from the source.
Holdtime Time the LSP remains valid (in seconds). An LSP hold time of 0 indicates that this LSP was
purged and is being removed from the link-state database (LSDB) of all routers. The value indicates
how long the purged LSP stays in the LSDB before being completely removed.
OL Overload bit. Determines if the IS is congested. If the Overload bit is set, other routers do not use
this system as a transit router when calculating routers. Only packets for destinations directly
connected to the overloaded router are sent to this router.
show isis database, on page 796 Displays the IS-IS link-state packet (LSP) database.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
798
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis fast-reroute
summary Use to display the number of prefixes having protection per priority.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The following is sample output from show isis fast-reroute command that displays per-prefix LFA
information:
L1 10.1.6.0/24 [20/115]
via 10.3.7.47, POS0/3/0/1, router2
FRR backup via 10.1.7.145, GigabitEthernet0/1/0/3, router3
The following is sample output from show isis fast-reroute detail command that displays tie-breaker
information about the backup:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
799
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis fast-reroute
The following is sample output from show isis fast-reroute summary command that displays the
number of prefixes having protection per priority:
Prefixes reachable in L1
All paths protected 0 0 2 8 10
Unprotected 0 0 1 3
4
Protection coverage 0.00% 0.00% 75.00% 78.57% 77.78%
Prefixes reachable in L2
All paths protected 0 0 0 0 0
Unprotected 0 0 0 0
0
Protection coverage 0.00% 0.00% 100.00% 0.00% 100.00%
The following is sample output from show isis fast-reroute sr-only command that displays fast-reroute
repair paths for prefixes associated with a segment routing prefix SID:
L2 20.1.0.101/32 [10/115]
via 10.1.1.101, GigabitEthernet0/0/0/2, r101, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.4.1.103, GigabitEthernet0/0/0/1 r103, SRGB Base:
16000, Weight: 0
P node: r103.00 [20.1.0.103], Label: ImpNull
Q node: r102.00 [20.1.0.102], Label: 24001
Prefix label: 16101
Backup-src: r101.00
L2 20.1.0.102/32 [30/115]
via 10.1.1.101, GigabitEthernet0/0/0/2, r101, SRGB Base: 16000, Weight: 0
Backup path: TI-LFA (link), via 10.4.1.103, GigabitEthernet0/0/0/1 r103, SRGB Base:
16000, Weight: 0
P node: r103.00 [20.1.0.103], Label: ImpNull
Q node: r102.00 [20.1.0.102], Label: 24001
Prefix label: ImpNull
Backup-src: r102.00
L2 20.1.0.103/32 [20/115]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
800
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis fast-reroute
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
801
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis hostname
Syntax Description instance instance-id (Optional) Displays the IS-IS router name-to-system ID mapping table for the
specified IS-IS instance only.
The instance-id argument is the instance identifier (alphanumeric) defined by the
router isis command.
Command Default No instance ID specified displays the IS-IS router name-to-system ID mapping table for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The show isis hostname command does not display entries if the dynamic hostnames are disabled.
isis read
Examples The following is sample output from the show isis hostname command with the instance and
instance-id values specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
802
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis hostname
Field Description
System ID Dynamic hostname of the system. The hostname is specified using the hostname
command. If the dynamic hostname is not known or hostname dynamic disable
command has been executed, the 6-octet system ID is used.
* Local router.
hostname dynamic disable, on page 700 Enables the IS-IS routing protocol to dynamically update the
mapping of router names to system IDs.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
803
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis interface
Syntax Description type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
level { 1 | 2 } (Optional) Displays IS-IS interface information for Level 1 or Level 2 independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis interface command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
804
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis interface
Level-2
Adjacency Count: 1
LSP Pacing Interval: 33 ms
PSNP Entry Queue Size: 0
CLNS I/O
Protocol State: Up
MTU: 4469
Field Description
Circuit Type Levels the interface is running on (circuit-type configuration) which may be
a subset of levels on the router.
Extended Circuit Number Valid only for point-to-point interfaces (32-bit integer).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
805
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis interface
Field Description
LSP Rexmit Queue Size Number of LSPs pending retransmission on the interface.
Adjacency Count Number of adjacencies formed with a neighboring router that supports the
same set of protocols.
PSNP Entry Queue Size Number of SNP entries pending inclusion in the next PSNP.
Priority (Local/DIS) Priority of this interface or priority of the Designated Intermediate System.
Next LAN IIH in Time (in seconds) in which the next LAN hello message is sent.
LSP Pacing Interval Interval at which the link-state packet (LSP) transmission rate (and by
implication the reception rate of other systems) is to be reduced.
SNPA Data-link address (also known as the Subnetwork Point of Attachment [SNPA])
of the neighbor.
All Level-n ISs Status of interface membership in Layer 2 multicast group. The status options
are Yes or reason for not being a member of the multicast group.
Adjacency Formation Status of adjacency formation. The status options are Running or a reason for
not being ready to form adjacencies.
Metric (L1/L2) IS-IS metric for the cost of the adjacency between the originating router and
the advertised neighbor, or the metric of the cost to get from the advertising
router to the advertised destination (which can be an IP address, an end system
(ES), or a connectionless network service (CLNS) prefix).
MPLS LDP Sync (L1/L2) Status of LDP IS-IS synchronization, either enabled or disabled. When enabled,
the state of synchronization (Sync Status) is additionally displayed as either
achieved or not achieved.
IPv4 Address Family Status of the address family, either enabled or disabled.
Forwarding Address(es) Addresses on this interface used by the neighbor for next-hop forwarding.
LSP transmit timer expires in LSP transmission expiration timer interval (in milliseconds).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
806
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis interface
Field Description
The following is sample output from the show isis interface command with the brief keyword:
Interface All Adjs Adj Topos Adv Topos CLNS MTU Prio
OK L1 L2 Run/Cfg Run/Cfg L1 L2
----------------- --- --------- --------- --------- ---- ---- --------
PO0/5/0/0 Yes 1 1 1/1 1/1 Up 4469 - -
Gi0/6/0/0 Yes 1* 1* 1/1 1/1 Up 1497 64 64
Field Description
Adj Topos Run/Cfg Number of topologies that participate in forming adjacencies. Number of topologies
that were configured to participate in forming adjacencies.
Adv Topos Run/Cfg Number of topologies that participate in advertising prefixes. Number of topologies
that were configured to participate in advertising prefixes.
CLNS Status of the Connectionless Network Service. Status options are Up or Down.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
807
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis lsp-log
show isis [instance instance-id] lsp-log [level {1 | 2}] [{last number | first number}]
Syntax Description instance instance-id (Optional) Displays the LSP log information for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined by
the router isis command.
last number (Optional) Specifies that the output be restricted to the last number of entries.
Range is 1 to 20.
first number (Optional) Specifies that the output be restricted to the first number of entries.
Range is 1 to 20.
Command Default No instance ID specified displays the LSP log information for all the IS-IS instances.
Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis lsp-log command with the instance and instance-id
values specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
808
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis lsp-log
Field Description
When How long ago (in hh:mm:ss) an LSP rebuild occurred. The last 20 occurrences are logged.
Count Number of events that triggered this LSP run. When there is a topology change, often multiple
LSPs are received in a short period. A router waits 5 seconds before running a full LSP, so it can
include all new information. This count denotes the number of events (such as receiving new LSPs)
that occurred while the router was waiting its 5 seconds before running full LSP.
Interface Interface that corresponds to the triggered reasons for the LSP rebuild.
Triggers A list of all reasons that triggered an LSP rebuild. The triggers are
• AREASET—area set changed
• ATTACHFLAG—bit attached
• CLEAR— clear command
• CONFIG—configuration change
• DELADJ—adjacency deleted
• DIS—DIS changed
• IFDOWN—interface down
• IPADDRCHG—IP address change
• IPDEFORIG—IP def-orig
• IPDOWN—connected IP down
• IFDOWN—interface down
• IPEXT—external IP
• IPIA—nterarea IP
• IPUP—connected IP up
• LSPDBOL—LSPDBOL bit
• LSPREGEN—LSP regeneration
• NEWADJ— new adjacency
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
809
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mesh-group
Syntax Description instance instance-id (Optional) Displays the mesh group information for the specified IS-IS instance
only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays the IS-IS mesh group information for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis mesh-group command with the instance and
instance-id values specified:
Mesh group 6:
GigabitEthernet 0/4/0/1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
810
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mesh-group
Field Description
Mesh group Mesh group number to which this interface is a member. A mesh group optimizes
link-state packet (LSP) flooding in nonbroadcast multiaccess (NBMA) networks
with highly meshed, point-to-point topologies. LSPs that are first received on
interfaces that are part of a mesh group are flooded to all interfaces except those in
the same mesh group.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
811
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng adjacency-log
show isis [instance instance-id] mpls traffic-eng adjacency-log [{last number | first number}]
Syntax Description instance instance-id (Optional) Displays the MPLS TE adjacency changes for the specified IS-IS instance
only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
last number (Optional) Specifies that the output is restricted to last number of entries. Range
is 1 to 20.
first number (Optional) Specifies that the output is restricted to first number of entries. Range
is 1 to 20.
Command Default No instance ID specified displays MPLS TE adjacency changes for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show isis mpls traffic-eng adjacency-log command to display the status of MPLS TE adjacencies.
isis read
Examples The following is sample output from the show isis mpls traffic-eng adjacency-log command with
the instance and instance-id values specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
812
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng adjacency-log
Table 66: show isis instance isp mpls traffic-eng adjacency-log Field Descriptions
Field Description
When Time (in hh:mm:ss) since the entry was recorded in the log.
show isis mpls traffic-eng advertisements, on page Displays the last flooded record from MPLS traffic
814 engineering.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
813
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng advertisements
Syntax Description instance instance-id (Optional) Displays the latest flooded record from MPLS TE for the specified IS-IS
instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays the latest flooded record from MPLS TE for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show isis mpls traffic-eng advertisements command to verify that MPLS TE is flooding its record
and that the bandwidths are correct.
isis read
Examples The following is sample output from the show isis mpls traffic-eng advertisements command
with the instance and instance-id values specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
814
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng advertisements
Table 67: show isis instance isp mpls traffic-eng advertisements Field Descriptions
Field Description
System ID Dynamic hostname of the system. The hostname is specified using the
hostname command. If the dynamic hostname is not known or if the hostname
dynamic disable command has been executed, the 6-octet system ID is used.
Neighbor System ID System ID of a neighbor number in an area. The six bytes directly preceding
the n-selector are the system ID. The system ID length is a fixed size and cannot
be changed. The system ID must be unique throughout each area (Level 1) and
throughout the backbone (Level 2). In an IS-IS routing domain, each router is
represented by a 6-byte hexadecimal system ID. When network administrators
maintain and troubleshoot networking devices, they must know the router name
and corresponding system ID.
Global pool BW unreserved Unreserved bandwidth that is available in the global pool.
Sub pool BW unreserved Amount of unreserved bandwidth that is available in the subpool.
Affinity Bits Link attribute flags being flooded. Bits are MPLS-TE specific.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
815
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng advertisements
show isis mpls traffic-eng adjacency-log, on page Displays a log of MPLS TE adjacency changes for
812 IS-IS.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
816
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng tunnel
Syntax Description instance instance-id (Optional) Displays the MPLS TE tunnel information for the specified IS-IS instance
only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays the MPLS TE tunnel information for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show isis command to find the current status of MPLS TE tunnels.
Tunnels are used in IS-IS next-hop calculations.
isis read
Examples The following is sample output from the show isis mpls traffic-eng tunnel command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
817
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis mpls traffic-eng tunnel
Field Description
System ID Dynamic hostname of the system. The hostname is specified using the hostname command.
If the dynamic hostname is not known or hostname dynamic disable command has been
executed, the 6-octet system ID is used.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
818
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis neighbors
show isis [instance instance-id] neighbors [{type interface-path-id | summary}] [detail] [systemid
system-id]
Syntax Description instance instance-id (Optional) Displays the IS-IS neighbor information for the specified IS-IS instance
only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
systemid system-id (Optional) Displays the information for the specified neighbor only.
Command Default No instance ID specified displays neighbor information for all the IS-IS instances.
Both Level 1 and Level 2 are configured if no level is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
819
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis neighbors
Examples The following is sample output from the show isis neighbors command with the instance and
instance-id values specified:
Field Description
System ID Dynamic hostname of the system. The hostname is specified using the hostname
command. If the dynamic hostname is not known or hostname dynamic disable
command has been executed, the 6-octet system ID is used.
SNPA Data-link address (also known as the Subnetwork Point of Attachment [SNPA]) of
the neighbor.
State Adjacency state of the neighboring interface. Valid states are: Down, Init, and Up.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
820
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis neighbors
Field Description
IETF-NSF Specifies whether the neighbor can adhere to the IETF-NSF restart mechanism.
Valid states are Capable and Unable.
Uptime Time (in hh:mm:ss) that the neighbor has been up.
IPFRR: LFA Neighbor IP fast reroute (IPFRR) loop-free alternate (LFA) neighbor.
The following is sample output from the show isis neighbors command with the summary
keyword specified:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
821
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis protocol
Syntax Description instance instance-id (Optional) Displays the IS-IS adjacencies for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
Command Default No instance ID specified displays IS-IS adjacencies for all the IS-IS instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis protocol command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
822
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis protocol
Field Description
System ID: Dynamic hostname of the system. The hostname is specified using the hostname
command. If the dynamic hostname is not known or hostname dynamic disable
command has been executed, the 6-octet system ID is used.
Routing for areaaddress(es) Area addresses for which this router provides the routing.
Process startup mode: Mode in which the last process startup occurred. Valid modes are:
• Cisco Proprietary NSF Restart
• IETF NSF Restart
• Cold Restart
iSPF status: State of incremental shortest path first (iSPF) configuration for this IS-IS
instance. Four states exist:
Disabled if iSPF has not been configured but is awaiting a full SPF to compile
the topology for use by the iSPF algorithm.
Dormant if iSPF has been configured but is awaiting initial convergence before
initializing.
Awake if iSPF has been configured but is awaiting a full SPF to compile the
topology for use by the iSPF algorithm.
Active if IS-IS is ready to consider using the iSPF algorithm whenever a new
route calculation needs to be run.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
823
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis route
show isis [instance instance-id] [{ipv4 | ipv6 | afi-all}] [{unicast | multicast [topology {alltopo-name}]
| safi-all}] route [{ip-address mask | ip-address/length [longer-prefixes]}] [summary] [multicast-intact]
[backup] [detail] [sr-only]
Syntax Description instance instance-id (Optional) Displays the IP reachability information for the specified IS-IS instance
only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
topology topo-name (Optional) Specifies topology table information and name of the topology table.
ip-address (Optional) Network IP address about which routing information should be displayed.
/ length (Optional) Length of the IP prefix. A decimal value that indicates how many of
the high-order contiguous bits of the address compose the prefix (the network
portion of the address). A slash must precede the decimal value. Range is 0 to 32.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
824
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis route
Command Default No instance ID specified displays the IP reachability information for all the IS-IS instances.
Release 5.2.0 The output of this command when detail keyword is used is modified to display prefix
segment ID index values.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis route command:
L2 10.76.240.6/32 [4/115]
via 10.76.245.252, SRP0/1/0/2, isp2
via 10.76.246.252, SRP0/1/0/0, isp2
C 10.76.240.7/32
is directly connected, Loopback0
L2 10.76.240.9/32 [256/115]
via 10.76.249.2, GigabitEthernet 0/3/0/0, isp3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
825
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis route
L2 10.76.240.10/32 [296/115]
via 10.76.249.2, GigabitEthernet 0/3/0/0, isp3
C 10.76.245.0/24
is directly connected, SRP0/1/0/2
C 10.76.246.0/24
is directly connected, SRP0/1/0/0
C 10.76.249.0/26
is directly connected, GigabitEthernet 0/3/0/0
L2 10.101.10.0/24 [296/115]
via 10.76.249.2, GigabitEthernet 0/3/0/0, isp3
Field Description
This is sample output from the show isis route command with detail keyword that shows prefix
segment ID (SID) and Segment Routing Global Block (SRGB) values:
Sun May 4 13:05:11.073 PDT
This is sample output from the show isis route command with sr-only keyword that shows only
routes associated with a segment routing prefix SID:
C 20.1.0.100/32
is directly connected, Loopback0
L2 20.1.0.101/32 [10/115]
via 10.1.1.101, GigabitEthernet0/0/0/2, r101, SRGB Base: 16000, Weight: 0
L2 20.1.0.102/32 [30/115]
via 10.1.1.101, GigabitEthernet0/0/0/2, r101, SRGB Base: 16000, Weight: 0
L2 20.1.0.103/32 [20/115]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
826
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis route
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
827
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
show isis [instance instance-id] [[{ipv4 | ipv6 | afi-all}] [{unicast | multicast [topology {alltopo-name}]
| safi-all}]] spf-log [level {1 | 2}] [{ispf | fspf | prc | nhc}] [{detail | verbose | plfrr | ppfrr}] [{last
number | first number}]
Syntax Description instance instance-id (Optional) Displays the IS-IS SPF log for the specified IS-IS instance only.
topology all | topo-name (Optional) Specifies topology table information for all topologies or for the
specified topology table ( top-name ).
level { 1 | 2 } (Optional) Displays the IS-IS SPF log for Level 1 or Level 2 independently.
detail (Optional) Specifies detailed output. Includes a breakdown of the time taken
to perform the calculation and changes resulting from the calculation.
last number (Optional) Specifies that the output is restricted to the last number of entries.
Range is 1 to 210.
first number (Optional) Specifies that the output is restricted to the first number of entries.
Range is 1 to 210.
Command Default No instance ID specified displays IS-IS adjacencies for all the IS-IS instances.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
828
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read
Examples The following is sample output from the show isis spf-log command:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
829
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
Field Description
Duration Number of milliseconds taken to complete this SPF run. Elapsed time is wall clock time,
not CPU time.
Nodes Number of routers and pseudonodes (LANs) that make up the topology calculated in this
SPF run.
Trig Count Number of events that triggered this SPF run. When there is a topology change, often
multiple link-state packets (LSPs) are received in a short time. Depending on the
configuration of the spf-interval command, a router may wait for a fixed period of time
before running a router calculation. This count denotes the number of triggering events
that occurred while the router was waiting to run the calculation. For a full description of
the triggering events, see List of Triggers.
First Trigger LSP ID stored by the router whenever a full SPF calculation is triggered by the arrival of
LSP a new LSP. The LSP ID can suggest the source of routing instability in an area. If multiple
LSPs are causing an SPF run, only the LSP ID of the first received LSP is remembered.
Triggers List of all reasons that triggered a full SPF calculation. For a list of possible triggers, see
List of Triggers.
Trigger Description
ADMINDIST Configured another administrative distance for the IS-IS instance on this router.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
830
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
Trigger Description
TLVCODE Type, length, and value (TLV) objects code mismatch, indicating that different TLV
objects are included in the newest version of an LSP.
The following is sample output from the show isis spf-log command with the first keyword
specified:
Field Description
Type Type of route calculation. The possible types are incremental SPF (iSPF), full SPF (FSPF),
or partial route calculation (PRC).
Time (ms) Number of milliseconds taken to complete this SPF run. Elapsed time is wall clock time,
not CPU time.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
831
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
Field Description
Nodes Number of routers and pseudonodes (LANs) that make up the topology calculated in this
SPF run.
Trig Count Number of events that triggered this SPF run. When there is a topology change, often
multiple link-state packets (LSPs) are received in a short time. Depending on the
configuration of the spf-interval command, a router may wait for a fixed period of time
before running a router calculation. This count denotes the number of triggering events
that occurred while the router was waiting to run the calculation. For a full description of
the triggering events, see List of Triggers.
First Trigger LSP ID stored by the router whenever a full SPF calculation is triggered by the arrival of
LSP a new LSP. The LSP ID can suggest the source of routing instability in an area. If multiple
LSPs are causing an SPF run, only the LSP ID of the first received LSP is remembered.
Triggers List of all reasons that triggered a full SPF calculation. For a list of possible triggers, see
List of Triggers.
The following is sample output from the show isis spf-log command with the detail keyword
specified:
All Priorities 0 0 0
Prefixes (Routes)
Critical Priority: 0 - 0
High Priority: 0 - 0
Medium Priority 0 - 0
Low Priority: 0 - 0
All Priorities 0 - 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
832
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
Field Description
Type Type of route calculation. The possible types are incremental SPF (iSPF), full SPF
(FSPF), or partial route calculation (PRC).
Time (ms) Number of milliseconds taken to complete this SPF run. Elapsed time is wall clock time,
not CPU time.
Nodes Number of routers and pseudonodes (LANs) that make up the topology calculated in this
SPF run.
Trig Count Number of events that triggered this SPF run. When there is a topology change, often
multiple link-state packets (LSPs) are received in a short time. Depending on the
configuration of the spf-interval command, a router may wait for a fixed period of time
before running a router calculation. This count denotes the number of triggering events
that occurred while the router was waiting to run the calculation. For a full description
of the triggering events, see List of Triggers.
First Trigger LSP LSP ID stored by the router whenever a full SPF calculation is triggered by the arrival
of a new LSP. The LSP ID can suggest the source of routing instability in an area. If
multiple LSPs are causing an SPF run, only the LSP ID of the first received LSP is
remembered.
Triggers List of all reasons that triggered a full SPF calculation. For a list of possible triggers, see
List of Triggers.
New LSP Arrivals Number of LSP arrivals since the start of this route calculation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
833
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis spf-log
Field Description
Next Wait Interval Enforced delay until the next route calculation can be run, based on the spf-interval
command configuration.
spf-interval, on page 849 Sets IS-IS throttling of shortest path first (SPF) calculations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
834
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis statistics
Syntax Description instance instance-id (Optional) Displays the IS-IS traffic statistics for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
Command Default No instance ID specified displays IS-IS traffic statistics for all the IS-IS instances.
IS-IS traffic statistics are displayed for all interfaces.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The show isis statistics command displays IS-IS traffic counters for the specified interface or all traffic
counters if no interface is specified.
isis read
Examples The following is sample output from the show isis statistics command that shows all traffic counters:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
835
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis statistics
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
836
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis statistics
Field Description
Fast PSNP cache (hits/tries) Number of successful lookups (hits) along with the number of lookup
attempts (tries). To save time or processing power when receiving multiple
copies of the same LSP, IS-IS attempts to look up incoming LSPs to see if
they have been received recently.
Fast CSNP cache (hits/tries) Number of successful lookups (hits) along with the number of lookup
attempts (tries). To reduce CSNP construction time, IS-IS maintains a cache
of CSNPs and attempts to look up CSNP in this cache before transmission
on the interface.
Fast CSNP cache updates Number of times the CSNP cache has been updated since the last clearing
of statistics. The cache is updated on LSP addition or removal from the
database.
LSP checksum errors received Number of internal checksum errors received in LSPs.
IIH (LSP/SNP) dropped Number of hello, LSP, and SNP messages dropped.
Average transmit times and Average time taken to transmit the pdu type across all interfaces and the
rate corresponding rate at which the pdu type is being transmitted.
Average process times and rate Average time taken to process an incoming pdu type across all interfaces
and the corresponding rate at which the pdu type is being received.
LSPs sourced (new/refresh) Number of LSPs this IS-IS instance has created or refreshed. To find more
details on these LSPs, use the show isis lsp-log command.
SPF calculations Number of shortest path first (SPF) calculations. SPF calculations are
performed only when the topology changes. They are not performed when
external routes change. The interval at which SPF calculations are performed
is configured using the spf-interval command.
iSPF calculations Number of incremental shortest path first (iSPF) calculations. iSPF
calculations are performed only when ISPF has been configured in the isis
address family configuration submode.
Partial Route Calculations Number of partial route calculations (PRCs). PRCs are processor intensive.
Therefore, it may be useful to limit their number, especially how often a
PRC is done, especially on slower networking devices. Increasing the PRC
interval reduces the processor load on the router, but might slow the rate of
convergence. The interval at which PRC calculations are performed is
configured using the spf-interval command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
837
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis statistics
Field Description
Level-(1.2) DRElections Total number of Designated Intermediate System elections that have taken
place. These counts are maintained on an individual level basis.
LSP Flooding Duplicates Number of duplicate LSPs filtered from flooding to the neighbor. In case
of parallel interfaces to the same neighbor, IS-IS optimizes the flooding by
avoiding sending the same LSP copy on other interfaces.
show isis spf-log, on page 828 Displays how often and why the router has run a full SPF calculation.
spf-interval, on page 849 Sets IS-IS throttling of shortest path first (SPF) calculations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
838
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis topology
show isis [instance instance-id] [[{ipv4 | ipv6 | afi-all}] [{unicast | multicast [topology {all |
topo-name}] | safi-all}]] | summary | level {1 | 2} [multicast-intact] [systemid system-id] [detail]
Syntax Description instance instance-id (Optional) Displays the IS-IS topology for the specified IS-IS instance only.
• The instance-id argument is the instance identifier (alphanumeric) defined
by the router isis command.
topology topo-name (Optional) Specifies topology table information and name of the topology table.
level { 1 | 2 } (Optional) Displays the IS-IS link-state topology for Level 1 or Level 2
independently.
systemid system-id (Optional) Displays the information for the specified router only.
Command Default No instance ID specified displays a list of connected routers in all areas for all the IS-IS instances.
Both Level 1 and Level 2 is configured if no level is specified.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
839
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis topology
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show isis topology command to verify the presence and connectivity among all routers in all areas.
isis read
Examples The following is sample output from the show isis topology command:
Field Description
System Dynamic hostname of the system. The hostname is specified using the hostname command. If
ID the dynamic hostname is not known or hostname dynamic disable command has been executed,
the 6-octet system ID is used.
Metric Metric assigned to the link and used to calculate the cost from each router using the links in the
network to other destinations. Range is 1 to 16777214. Default is 1 to 63 for narrow metric and
1 to 16777214 for wide metric. 0 is set internally if no metric has been specified by the user.
SNPA Data-link address (also known as the Subnetwork Point of Attachment [SNPA]) of the neighbor.
The following is sample output from the show isis topology command with the summary keyword
specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
840
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show isis topology
Total nodes: 1 1 2 1 1 2
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
841
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show protocols (IS-IS)
protocol (Optional) Specifies a routing protocol. For the IPv4 address family, the options are:
• bgp
• isis
• ospf
• rip
• eigrp
For the IPv6 address family, the options are:
• bgp
• isis
• ospfv3
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If IPv6 is enabled on an IS-IS instance, the instance is displayed in the show protocols ipv6 command output.
IPv4 IS-IS instances are displayed in the show protocols ipv4 command output.
When using the show protocols command with the ipv6 or ipv4 keyword, you get all routing instances
in that particular address family—not only IS-IS instances.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
842
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show protocols (IS-IS)
isis read
rib read
Examples The following example shows the output for the show protocols command :
Field Description
System ID Dynamic hostname of the system. The hostname is specified using the
hostname command. If the dynamic hostname is not known or hostname
dynamic disable command has been executed, the 6-octet system ID is
used.
Manual area address(es) Area addresses configured manually on the originating router.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
843
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show protocols (IS-IS)
Field Description
Routing for area address(es) Area addresses for which this router provides the routing.
Most recent startup mode Mode in which the most recent startup was performed.
Topologies supported by IS-IS Address and subaddress family IS-IS are configured.
Metric style Type, length, and value (TLV) objects accepted by IS-IS. To configure this
value, see the metric-style narrow, on page 735, metric-style transition, on
page 737, or metric-style wide, on page 739 command.
ISPF status State of iSPF configuration for this IS-IS instance. Four states exist:
• Disabled if iSPF has not been configured but is awaiting a full SPF to
compile the topology for use by the iSPF algorithm.
• Dormant if iSPF has been configured but is awaiting initial convergence
before initializing.
• Awake if iSPF has been configured but is awaiting a full SPF to compile
the topology for use by the iSPF algorithm.
• Active if IS-IS is ready to consider using the iSPF algorithm whenever
a new route calculation needs to be run.
Interfaces supported by IS-IS Interfaces and their states currently supported by IS-IS. Both operational and
configuration status are displayed.
The following example shows how to disable the IPv4 address family, with no output shown for
IS-IS IPv4 instances from the show protocols ipv4 command:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router isis uut
RP/0/RSP0/CPU0:router(config-isis)# no address-family ipv4 unicast
RP/0/RSP0/CPU0:router(config-isis)# commit
metric-style narrow, on page 735 Configures the IS-IS software to generate and accept old-style type,
length, and value (TLV) objects.
metric-style transition, on page 737 Configures the IS-IS software to generate and accept both old-style and
new-style type length, and value (TLV) objects.
metric-style wide, on page 739 Configures the IS-IS software to generate and accept only new-style
type, length, and value (TLV) objects.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
844
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
show protocols (IS-IS)
Command Description
redistribute (IS-IS), on page 770 Redistributes routes from one IS-IS instance into another instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
845
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
shutdown (IS-IS)
shutdown (IS-IS)
To disable the Intermediate System-to-Intermediate System (IS-IS) protocol on a particular interface, use the
shutdown command in interface configuration mode. To re-enable the IS-IS protocol, use the no form of
this command.
shutdown
no shutdown
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example disables the IS-IS protocol on GigabitEthernet interface 0/1/0/1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
846
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
single-topology
single-topology
To configure the link topology for IP Version 4 (IPv4) when IP Version 6 (IPv6) is configured, use the
single-topology command in address family configuration mode. To remove the single-topology command
from the configuration file and restore the system to its default condition, use the no form of this command.
single-topology
no single-topology
Command Default Performs in multitopology mode in which independent topologies for IPv4 and IPv6 are running in a single
area or domain.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the single-topology command to allow Intermediate System-to-Intermediate System (IS-IS) for IPv6
to be configured on interfaces along with an IPv4 network protocol. All interfaces must be configured with
the identical set of network protocols, and all routers in the IS-IS area (for Level 1 routing) or the domain (for
Level 2 routing) must support the identical set of network layer protocols on all interfaces.
When single-topology support for IPv6 is being used, only old-style type, length, and value (TLV) objects
may be used and a single shortest path (SPF) individual level is used to compute IPv4 (if configured) and
IPv6 routes. The use of a single SPF means that both IPv4 IS-IS and IPv6 IS-IS routing protocols must share
a network topology.
To allow link information to be shared between IPv4 and IPv6, you must configure the single-topology
command for an address family. In single-topology IPv6 mode, the configured metric is always the same for
both IPv4 and IPv6.
isis read,
write
Examples The following example shows how to enable single-topology mode for IPv6:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
847
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
snmp-server traps isis
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples
adjacency-change isisAdjacencyChange
all Enable all IS-IS traps
area-mismatch isisAreaMismatch
attempt-to-exceed-max-sequence isisAttemptToExceedMaxSequence
authentication-failure isisAuthenticationFailure
authentication-type-failure isisAuthenticationTypeFailure
corrupted-lsp-detected isisCorruptedLSPDetected
database-overload isisDatabaseOverload
id-len-mismatch isisIDLenMismatch
lsp-error-detected isisLSPErrorDetected
lsp-too-large-to-propagate isisLSPTooLargeToPropagate
manual-address-drops isisManualAddressDrops
max-area-addresses-mismatch isisMaxAreaAddressesMismatch
orig-lsp-buff-size-mismatch isisOrigLSPBuffSizeMismatch
own-lsp-purge isisOwnLSPPurge
protocols-supported-mismatch isisProtocolsSupportedMismatch
rejected-adjacency isisRejectedAdjacency
sequence-number-skip isisSequenceNumberSkip
version-skew isisVersionSkew
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
848
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
spf-interval
spf-interval
To customize IS-IS throttling of shortest path first (SPF) calculations, use the spf-interval command in
address family configuration mode. To restore default values, use the no form of this command.
Syntax Description initial-wait initial Initial SPF calculation delay (in milliseconds) after a topology change. Range
is 0 to 120000.
secondary-wait secondary Hold time between the first and second SPF calculations (in milliseconds).
Range is 0 to 120000.
maximum-wait maximum Maximum interval (in milliseconds) between two consecutive SPF calculations.
Range is 0 to 120000.
level { 1 | 2 } (Optional) Enables the SPF interval configuration for Level 1 or Level 2
independently.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
SPF calculations are performed only when the topology changes. They are not performed when external routes
change.
Use the spf-interval command to control how often the software can perform the SPF calculation. The SPF
calculation is processor intensive. Therefore, it may be useful to limit how often this calculation is done,
especially when the area is large and the topology changes often. Increasing the SPF interval reduces the
processor load of the router, but potentially slows the rate of convergence.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
849
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
spf-interval
Examples The following example shows how to set the initial SPF calculation delay to 10 milliseconds and the
maximum interval between two consecutive SPF calculations to 5000 milliseconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
850
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
spf prefix-priority (IS-IS)
spf prefix-priority [level {1 | 2}] {critical | high | medium} {access-list-name | tag tag}
no spf prefix-priority [level {1 | 2}] {critical | high | medium} [{access-list-name | tag tag}]
Syntax Description level { 1 | 2 } (Optional) Enables the assignment of a priority to Level 1 or Level 2 independently.
tag tag Specifies a tag to indicate priority. The tag argument range is 1 to 4294967295.
Command Default By default, IPv4 prefixes with a length of 32 and IPv6 prefixes with a length of 128 are given medium priority.
The remaining prefixes are given low priority.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the spf prefix-priority command to change the sequence of prefix updates to the RIB after an SPF is
run. ISIS installs prefixes in the RIB according to the following priority order:
Critical > High > Medium > Low
The spf prefix-priority command supports prefix lists for the first three priorities. The unmatched prefixes
are updated with low priority.
If a spf prefix-priority is specified, the default behavior of prioritizing either length 32 or 128 prefixes for
IPv4 or IPv6, respectively, as medium is disabled.
isis read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
851
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
spf prefix-priority (IS-IS)
Examples The following example shows how to set the prefix priorities:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
852
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
summary-prefix (IS-IS)
summary-prefix (IS-IS)
To create aggregate addresses for the Intermediate System-to-Intermediate System (IS-IS) protocol, use the
summary-prefix command in address family configuration mode. To restore the default behavior, use the
no form of this command.
Syntax Description address Summary address designated for a range of IPv4 addresses. The address argument must
be in four-part, dotted-decimal notation.
/ prefix-length Length of the IPv4 or IPv6 prefix. A decimal value that indicates how many of the
high-order contiguous bits of the address compose the prefix (the network portion of the
address). A slash must precede the decimal value.
ipv6-prefix Summary prefix designated for a range of IPv6 prefixes. The ipv6-prefix argument must
be in the form documented in RFC 2373, in which the address is specified in hexadecimal
using 16-bit values between colons.
level { 1 | 2 } (Optional) Redistributes routes into Level 1 or Level 2 and summarizes them with the
configured address and mask value.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Multiple groups of addresses can be summarized for a given level. Routes learned from other routing protocols
can also be summarized. The metric used to advertise the summary is the smallest metric of all the more-specific
routes. Use the summary-prefix command to help reduce the size of the routing table.
This command also reduces the size of the link-state packets (LSPs) and thus the link-state database. It also
helps ensure stability, because a summary advertisement depends on many more specific routes. If one
more-specific route flaps, in most cases, this flap does not cause a flap of the summary advertisement.
The drawback of summary addresses is that other routes might have less information to calculate the most
optimal routing table for all individual destinations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
853
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
summary-prefix (IS-IS)
Note When IS-IS advertises a summary prefix, it automatically inserts the summary prefix into the IP routing table
but labels it as a “discard” route entry. Any packet that matches the entry is discarded to prevent routing loops.
When IS-IS stops advertising the summary prefix, the routing table entry is removed.
isis read,
write
Examples The following example shows how to redistribute Open Shortest Path First (OSPF) routes into IS-IS:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
854
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
suppressed
suppressed
To allow an IS-IS interface to participate in forming adjacencies without advertising connected prefixes in
the system link-state packets (LSPs), use the suppressed command in interface configuration mode. To
enable advertising connected prefixes, use the no form of this command.
suppressed
no suppressed
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the suppressed command to reduce the number of routes that IS-IS has to maintain, improving
convergence times after an isolated failure. Improvement is noticeable if the command is used widely throughout
the network. Other routers in the domain do not install routes to the affected connected prefixes.
isis read,
write
Examples The following example shows how to disable the advertisement of connected prefixes on
GigabitEthernet interface 0/1/0/1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
855
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
tag (IS-IS)
tag (IS-IS)
To associate and advertise a tag with the prefix of an IS-IS interface, use the tag command in interface
address family configuration mode. To restore the default behavior, use the no form of this command.
tag tag
no tag [tag]
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to associate and advertise an interface tag:
spf prefix-priority (IS-IS), on page 851 Assigns a priority to an ISIS prefix for customizing the RIB update
sequence.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
856
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
topology-id
topology-id
To differentiate one topology in the domain from another while configuring a multicast routing table, use the
topology-id command in Intermediate System-to-Intermediate System (IS-IS) address family configuration
submode. To disable the topology use the no form of the command.
topology-id isis-multicast-topology-id-number
no topology-id isis-multicast-topology-id-number
Syntax Description isis-multicast-topology-id-number ID number for a specific IS-IS multicast topology. Range is 6 to 4095.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
isis read,
write
Examples The following example shows how to differentiate a topology from another in the multicast routing
table in IS-IS routing:
address-family multicast topology Used in conjunction with the topology-id command, enables a
(IS-IS), on page 656 multicast topology globally when configuring Intermediate
System-to-Intermediate System (IS-IS) routing.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
857
IS-IS Commands on Cisco ASR 9000 Series RouterCisco IOS XR Software
trace (IS-IS)
trace (IS-IS)
To set the the IS-IS buffer size, use the trace command in router configuration mode. To return to the default
value, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples The following example shows how to set the isis buffer size for severe traces to 1200:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
858
EIGRP Commands
This module describes the commands used to configure and monitor the Enhanced Interior Gateway Routing
Protocol (EIGRP).
For detailed information about EIGRP concepts, configuration tasks, and examples, see Implementing EIGRP
on Cisco ASR 9000 Series Router in Routing Configuration Guide for Cisco ASR 9000 Series Routers.
• address-family (EIGRP), on page 861
• authentication keychain, on page 863
• auto-summary (EIGRP), on page 865
• autonomous-system, on page 867
• bandwidth-percent (EIGRP), on page 869
• bfd fast-detect (EIGRP), on page 870
• bfd minimum-interval (EIGRP), on page 871
• bfd multiplier (EIGRP), on page 873
• clear eigrp neighbors, on page 874
• clear eigrp topology, on page 876
• default-information, on page 878
• default-metric (EIGRP), on page 879
• distance (EIGRP), on page 881
• hello-interval (EIGRP), on page 883
• hold-time (EIGRP), on page 884
• interface (EIGRP), on page 886
• log-neighbor-changes, on page 888
• log-neighbor-warnings, on page 889
• maximum-paths (EIGRP), on page 890
• maximum-prefix (EIGRP), on page 891
• metric (EIGRP), on page 893
• metric maximum-hops, on page 895
• metric rib-scale, on page 896
• metric weights, on page 897
• neighbor (EIGRP), on page 900
• neighbor maximum-prefix, on page 902
• next-hop-self disable, on page 905
• nsf disable (EIGRP), on page 906
• passive-interface (EIGRP), on page 908
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
859
EIGRP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
860
EIGRP Commands
address-family (EIGRP)
address-family (EIGRP)
To enable an IPv4 address family under Enhanced Interior Gateway Routing Protocol (EIGRP), use the
address-family command in the appropriate mode. To remove the address family from the EIGRP
configuration, use the no form of this command.
address-family{ipv4 | ipv6}
no address-family{ipv4 | ipv6}
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the address-family ipv4 command to configure IPv4 address family sessions in EIGRP.
EIGRP Virtual Private Networks (VPNs) can be configured under IPv4 address family configuration modes
after first entering VRF configuration mode. All commands in address family configuration mode can be
configured in VRF address families except the autonomous-system and maximum-prefix commands.
eigrp read,
write
Examples The following example shows how to configure an IPv4 VRF address family session after defining
the VRF named vrf1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
861
EIGRP Commands
address-family (EIGRP)
maximum-prefix (EIGRP) Limits the number of prefixes that are accepted under an address family by
EIGRP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
862
EIGRP Commands
authentication keychain
authentication keychain
To authenticate all EIGRP protocol traffic on one or more interfaces based on the MD5 algorithm, use the
authentication keychain command in an appropriate configuration mode. To disable authentication, use the
no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the address-family ipv4 command to configure IPv4 address family sessions in EIGRP and the
address-family ipv6 command to configure IPv6 address family sessions in EIGRP.
EIGRP Virtual Private Networks (VPNs) can be configured under IPv4 and IPv6 address family configuration
modes after first entering VRF configuration mode.
eigrp read,
write
Examples The following example shows how to enable an EIGRP authentication keychain:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
863
EIGRP Commands
authentication keychain
router eigrp, on page 917 Configures a routing process and enter router configuration mode for Enhanced
Interior Gateway Routing Protocol (EIGRP).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
864
EIGRP Commands
auto-summary (EIGRP)
auto-summary (EIGRP)
To allow automatic summarization of subnet routes into network-level routes for an Enhanced Interior Gateway
Routing Protocol (EIGRP) process, use the auto-summary command in the appropriate configuration mode.
To disable this function and send subprefix routing information across classful network boundaries, use the
no form of this command.
auto-summary
no auto-summary
Command Default The behavior of this command is disabled by default. (The software sends subnet routing information across
classful network boundaries.)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Route summarization reduces the amount of routing information in the routing tables. Use the auto-summary
command to allow the software to create summary subprefixes to the classful network boundary when crossing
classful network boundaries.
EIGRP summary routes are given an administrative distance value of 5. You cannot configure this value.
eigrp read,
write
Examples The following example shows how to enable automatic summarization for EIGRP 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
865
EIGRP Commands
auto-summary (EIGRP)
summary-address (EIGRP), on page 942 Configures a summary aggregate address for a specified interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
866
EIGRP Commands
autonomous-system
autonomous-system
To configure the autonomous-system number for an address-family of Enhanced Interior Gateway Routing
Protocol (EIGRP) routing process, use the autonomous-system command in the address family configuration
mode. To remove the autonomous-system number for an address-family of EIGRP routing process, use the
no form of this command.
autonomous-system as-number
no autonomous-system as-number
Syntax Description as-number Autonomous system number of the EIGRP routing process. Range is from 1 to 65535.
Command Modes IPv4 address family configuration (For EIGRP configured using virtual-name only).
Release 5.1 This command was added in address family configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the autonomous-system command in IPv4 VRF address family configuration mode.
The same VRF-autonomous-system combination cannot be used across multiple process instances.
eigrp read,
write
Examples This example shows how to configure autonomous system 101 under VRF VPN-1:
This example shows how to configure autonomous-system 1 for default/global VRF of EIGRP
configured using virtual-name:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
867
EIGRP Commands
autonomous-system
vrf (EIGRP), on page 947 Defines a VRF instance and to enters VRF configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
868
EIGRP Commands
bandwidth-percent (EIGRP)
bandwidth-percent (EIGRP)
To configure the percentage of bandwidth that may be used by EIGRP on an interface, use the
bandwidth-percent command in interface configuration mode. To restore the default value, use the no
form of this command.
bandwidth-percent percent
no bandwidth-percent
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
EIGRP uses up to 50 percent of the bandwidth of a link, as defined by the bandwidth interface configuration
command. This command may be used if some other fraction of the bandwidth is desired. Values greater than
100 percent may be configured. The configuration option may be useful if the bandwidth is set artificially
low for other reasons.
eigrp read,
write
Examples The following example shows how to configure EIGRP to use up to 75 percent (42 kbps) of an
interface in autonomous system 209:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
869
EIGRP Commands
bfd fast-detect (EIGRP)
bfd fast-detect
no bfd fast-detect
Command Default BFD detection of failures in the path between adjacent forwarding engines is disabled.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to configure BFD on a EIGRP router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router eigrp 100
RP/0/RSP0/CPU0:router(config-eigrp)# address-family ipv4
RP/0/RSP0/CPU0:router(config-eigrp-af)# interface gigabitEthernet 2/2/2/1
RP/0/RSP0/CPU0:router(config-eigrp-af-if)# bfd fast-detect
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
870
EIGRP Commands
bfd minimum-interval (EIGRP)
Syntax Description milliseconds Interval between sending BFD hello packets to the neighbor. The range is 15 to 30000
milliseconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to configure BFD minimum interval on a EIGRP router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router eigrp 100
RP/0/RSP0/CPU0:router(config-eigrp)# address-family ipv4
RP/0/RSP0/CPU0:router(config-eigrp-af)# interface gigabitEthernet 2/2/2/1
RP/0/RSP0/CPU0:router(config-eigrp-af-if)# bfd minimum-interval 50
bfd minimum-interval, on page 593 Specifies the minimum control packet interval for BFD sessions
for the corresponding BFD configuration scope.
bfd multiplier, on page 600 Sets the BFD multiplier.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
871
EIGRP Commands
bfd minimum-interval (EIGRP)
Command Description
show bfd, on page 625 Displays BFD information for a specific location.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
872
EIGRP Commands
bfd multiplier (EIGRP)
Syntax Description multiplier Number of times a packet is missed before BFD declares the neighbor down. The range is 2 to
50.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to configure BFD minimum interval on a EIGRP router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router eigrp 100
RP/0/RSP0/CPU0:router(config-eigrp)# address-family ipv4
RP/0/RSP0/CPU0:router(config-eigrp-af)# interface gigabitEthernet 2/2/2/1
RP/0/RSP0/CPU0:router(config-eigrp-af-if)# bfd multiplier 5
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
873
EIGRP Commands
clear eigrp neighbors
clear eigrp [as-number] [vrf {vrfall}] [{ipv4 | ipv6}] neighbors [{ip-addresstype interface-path-id}]
[soft]
Syntax Description as-number (Optional) Autonomous system number. Range is from 1 to 65535.
vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or all VRF
instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
Command Default When no autonomous system number or VRF instance is specified, all EIGRP neighbor entries are cleared
from the table.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
874
EIGRP Commands
clear eigrp neighbors
Examples The following example shows how to clear all EIGRP VRF entries for neighbor Gigabit Ethernet
interface 0/5/0/0:
show eigrp interfaces, on page 922 Displays information about interfaces configured for EIGRP.
show eigrp neighbors, on page 926 Displays the neighbors discovered by EIGRP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
875
EIGRP Commands
clear eigrp topology
clear eigrp [as-number] [vrf {vrfall}] [{ipv4 | ipv6}] topology [{prefix mask prefixl/ength}]
Syntax Description as-number (Optional) Autonomous system number. Range is from 1 to 65535.
vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or all VRF
instances.
/ length Prefix length, which can be indicated as a slash (/) and number. For example, /8 indicates
that the first eight bits in the IP prefix are network bits. If length is used, the slash is
required.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to clear EIGRP topology entries for a specific route:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
876
EIGRP Commands
clear eigrp topology
show eigrp topology, on page 929 Displays information for the EIGRP topology table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
877
EIGRP Commands
default-information
default-information
To control the candidate default routing information for an Enhanced Interior Gateway Routing Protocol
(EIGRP), use the defaultinformation command in the appropriate configuration mode. To suppress EIGRP
candidate default information in incoming or outgoing updates, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to configure inbound default routes specified with route policy
acme to be accepted by an EIGRP peer in autonomous system 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
878
EIGRP Commands
default-metric (EIGRP)
default-metric (EIGRP)
To set metrics for an Enhanced Interior Gateway Routing Protocol (EIGRP), use the defaultmetric command
in the appropriate configuration mode. To remove the metric values and restore the default state, use the no
form of this command.
Syntax Description bandwidth Minimum bandwidth of the route in kilobits per second. Range is 1 to 4294967295.
reliability Likelihood of successful packet transmission expressed as a number between 0 and 255. The
value 255 means 100-percent reliability; 0 means the link is not reliable.
loading Effective bandwidth of the route expressed as a number from 1 to 255 (255 is 100-percent
loading).
mtu Minimum maximum transmission unit (MTU) size of the route in bytes. Range is from 1 to
65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-metric command to provide default metric values while redistributing a protocol into EIGRP.
Metric defaults have been carefully set to work for a wide variety of networks. Take great care when changing
these values.
eigrp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
879
EIGRP Commands
default-metric (EIGRP)
Examples The following example shows how to take redistributed Routing Information Protocol (RIP) metrics
and translate them into EIGRP metrics with values as follows: bandwidth = 1000, delay = 100,
reliability = 250, loading = 100, and MTU = 1500.
redistribute Redistributes routes from one routing domain into another routing domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
880
EIGRP Commands
distance (EIGRP)
distance (EIGRP)
To allow the use of one of two administrative distances—internal and external—that could provide a better
route to a node, use the distance command in the appropriate configuration mode. To reset these values to
their defaults, use the no form of this command.
Syntax Description internal-distance Administrative distance for EIGRP internal routes. Internal routes are those that are learned
from another entity within the same autonomous system (AS). The distance can be a value
from 1 to 255.
external-distance Administrative distance for EIGRP external routes. External routes are those for which
the best path is learned from a source external to the AS. The distance can be a value from
1 to 255.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An administrative distance is a rating of the trustworthiness of a routing information source, such as an
individual router or a group of routers. Numerically, an administrative distance is an integer from 0 to 255.
In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing
information source cannot be trusted at all and should be ignored.
Use the distance command if another protocol is known to provide a better route to a node than was actually
learned through the external Enhanced Interior Gateway Routing Protocol (EIGRP) or some internal routes
should be preferred by EIGRP.
To display the default administrative distance for a specified routing process, use the show protocols EXEC
command.
eigrp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
881
EIGRP Commands
distance (EIGRP)
Examples The following example shows how to set the administrative distance of all EIGRP 1 internal routes
(within vrf vpn-1) to 80 and all EIGRP external routes to 130:
show protocols (EIGRP), on page 934 Displays information about the Enhanced Interior Gateway Routing
Protocol (EIGRP) running on the router.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
882
EIGRP Commands
hello-interval (EIGRP)
hello-interval (EIGRP)
To configure the hello interval for an interface, use the hello-interval command in interface configuration
mode. To restore the default value, use the no form of this command.
hello-interval seconds
no hello-interval
Syntax Description seconds Hello interval (in seconds). Range is from 1 to 65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to set the hello interval to 10 seconds for the interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
883
EIGRP Commands
hold-time (EIGRP)
hold-time (EIGRP)
To configure the hold time for an interface, use the hold-time command in interface configuration mode.
To restore the default value, use the no form of this command.
hold-time seconds
no hold-time
Syntax Description seconds Hold time (in seconds). Range is from 1 to 65535.
Command Default Three times the default hello interval time of 15 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
On very congested and large networks, the default hold time might not be sufficient time for all routers to
receive hello packets from their neighbors. In this case, you may want to increase the hold time.
We recommend that the hold time be at least three times the hello interval. If a router does not receive a hello
packet within the specified hold time, routes through this router are considered unavailable.
Increasing the hold time delays route convergence across the network.
To ensure nonstop forwarding during RP failovers, we recommend that the hold time be increased to 30
seconds.
eigrp read,
write
Examples The following example shows how to set the hold time to 0 to 40 seconds for the interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
884
EIGRP Commands
hold-time (EIGRP)
hello-interval (EIGRP), on page 883 Configures the hello interval for the EIGRP routing process designated
by an autonomous system number.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
885
EIGRP Commands
interface (EIGRP)
interface (EIGRP)
To define the interfaces on which the Enhanced Interior Gateway Routing Protocol (EIGRP) routing protocol
runs, use the interface command in the appropriate configuration mode. To disable EIGRP routing for
interfaces, use the no form of this command.
Syntax Description type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Command Default When you do not specify this command in configuration mode, EIGRP routing for interfaces is not enabled.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the interface command to associate a specific interface with an EIGRP process. The interface remains
associated with the process even when the IPv4 address of the interface changes.
This command places the router in interface configuration mode, from which you can configure
interface-specific settings. Commands configured under this mode (such as the hello-interval command)
are automatically bound to that interface.
eigrp read,
write
Examples The following example shows how to enter interface configuration mode for EIGRP process 1 and
set the hello interval to 10 seconds for GigabitEthernet interface 0/1/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
886
EIGRP Commands
interface (EIGRP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
887
EIGRP Commands
log-neighbor-changes
log-neighbor-changes
To enable the logging of changes in Enhanced Interior Gateway Routing Protocol (EIGRP) neighbor
adjacencies, use the log-neighbor-changes command in the appropriate configuration mode. To disable the
logging of changes in EIGRP neighbor adjacencies, use the no form of this command.
log-neighbor-changes
no log-neighbor-changes
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the log-neighbor-changes command to log neighbor adjacency changes, monitor the stability of the
routing system, and help detect problems. Logging is disabled by default. To disable the logging of neighbor
adjacency changes, use the no form of this command.
eigrp read,
write
Examples The following example shows how to enable logging of neighbor changes for EIGRP 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
888
EIGRP Commands
log-neighbor-warnings
log-neighbor-warnings
To enable the logging of Enhanced Interior Gateway Routing Protocol (EIGRP) neighbor warning messages,
use the log-neighbor-warnings command in the appropriate configuration mode. To disable the logging of
EIGRP neighbor warning messages, use the no form of this command.
log-neighbor-warnings
no log-neighbor-warnings
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the log-neighbor-warnings command to disable and enable neighbor warning messages. When neighbor
warning messages occur, they are not logged by default.
eigrp read,
write
Examples The following example shows how to configure log neighbor warning messages for EIGRP process
20:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
889
EIGRP Commands
maximum-paths (EIGRP)
maximum-paths (EIGRP)
To control the maximum number of parallel routes that the Enhanced Interior Gateway Routing Protocol
(EIGRP) can support, use the maximum-paths command in the appropriate configuration mode. To remove
the maximum-paths command from the configuration file and restore the system to its default condition
with respect to the routing protocol, use the no form of this command.
maximum-paths maximum
no maximum-paths
Syntax Description maximum Maximum number of parallel routes that EIGRP can install in a routing table. Range is from 1
to 32 routes .
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum-paths command to allow the EIGRP protocol to install multiple paths into the routing
table for each prefix. Multiple paths are installed for both internal and external routes, providing these routes
are learned in the same autonomous system and that they are equal cost (according to the EIGRP best path
algorithm).
eigrp read,
write
Examples The following example shows how to allow a maximum of 10 paths to a destination:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
890
EIGRP Commands
maximum-prefix (EIGRP)
maximum-prefix (EIGRP)
To limit the number of prefixes that are accepted under a VRF address family by Enhanced Interior Gateway
Routing Protocol (EIGRP), use the maximum-prefix command in IPv4 VRF address family configuration
mode. To disable this function, use the no form of this command.
Syntax Description maximum Maximum number of prefixes allowed under an address family. Range is from 1 to
4294967295.
The number of prefixes that can be configured is limited only by the available system
resources on the router.
threshold (Optional) Syslog warning messages are specified as a percentage of the maximum
prefix limit that was exceeded. The prefix percentage number range is from 1 to 100.
The default is 75 percent.
dampened (Optional) A decay penalty is applied to the restart time period each time the maximum
prefix limit is exceeded. The half-life for the decay penalty is 150 percent of the
default or user-defined restart time value in minutes. This keyword is disabled by
default.
reset-time minutes (Optional) The restart count is reset to 0 after the default or user-defined reset time
period has expired. The range of values that can be applied with the minutes argument
is from 1 to 65535 minutes. The default reset-time period is 15 minutes.
restart minutes (Optional) A time period when router adjacencies are not formed or when redistributed
routes are not accepted from the RIB after the maximum prefix limit has been
exceeded. The value for the minutes argument is from 1 to 65535 minutes. The default
restart time period is 5 minutes.
restart-count (Optional) Number of times a peering session is automatically reestablished after the
number peering session is torn down or after the redistribute route is cleared and relearned
when the maximum prefix exceeds limits. The default restart count limit is 3.
Caution After the restart count threshold is crossed, you need to use the clear
eigrp neighbors command to re-establish normal peering, redistribution,
or both.
warning-only (Optional) Configures the router to generate syslog messages only when the maximum
prefix limit is reached, instead of terminating the peering session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
891
EIGRP Commands
maximum-prefix (EIGRP)
restart : 5 minutes
restart-count : 3
warning-only : False
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum-prefix command to limit the number of prefixes that are accepted from all sources. When
the maximum prefix limit is exceeded, sessions with remote peers are torn down, all routes learned from
remote peers and through redistribution are removed from the topology and routing tables, and redistribution
and peering are suspended for the default or user-defined time period.
eigrp read,
write
Examples The following example shows how to configure the maximum prefix limit for an EIGRP process,
which includes routes learned through redistribution and routes learned through EIGRP peering
sessions. The maximum limit is set to 50,000 prefixes. When the number of prefixes learned through
redistribution reaches 37,500 (75 percent of 50,000), warning messages are displayed in the console.
When the maximum prefix limit is exceeded, all peering sessions are reset, the topology and routing
tables are cleared and redistributed routes and all peering sessions are placed in a penalty state.
clear eigrp neighbors, on page 874 Deletes EIGRP VPN neighbor entries from the table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
892
EIGRP Commands
metric (EIGRP)
metric (EIGRP)
To set metrics for an Enhanced Interior Gateway Routing Protocol (EIGRP) interface, use the metric command
in interface configuration mode. To remove the metric values and restore the default state, use the no form
of this command.
Syntax Description bandwidth Minimum interface bandwidth of the route in kilobits per second. Range is 1 to 4294967295.
delay Interface route delay in tens of microseconds. Delay is 1 or any positive number that is a
multiple of 39.1 nanoseconds. Range is 1 to 4294967295.
Use the picoseconds keyword to specify interface route delay in picoseconds.
• If picoseconds is not used , the interface route delay in tens of microsecond (default).
Range is 1 to 4294967295
• If picoseconds is used, interface route delay in picoseconds. Range is 1 to 4294967295
reliability Likelihood of successful packet transmission expressed as a number between 0 and 255. The
value 255 means 100-percent reliability; 0 means no reliability.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the metric command to provide metric values while redistributing a protocol into an EIGRP interface.
Metric defaults have been carefully set to work for a wide variety of networks. Take great care when changing
these values.
The picoseconds keyword is supported only in 64 bit mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
893
EIGRP Commands
metric (EIGRP)
This example shows how to configure metric values for interface POS 0/1/0/1 with values as bandwidth
= 100, delay = 7, reliability = 250, and load = 100.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router eigrp 100
RP/0/RSP0/CPU0:router(config-eigrp)# address-family ipv4
RP/0/RSP0/CPU0:router(config-eigrp-af)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-eigrp-af-if)# metric bandwidth 100 delay 7 reliability 250
load 100
This example shows how to set the delay of interface GigabitEthernet0/0/0/0 to 100 picoseconds:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router eigrp 1
RP/0/RSP0/CPU0:router(config-eigrp)#address-family ipv6
RP/0/RSP0/CPU0:router(config-eigrp-af-if)#metric delay 100 picoseconds
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
894
EIGRP Commands
metric maximum-hops
metric maximum-hops
To advertise as unreachable those Enhanced Interior Gateway Routing Protocol (EIGRP) routes with a hop
count higher than is specified by the command, use the metric maximum-hops command in the appropriate
configuration mode. To reset the value to the default, use the no form of this command.
Syntax Description hops-number Maximum hop count. Range is from 1 to 255 hops.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the metric maximum-hops command to provide a safety mechanism that breaks any potential
count-to-infinity problems. This command causes the EIGRP routing protocol to advertise as unreachable
routes with a hop count greater than the value assigned to the hops-number argument.
eigrp read,
write
Examples The following example shows how to configure a hop count to 200 for a router that has a complex
WAN generating a large hop count under normal (nonlooping) operations.
metric weights, on page 897 Allows the tuning of the EIGRP metric calculations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
895
EIGRP Commands
metric rib-scale
metric rib-scale
To set a RIB scale for EIGRP, use the metric rib-scale command in an appropriate configuration mode. To
remove the RIB scale and restore the default state, use the no form of this command.
Syntax Description scale-down-value Amount to divide the EIGRP Wide Metric by to convert to a 4 Byte RIB metric. Legal
ranges are 1-256. Results are expressed as whole integers only (no rounding).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The ability to scale the RIB metric is provided through the use of the metric rib-scale configuration command.
When entered, the command will result in all routes in the RIB being cleared and replaced with the new metric
values.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router eigrp 1
RP/0/RSP0/CPU0:router(config-eigrp)#address-family ipv4
RP/0/RSP0/CPU0:router(config-eigrp-af)#metric rib-scale 64
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
896
EIGRP Commands
metric weights
metric weights
To allow the tuning of the Enhanced Interior Gateway Routing Protocol (EIGRP) metric calculations, use the
metric weights command in the appropriate configuration mode. To reset the values to their defaults, use
the no form of this command.
k1 k2 k3 k4 Constants that convert an EIGRP metric vector into a scalar quantity. The range is 0 to
k5k6 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the metric weights command to alter the default behavior of EIGRP routing and metric computation
and allow the tuning of the EIGRP metric calculation for a particular ToS.
If k5 equals 0, the composite EIGRP metric is computed according to the following formula:
metric = [k1 * bandwidth + (k2 * bandwidth)/(256 – load) + k3 * delay]
If k5 does not equal zero, an additional operation is performed:
metric = metric * [k5/(reliability + k4)]
Bandwidth is inverse minimum bandwidth of the path in BPS scaled by a factor of 2.56 * 1012. The range is
from a 1200-bps line to 10 terabits per second.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
897
EIGRP Commands
metric weights
Delay is in units of 10 microseconds. The range of delay is from 10 microseconds to 168 seconds. A delay
of all 1s indicates that the network is unreachable.
The delay parameter is stored in a 32-bit field, in increments of 39.1 nanoseconds. The range of delay is from
1 (39.1 nanoseconds) to hexadecimal FFFFFFFF (decimal 4,294,967,040 nanoseconds). A delay of all 1s
(that is, a delay of hexadecimal FFFFFFFF) indicates that the network is unreachable.
This table lists the default values used for several common media.
This command is supported only in 64 bit mode. The constraint k6 does not have effect in 64 bit mode.
Reliability is given as a fraction of 255. That is, 255 is a reliability of 100 percent or a perfectly stable link.
Load is given as a fraction of 255. A load of 255 indicates a completely saturated link.
eigrp read,
write
Examples The following example shows how to set the metric weights to change the default values:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
898
EIGRP Commands
metric weights
metric maximum-hops, on page 895 Advertises as unreachable those EIGRP VPN routes with a hop count
higher than is specified by the command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
899
EIGRP Commands
neighbor (EIGRP)
neighbor (EIGRP)
To define a neighboring router with which to exchange Enhanced Interior Gateway Routing Protocol (EIGRP)
information, use the neighbor command in interface configuration mode. To remove an entry, use the no
form of this command.
Syntax Description ip-address IP address of a peer router with which routing information is exchanged.
max-hops The maximum number of hops within which the neighbor is expected to be reachable from the
configured router. The default value is 100 hops.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the neighbor command to permit the point-to-point (nonbroadcast) exchange of routing information.
If a neighbor is configured on an interface using the neighbor command, the interface stops sending or
receiving multicast hello messages. However, the interface can send or receive unicast hello messages. So
each neighbor on a LAN must be configured individually .Multiple neighbor commands can be used to
specify additional neighbors or peers.
eigrp read,
write
Examples This example shows how to permit the sending of EIGRP updates to specific neighbors. One copy
of the update is generated for each neighbor:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
900
EIGRP Commands
neighbor (EIGRP)
passive-interface (EIGRP), on page 908 Disables sending and receiving "hello" messages on (EIGRP)
interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
901
EIGRP Commands
neighbor maximum-prefix
neighbor maximum-prefix
To limit the number of prefixes that are accepted from a single Enhanced Interior Gateway Routing Protocol
(EIGRP) neighbor or all EIGRP VPN neighbors, use the neighbor maximum-prefix command in IPv4 VRF
address family configuration mode. To disable this function, use the no form of this command.
threshold (Optional) Syslog warning messages are specified as a percentage of the maximum
prefix limit that was exceeded. The prefix percentage number range is from 1 to
100. The default is 75 percent.
dampened (Optional) Configures a decay penalty to be applied to the restart time period each
time the maximum prefix limit is exceeded. The half-life for the decay penalty is
150 percent of the default or user-defined restart time value in minutes. This keyword
is disabled by default.
reset-time minutes (Optional) Configures the router to reset the restart count to 0 after the default or
configured reset time period has expired. The range is from 1 to 65535 minutes.
restart minutes (Optional) Configures a time period in which the router does not form adjacencies
or accept redistributed routes from the RIB after the maximum prefix limit has been
exceeded. The range is from 1 to 65535 minutes.
restart-count number (Optional) Configures the number of times a peering session can be automatically
reestablished after the peering session has been torn down or a redistribute route
has been cleared and relearned because the maximum prefix limit has been exceeded.
Caution After the restart count threshold is crossed, you need to use the clear
eigrp neighbors command to reestablish normal peering, redistribution,
or both.
warning-only (Optional) Configures the router to generate syslog messages only when the
maximum prefix limit is reached, instead of terminating the peering session.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
902
EIGRP Commands
neighbor maximum-prefix
dampened : disabled
warning-only : disabled
reset-time : 15 minutes
restart : 5 minutes
restart-count : 3
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The neighbor maximum-prefixcommand is configured to protect an individual peering session or all peering
sessions. When this feature is enabled and the maximum prefix limit is exceeded, the router tears down the
peering session, clears all routes that are learned from the peer, and then places the peer in a penalty state for
the default or user-defined time period. After the penalty time period expires, normal peering is reestablished.
Note In EIGRP, neighbor commands have been used traditionally to configure static neighbors. In the context of
this feature, however, the neighbor maximum-prefix command can be used to configure the maximum prefix
limit for both statically configured and dynamically discovered neighbors.
When configuring the neighbor maximum-prefix command to protect a single peering session, just the
maximum prefix limit, percentage threshold, and warning only configuration options can be configured.
Session dampening, restart, and reset timers are configured on a global basis.
eigrp read,
write
Examples The following example shows how to configure the maximum prefix limit for a single peer. The
maximum limit is set to 1000 prefixes, and the warning threshold is set to 80 percent. When the
maximum prefix limit is exceeded, the session with this peer is torn down, all routes learned from
this peer are removed from the topology and routing tables, and this peer is placed in a penalty state
for 5 minutes (default penalty value).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
903
EIGRP Commands
neighbor maximum-prefix
The following example shows how to configure the maximum prefix limit for all peers. The maximum
limit is set to 10,000 prefixes, the warning threshold is set to 90 percent, the restart timer is set to 4
minutes, a decay penalty is configured for the restart timer with the dampened keyword, and all
timers are configured to be reset to 0 every 60 minutes. When the maximum prefix limit is exceeded,
all peering sessions are torn down, all routes learned from all peers are removed from the topology
and routing tables, and all peers are placed in a penalty state for 4 minutes (user-defined penalty
value). A dampening exponential decay penalty is also applied.
clear eigrp neighbors, on page 874 Deletes EIGRP and VRF neighbor entries from the appropriate tables.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
904
EIGRP Commands
next-hop-self disable
next-hop-self disable
To instruct the Enhanced Interior Gateway Routing Protocol (EIGRP) process to use the received next-hop
value when advertising the routes, use the next-hop-self disablecommand in interface configuration mode.
To revert to the default, use the no form of this command.
next-hop-self disable
no next-hop-self disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
EIGRP, by default, sets the IP next-hop value to be itself for routes that it is advertising, even when advertising
those routes on the same interface from which learned them. To change this default, you must use the
next-hop-self disable interface configuration command to instruct EIGRP to use the received next-hop value
when advertising these routes.
The next-hop-self disable feature is not available for redistributed routes.
eigrp read,
write
Examples The following example shows how to change the default IP next-hop value and instruct EIGRP to
use the received next-hop value:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
905
EIGRP Commands
nsf disable (EIGRP)
nsf disable
no nsf disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If NSF is to be disabled for both IPv4 and IPv6 address families of all VRFs, use the nsf disable command
at router configuration mode.
If NSF is to be disabled for a specific address family under a specific VRF, use the nsf disable command at
address family configuration mode.
If NSF is disabled, EIGRP will not be able to retain the routes learnt from its peers and may result in traffic
loss during ISSU.
This example shows how to disable NSF for all address families under all VRF's:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router eigrp 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
906
EIGRP Commands
nsf disable (EIGRP)
RP/0/RSP0/CPU0:router(config-eigrp)#nsf disable
This example shows how to disable NSF for IPv4 address family of VRF v1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router eigrp 1
RP/0/RSP0/CPU0:router(config-eigrp)#vrf v1
RP/0/RSP0/CPU0:router(config-eigrp-vrf)#address-family ipv4
RP/0/RSP0/CPU0:router(config-eigrp-vrf-af)#nsf disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
907
EIGRP Commands
passive-interface (EIGRP)
passive-interface (EIGRP)
To disable sending and receiving "hello" messages on an Enhanced Interior Gateway Routing Protocol (EIGRP)
interface and to disable formation of neighbors on the interface, use the passive-interface command in
interface configuration mode. To reenable sending and receiving "hello messages", use the no form of this
command.
passive-interface
no passive-interface
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the passive-interface command to disable sending of "hello" massages. The particular subnet on that
interface will continue to be advertised by EIGRP to neighbors on other interfaces.
eigrp read,
write
Examples This example shows how to configure passive-interface command on GigabitEthernet interface
0/6/5/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
908
EIGRP Commands
redistribute (EIGRP)
redistribute (EIGRP)
To inject routes from one routing domain into the Enhanced Interior Gateway Routing Protocol (EIGRP), use
the redistribute command in the appropriate configuration mode. To remove the redistribute command
from the configuration file and restore the system to its default condition in which the software does not
redistribute routes, use the no form of this command.
connected Distributes routes that are established automatically by virtue of having enabled IP
on an interface.
ospf Distributes routes from the OSPF protocol. This protocol is supported in the IPv4
address family.
route-policy name (Optional) Specifies the identifier of a configured policy. A policy is used to filter
the importation of routes from this source routing protocol to EIGRP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
909
EIGRP Commands
redistribute (EIGRP)
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Redistributed routing information should always be filtered by the route- policy name keyword and
argument. This filtering ensures that only those routes intended by the administrator are redistributed by
EIGRP.
A default metric is usually required to redistribute routes from another protocol into EIGRP. The metric is
configured through the default-metric command or under the route policy configured with the redistribute
command. The two exceptions to this requirement are when EIGRP redistributes BGP routes on a provider
edge (PE) router in an MPLS-VPN scenario and when EIGRP redistributes EIGRP routes from another
autonomous-system number. In case of MPLS-VPN scenario, if the originating protocol of the route is EIGRP
with the same autonomous-system, the metric would be learned automatically from the extended communities
of the BGP route. In case of redistribution from EIGRP belonging to different autonomous-system, the metric
would be learned automatically from the extended communities from RIB.
For information about routing policies, see the Routing Policy Commands on Cisco ASR 9000 Series Router
module of the Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference.
eigrp read,
write
Examples This example shows how to cause BGP routes to be redistributed into an EIGRP autonomous system:
This example shows how to redistribute the specified IS-IS process routes into an EIGRP autonomous
system within a VPN routing and forwarding instance (VRF). The IS-IS routes are redistributed
using route policy 3.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
910
EIGRP Commands
redistribute (EIGRP)
This example shows how to cause EIGRP routes from autonomous-system 100 to be redistributed
into EIGRP autonomous-system 1.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
911
EIGRP Commands
redistribute maximum-prefix
redistribute maximum-prefix
To limit the number of prefixes redistributed into an Enhanced Interior Gateway Routing Protocol (EIGRP)
process, use the redistribute maximum-prefix command in IPv4 VRF address family configuration mode.
To disable this function, use the no form of this command.
Syntax Description maximum Maximum number of prefixes that are redistributed into EIGRP under an
address-family. The range is from 1 to 4294967295.
The number of prefixes that can be configured is limited only by the available system
resources on the router.
threshold (Optional) Syslog warning messages are specified as a percentage of the maximum
prefix limit that was exceeded. The prefix percentage number range is from 1 to 100.
The default is 75 percent.
restart minutes (Optional) Configures a time period in which the router will not form adjacencies or
accept redistributed routes from the RIB after the maximum-prefix limit has been
exceeded. The value for the minutes argument is from 1 to 65535 minutes.
restart-count (Optional) Configures the number of times a peering session can be automatically
number reestablished after the peering session has been torn down or after the redistribute
route has been cleared and relearned because the maximum prefix limit has been
exceeded.
After the restart count threshold has been crossed, you will need to enter the process
restart eigrp command to reestablish normal peering, redistribution, or both.
reset-time minutes (Optional) Configures the router to reset the restart count to 0 after the default or
configured reset time period has expired. The value for the minutes argument is from
1 to 65535 minutes.
dampened (Optional) Configures a decay penalty to be applied to the restart time period each
time the maximum prefix limit is exceeded. The half-life for the decay penalty is 150
percent of the default or user-defined restart time value in minutes.
warning-only (Optional) Configures the router to only generate syslog messages when the maximum
prefix limit is reached, instead of suspending redistribution.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
912
EIGRP Commands
redistribute maximum-prefix
dampened: disabled
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the redistribute maximum-prefix command to configure limit prefixes learned through redistribution.
When the maximum prefix limit is exceeded, all routes learned from the Routing Information Base (RIB) are
discarded and redistribution is suspended for the default or user-defined time period. The maximum prefix
limit that can be configured for redistributed prefixes is limited only by the available system resources on the
router.
eigrp read,
write
Examples The following example shows how to configure the maximum prefix limit for routes learned through
redistribution. The maximum limit is set to 5000 prefixes, and the warning threshold is set to 95
percent. When the number of prefixes learned through redistribution reaches 4750 (95 percent of
5000), warning messages are displayed in the console. Because the warning-only keyword is
configured, the topology and routing tables are not cleared and route redistribution is not placed in
a penalty state.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
913
EIGRP Commands
remote-neighbor (unicast)
remote-neighbor (unicast)
To configure any neighbor that is multiple hops away, including remote static neighbors, use the
remote-neighbor command.
Syntax Description unicast-listen Use unicast to form remote neighbor relationship without having to
manually configure the remote neighbors addresses.
allow-listroute policy name Name of the route-policy that specifies remote addresses from which
EIGRP neighbor connections may be accepted.
max-neighborsmaximum remote The maximum number of remote neighbors from which connection can
peers be accepted. The range is 1-65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the remote-neighbor unicast-listen command to configure a neighbor to use unicast to communicate
with a neighbor that is multiple hops away, and whose address has not been configured with the neighbor
command. A single unicast address can only be configured to a single remote static neighbor for a given
address-family. If you try to configure a second remote static neighbor using the same unicast address but a
different interface, it is rejected. EIGRP configuration of remote neighbors under different address families
is unrestricted.
Example
This example shows you how to configure both devices (hub and spoke) involved in the neighbor
relationship.
RP/0/RSP0/CPU0:HUB(config)#router eigrp 100
RP/0/RSP0/CPU0:HUB(config-eigrp)#address-family ipv4
RP/0/RSP0/CPU0:HUB(config-eigrp-af)#int g0/0/0/3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
914
EIGRP Commands
remote-neighbor (unicast)
RP/0/RSP0/CPU0:HUB(config-eigrp-af-if)#exit
RP/0/RSP0/CPU0:HUB(config-eigrp-af)#interface gigabitEthernet 0/0/0/3
RP/0/RSP0/CPU0:HUB(config-eigrp-af-if)#remote-neighbor unicast-listen
RP/0/RSP0/CPU0:HUB(config-eigrp-af-if)#commit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
915
EIGRP Commands
route-policy (EIGRP)
route-policy (EIGRP)
To apply a routing policy to updates advertised to or received from an Enhanced Interior Gateway Routing
Protocol (EIGRP) neighbor, use the route-policy command in the appropriate configuration mode. To disable
applying routing policy to updates, use the no form of this command.
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-policy command to specify a routing policy for an inbound or outbound route. The policy can
be used to filter routes or modify route attributes.
eigrp read,
write
Examples The following example shows how to apply the IN-Ipv4 policy to inbound IP Version 4 (IPv4) routes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
916
EIGRP Commands
router eigrp
router eigrp
To configure a routing process and enter router configuration mode for Enhanced Interior Gateway Routing
Protocol (EIGRP), use the router eigrp command in global configuration mode. To turn off the EIGRP
routing process, use the no form of this command.
Syntax Description instance-autonomous-system-number EIGRP instance autonomous-system number. This is used as the
autonomous-system number for the default/global VRF. Valid range
is 1 to 65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
• An explicit autonomous-system configuration is required for the default/global VRF when EIGRP is
configured using virtual instance-name.
• Up to 4 EIGRP instances can be configured.
•
eigrp read,
write
Examples The following example configures EIGRP routing process 109 (109 is the autonomous-system number
of default/global VRF):
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
917
EIGRP Commands
router eigrp
This example configures an EIGRP routing process and assigns it the name "name":
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
918
EIGRP Commands
router-id (EIGRP)
router-id (EIGRP)
To configure a router ID for an Enhanced Interior Gateway Routing Protocol (EIGRP) process, use the
router-id command in the appropriate configuration mode. To cause the software to use the default method
of determining the router ID, use the no form of this command.
router-id router-id
no router-id
Syntax Description router-id 32-bit router ID value specified in four-part, dotted-decimal notation.
Command Default If this command is not configured, EIGRP chooses an IPv4 address as the router ID from one of its interfaces.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
It is good practice to use the router-id command to explicitly specify a unique 32-bit numeric value for the
router ID. This action ensures that EIGRP can function regardless of the interface address configuration.
eigrp read,
write
Examples The following example shows how to assign the IP address of 172.20.1.1 to the EIGRP process 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
919
EIGRP Commands
show eigrp accounting
Syntax Description as-number (Optional) Autonomous system number. This option is available when a VPN
routing and forwarding (VRF) instance is not specified. Range is from 1 to 65535.
vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or
all VRF instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
EIGRP read
Examples The following is sample output from the show eigrp accounting command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
920
EIGRP Commands
show eigrp accounting
Note Connected and summary routes are not listed individually in the output of this command but are
counted in the total aggregate count for each process.
Field Description
EIGRP accounting for AS Identifies the EIGRP instance along with the AS number, router ID and table
ID.
Total Prefix Count Shows the aggregate sum of the prefixes in an EIGRP instance topology table.
The count includes prefixes learned from all neighbors or from redistribution.
States: A-Adjacency, A-Adjacency: Indicates a stable adjacency with the neighbor or a normal
P-Pending, D-Down redistribution state.
P-Pending: Neighbor adjacency or redistribution is suspended or in a penalized
state because the maximum prefix limit was exceeded.
D-Down: Neighbor adjacency or redistribution is suspended permanently until
a manual reset is performed with the clear route command.
Restart Count Number of times a route source exceeded the maximum prefix limit.
Restart Reset(s) Displays the time, in seconds, that a route source is in a P (penalized) state. If
the route source is in an A (stable or normal) state, the displayed time, in
seconds, is the time period until penalization history is reset.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
921
EIGRP Commands
show eigrp interfaces
show eigrp [as-number] [vrf{vrf-name | all}] [{ipv4 | ipv6}] interfaces [type interface-path-id] [detail]
Syntax Description as-number (Optional) Autonomous system number. This option is available when a VPN routing
and forwarding (VRF) instance is not specified.
Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or all
VRF instances.
type (Optional) Interface type. For more information, use the question mark ( ? ) online
help function.
Release 3.9.0 As plain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.3.0 The command output was modified to display relevant wide metric information.
Release 5.2.0 The command output was modified to display BFD information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
922
EIGRP Commands
show eigrp interfaces
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show eigrp interfaces command to determine on which interfaces EIGRP is active and learn
information about EIGRP related to those interfaces.
If an interface is specified, only that interface is displayed. Otherwise, all interfaces on which EIGRP is running
are displayed.
If an autonomous system is specified, only the routing process for the specified autonomous system is displayed.
Otherwise, all EIGRP processes are displayed.
EIGRP read
Examples The following is sample output from the show eigrp interfaces command:
Field Description
Xmit Queue Un/Reliable Number of packets remaining in the unreliable and reliable transmit queues.
Mean SRTT Mean smoothed round-trip time (SRTT) internal (in milliseconds).
Pacing Time Un/Reliable Pacing time used to determine when EIGRP packets should be sent out the interface
(unreliable and reliable packets).
Multicast Flow Timer Maximum number of seconds in which the router sends multicast EIGRP packets.
Pending Routes Number of routes in the packets in the transmit queue waiting to be sent.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
923
EIGRP Commands
show eigrp interfaces
The following is sample output from the show eigrp interfaces command when issued with the
detail keyword:
Field Description
hold time Hold time announced to neighbors. If neighbors do not get hello
packets from the router for this period, neighbors declare that the
neighbor relationship is down.
Un/reliable mcasts Number of unreliable and reliable multicast packets sent on this
interface.
Un/reliable ucasts Number or unreliable and reliable unicast packets sent on this
interface.
CR packets Number of packets sent with the conditional receive bit set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
924
EIGRP Commands
show eigrp interfaces
Field Description
Packets dropped due to wrong keychain Number of packets dropped due to wrong keychain configuration.
config
Packets dropped due to missing Number of packets dropped due to missing authentication.
authentication
Packets dropped due to invalid Number of packets dropped due to invalid authentication.
authentication
This is sample show eigrp interfaces command output to display relevant wide metric information:
show eigrp neighbors, on page 926 Displays the neighbors discovered by EIGRP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
925
EIGRP Commands
show eigrp neighbors
Syntax Description as-number (Optional) Autonomous system number. This option is available when a VPN
routing and forwarding (VRF) instance is not specified. Range is from 1 to 65535.
vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or
all VRF instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
Release 4.3.0 The command output was modified to display relevant wide metric information.
Release 5.2.0 The command output was modified to display BFD information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show eigrp neighbors command to determine when neighbors become active and inactive. This
command is also useful for debugging certain types of transport problems.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
926
EIGRP Commands
show eigrp neighbors
EIGRP read
Examples The following is sample output from the show eigrp neighbors command:
RP/0/RSP0/CPU0:router#
Field Description
Interface Interface on which the router is receiving hello packets from the peer.
Holdtime Length of time (in seconds) that the Cisco IOS XR software waits to hear from the peer before
declaring that the peer is down.
Uptime Elapsed time (in hours, minutes, and seconds) since the local router first heard from this neighbor.
Q Count Number of EIGRP packets (update, query, and reply) that the software waits to send.
Seq Sequence number of the last update, query, or reply packet that was received from this neighbor.
Num
SRTT Smoothed round-trip time. This is the number of milliseconds required for an EIGRP packet to
be sent to this neighbor and for the local router to receive an acknowledgment of that packet.
RTO Retransmission timeout (in milliseconds). This is the amount of time the software waits before
resending a packet from the retransmission queue to a neighbor.
The following is sample output from the show eigrp neighbors command when issued with the
detail keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
927
EIGRP Commands
show eigrp neighbors
Field Description
Version Version of EIGRP software (major.minor) running on the node and neighbor.
Retries Number of retransmissions sent to this neighbor since the last acknowledgement (ACK).
This is sample output from show eigrp neighbors command to display relevant wide metric
information:
H Address Interface
Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.10.10.11 Gi0/0/0/0 12 01:20:40 420 2520 0 5
Version 3.3/2.0, Retrans: 1, Retries: 0, Prefixes: 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
928
EIGRP Commands
show eigrp topology
show eigrp [as-number] [vrf{vrf-name | all}] [{ipv4 | ipv6}] topology [ip-address mask] {active |
all-links | detail-links | pending | summary | zero-successors}
Syntax Description as-number (Optional) Autonomous system number. This option is available when a VPN
routing and forwarding (VRF) instance is not specified.
Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or
all VRF instances.
active (Optional) Displays only active entries in the EIGRP topology table.
detail-links (Optional) Displays detailed information for all entries in the EIGRP topology table.
pending (Optional) Displays all entries in the EIGRP topology table that are waiting for an
update from a neighbor or are waiting to reply to a neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
929
EIGRP Commands
show eigrp topology
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.3.0 The command output was modified to display relevant wide metric information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the show eigrp topology command is used without any keywords or arguments, only routes that are
feasible successors are displayed.
The show eigrp topology command can be used to determine Diffusing Update Algorithm (DUAL) states
and to debug possible DUAL problems.
EIGRP read
Examples The following is sample output from the show eigrp topology command. The EIGRP metrics for
specified internal routes and external routes are displayed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
930
EIGRP Commands
show eigrp topology
Hop count is 1
External data:
Originating router is 10.89.245.1
AS number of route is 0
External protocol is Connected, external metric is 0
Administrator tag is 0 (0x00000000)
Field Description
10.2.1.1 (Gi0/0) Next hop and interface from which this path was learned.
Send flag Indicates if the sending of this prefix is pending to this neighbor.
Composite The first number is the EIGRP metric that represents the cost to the destination. The
Metric second number is the EIGRP metric that this peer advertised.
(409600/128256)
Vector Metric Shows the metric (bandwidth, delay, reliability, load, MTU, and hop count) advertised
by the neighbor.
External Data Shows the external information (originating router ID, AS number, external protocol,
metric, and tag) advertised by the neighbor.
This is sample show eigrp topology command output to display relevant wide metric information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
931
EIGRP Commands
show eigrp traffic
Syntax Description as-number (Optional) Autonomous system number. This option is available when a VPN
routing and forwarding (VRF) instance is not specified. Range is from 1 to 65535.
vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding instance (VRF) or
all VRF instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show eigrp traffic command to find the number of packets sent and received.
In addition, this command is useful in determining whether packets from one node are not reaching the
neighboring node due to connectivity or configuration problems.
EIGRP read
Examples The following is sample output from the show eigrp traffic command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
932
EIGRP Commands
show eigrp traffic
Field Description
Input queue high water mark Maximum number of packets in the input queue and number of drops.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
933
EIGRP Commands
show protocols (EIGRP)
default-context (Optional) Displays default context information. This keyword is available when the
eigrp or rip protocol is specified.
vrf vrf-name (Optional) Displays VPN routing and forwarding (VRF) information for the specified
process. This keyword is available when the eigrp or rip protocol is specified.
private (Optional) Displays private EIGRP data. This keyword is available when the eigrp is
specified.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.3.0 The command output was modified to display relevant wide metric information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show protocols command to get information about the protocols running on the router and to quickly
determine which protocols are active. The command is designed to summarize the important characteristics
of the running protocol, and command output varies depending on the specific protocol selected.
For EIGRP, the command output lists the instance number, default AS context, router ID, default networks,
distance, maximum paths, and so on.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
934
EIGRP Commands
show protocols (EIGRP)
EIGRP read
Examples The following is sample output from the show protocols eigrp command:
Field Descriptions
Address Family Address family for which the configuration status is shown.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
935
EIGRP Commands
show protocols (EIGRP)
Field Descriptions
Route hold time Time duration for which routes learned from a neighbor are held without
deletion while the neighbor is undergoing a graceful restart.
This is sample output from the show protocols eigrp command with wide metric information:
Field Descriptions
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
936
EIGRP Commands
site-of-origin (EIGRP)
site-of-origin (EIGRP)
To configure the Site of Origin (SoO) filtering on an Enhanced Interior Gateway Routing Protocol (EIGRP)
interface, use the site-of-origin command in interface configuration mode. To disable SoO filtering on an
interface, use the no form of this command.
number Network number. Range is from 0 to 4294967295 when a 2-byte AS number is used. Range
is from 0 to 65535 when a 4-byte AS number is used.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An EIGRP process must be capable of retrieving the SoO attribute on routes redistributed from the Border
Gateway Protocol (BGP) when required to support complex topologies that include MPLS VPN links between
sites with backdoor links.
Use the site-of-origin command to set an SoO BGP extended community attribute that is used to identify
routes that have originated from a site so that the readvertisement of that prefix back to the source site can be
prevented. The SoO extended community uniquely identifies the site from which a provider edge (PE) router
has learned a route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
937
EIGRP Commands
site-of-origin (EIGRP)
eigrp read,
write
Examples The following example shows how to configure SoO filtering on an EIGRP interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
938
EIGRP Commands
split-horizon disable (EIGRP)
split-horizon disable
no split-horizon disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
eigrp read,
write
Examples The following example shows how to disable split horizon an a GigabitEthernet link:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
939
EIGRP Commands
stub (EIGRP)
stub (EIGRP)
To configure a router as a stub for Enhanced Interior Gateway Routing Protocol (EIGRP), use the stub
command in the appropriate configuration mode. To disable this function, use the no form of this command.
redistributed (Optional) Advertises redistributed routes from other protocols and autonomous systems.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the stub command to configure a router as a stub in which the router directs all IP traffic to a distribution
router.
The stub command can be modified with several options, and these options can be used in any combination
except for the receive-only keyword.
The receive-only keyword restricts the router from sharing any of its routes with any other router in that
EIGRP autonomous system and does not permit any other option to be specified because it prevents any type
of route from being sent. The four other optional keywords ( connected , static , summary , and redistributed
) can be used in any combination but cannot be used with the receive-only keyword. If any of these four
keywords is used with the stub command, only the route types specified by the particular keyword or
keywords are sent. Route types specified by the nonused keyword or keywords are not sent.
The connected keyword permits EIGRP stub routing to send connected routes. If all the connected routes
are not covered by EIGRP interfaces, it may be necessary to redistribute connected routes with the redistribute
connected command under the EIGRP process. This option is enabled by default.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
940
EIGRP Commands
stub (EIGRP)
The static keyword permits EIGRP stub routing to send static routes. Without the configuration of this
option, EIGRP does not send any static routes. You may still need to redistribute static routes with the
redistribute static command.
The summary keyword permits EIGRP stub routing to send summary routes. Summary routes can be created
manually with the summary address command or automatically at a major network border router with the
auto-summary command enabled. This option is enabled by default.
The redistributed keyword permits EIGRP stub routing to send other routing protocols and autonomous
systems. Without the configuration of this option, EIGRP does not advertise redistributed routes.
eigrp read,
write
Examples The following example shows how to configure, as a stub, the router that advertises connected and
summary routes:
The following example shows how to configure the router as a receive-only neighbor (connected,
summary, and static routes are not sent):
redistribute (EIGRP), on page 909 Redistributes routes from one routing domain into EIGRP.
summary-address (EIGRP), on page 942 Configures a summary aggregate address for the specified EIGRP
interface.
auto-summary (EIGRP), on page 865 Allows automatic summarization of subnet routes into
network-level routes for an EIGRP process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
941
EIGRP Commands
summary-address (EIGRP)
summary-address (EIGRP)
To configure a summary aggregate address for the specified Enhanced Interior Gateway Routing Protocol
(EIGRP) interface, use the summary-address command in interface configuration mode. To disable a
configuration, use the no form of this command.
Syntax Description ip-address The IP address argument specifies the summary IP address to apply to an interface in
four-part, dotted-decimal notation.
/ length Prefix length, which can be indicated as a slash (/) and number. For example, /8 indicates
that the first eight bits in the IP prefix are network bits. If length is used, the slash is
required.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The summary-address command is used to configure interface-level address summarization. EIGRP
summary routes are given an administrative distance of 5. The administrative distance is used to advertise a
summary without installing it in the routing table.
By default, EIGRP summarizes subnet routes to the network level. The no auto-summary command can
be entered to configure subnet level summarization.
eigrp read,
write
Examples The following example shows how to configure an administrative distance of 95 on an EIGRP
interface for the 192.168.0.0/16 summary address:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
942
EIGRP Commands
summary-address (EIGRP)
auto-summary (EIGRP), on page 865 Allows automatic summarization of subnet routes into network-level
routes for an EIGRP process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
943
EIGRP Commands
timers active-time
timers active-time
To adjust the Enhanced Interior Gateway Routing Protocol (EIGRP) routing wait time, use the timers
active-time command in the appropriate configuration mode. To disable this function, use the timers
active-time no form of the command.
Syntax Description time-limit Active time limit (in minutes). Range is from 1 to 4294967295 minutes.
disabled Disables the timers and permits the routing wait time to remain active indefinitely.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the timers active-time command to control the time the router waits (after query is sent) before declaring
the route to be in the stuck in active (SIA) state.
eigrp read,
write
Examples The following example shows how to configure an indefinite routing wait time on the specified
EIGRP route:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
944
EIGRP Commands
timers nsf route-hold (EIGRP)
Syntax Description seconds Time, in seconds, that EIGRP holds routes for an inactive peer. Range is from 20 to 6000 seconds.
Release 4.1.1 The default route hold time was changed from 240 seconds to 480 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the timers nsf route-hold command to set the maximum period of time that the NSF-aware router holds
known routes for an NSF-capable neighbor during a switchover operation or a well-known failure condition.
The route hold timer is configurable so that you can tune network performance and avoid undesired effects,
such as packet loss on routes if the switchover operation takes too much time. When this timer expires, the
NSF-aware router scans the topology table and discards any stale routes, allowing EIGRP peers to find alternate
routes instead of waiting during a long switchover operation.
eigrp read,
write
Examples The following example shows how to set the route hold timer value for an NSF-aware router to
2 minutes (120 seconds):
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
945
EIGRP Commands
variance
variance
To control load balancing in an Enhanced Interior Gateway Routing Protocol (EIGRP)-based internetwork,
use the variance command in the appropriate configuration mode. To reset the variance to the default value,
use the no form of this command.
variance multiplier
no variance
Syntax Description multiplier Metric value used for load balancing. Range is from 1 to 128.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the variance command to set a variance on the EIGRP router so that the router can determine the
feasibility of a potential route. A route is feasible if the next router in the path is closer to the destination than
the current router and the metric for the entire path is within the variance. Only paths that are feasible can be
used for load balancing and included in the routing table.
If the following two conditions are met, the route is considered feasible and can be added to the routing table:
1. The local best metric must be greater than the metric learned from the next router.
2. The multiplier times the local best metric for the destination must be greater than or equal to the metric
through the next router.
eigrp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
946
EIGRP Commands
vrf (EIGRP)
vrf (EIGRP)
To define a VPN routing and forwarding (VRF) instance and enter VRF configuration mode, use the vrf
command in router configuration mode. To remove a VRF instance, use the no form of this command.
vrf vrf-name
no vrf vrf-name
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vrf command to configure a VRF instance. A VRF instance is a collection of VPN routing and
forwarding tables maintained at the provider edge (PE) router.
From VRF configuration mode, you must enter address family configuration mode and then issue commands,
such as the auto-summary command.
A single EIGRP routing process can support multiple VRFs. The number of VRFs that can be configured is
limited by available system resources on the router, which is determined by the number of VRFs, running
processes, and available memory. However, only a single VRF can be supported by each VPN. Redistribution
between different VRFs is not supported.
MPLS VPN support between PE and customer edge (CE) routers is configured only on PE routers that provide
VPN services over the service provider backbone. The customer site does not require any changes to equipment
or configurations to support the EIGRP VPN. Typically, a metric must be configured for routes to be advertised
to the CE router. The metric can be configured under the route-policy for the redistribute protocol command
or configured with the default-metric command.
You must remove IPv4/IPv6 addresses from an interface prior to assigning, removing, or changing a VRF on
an IP interface. If this is not done in advance, any attempt to change the VRF on an IP interface is rejected.
eigrp read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
947
EIGRP Commands
vrf (EIGRP)
Examples The following example shows how to enter IPv4 VRF address family configuration mode and identify
EIGRP commands that can be issued from that mode.
redistribute (EIGRP), on page 909 Injects routes from one routing domain EIGRP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
948
OSPF Commands
This module describes the commands used to configure and monitor the Open Shortest Path First (OSPF)
routing protocol.
For detailed information about OSPF concepts, configuration tasks, and examples, see the Implementing OSPF
on Cisco ASR 9000 Series Router module in the Routing Configuration Guide for Cisco ASR 9000 Series
Routers .
• address-family (OSPF), on page 952
• adjacency stagger, on page 953
• area (OSPF), on page 955
• authentication (OSPF), on page 957
• authentication-key (OSPF), on page 959
• auto-cost (OSPF), on page 961
• capability opaque disable, on page 963
• clear ospf process, on page 964
• clear ospf redistribution, on page 966
• clear ospf routes, on page 968
• clear ospf statistics, on page 969
• cost (OSPF), on page 971
• cost-fallback (OSPF), on page 973
• database-filter all out (OSPF), on page 975
• dead-interval (OSPF), on page 976
• default-cost (OSPF), on page 978
• default-information originate (OSPF), on page 980
• default-metric (OSPF), on page 982
• demand-circuit (OSPF), on page 984
• disable-dn-bit-check, on page 986
• distance (OSPF), on page 987
• distance ospf, on page 990
• distribute-list, on page 992
• domain-id (OSPF), on page 994
• domain-tag, on page 996
• fast-reroute (OSPFv2), on page 997
• fast-reroute per-link exclude interface, on page 999
• fast-reroute per-prefix exclude interface (OSPFv2), on page 1001
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
949
OSPF Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
950
OSPF Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
951
OSPF Commands
address-family (OSPF)
address-family (OSPF)
To enter address family configuration mode for Open Shortest Path First (OSPF), use the address-family
command in the appropriate mode. To disable address family configuration mode, use the no form of this
command.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPF version 2 automatically provides routing services for IPv4 unicast topologies, so this command is
redundant.
ospf read,
write
Examples The following example shows how to configure the OSPF router process with IPv4 unicast address
prefixes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
952
OSPF Commands
adjacency stagger
adjacency stagger
To configure staggering of OSPF adjacency during reload, process restart, and process clear, use the adjacency
stagger command in router configuration mode. To turn off adjacency staggering, either use the disable
keyword or use the no form of this command.
initial-num-nbr The initial number of simultaneous neighbors allowed to form adjacency to FULL in any
area to bring up to FULL after a router reload, OSPF process restart, or OSPF process
clear. Range is 1-65535. Default is 2.
max-num-nbr The subsequent number of simultaneous neighbors allowed to form adjacency, per OSPF
instance, after the initial set of OSPF neighbors have become FULL. Range is 1-65535.
Default is 64.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Staggering of the OSPF adjacency during reload, process restart (without NSR or graceful-restart), and process
clear reduces the overall adjacency convergence time.
Initially, allow 2 (configurable) neighbors to form adjacency to FULL per area. After the first adjacency
reaches FULL, up to 64 (configurable) neighbors can form adjacency simultaneously for the OSPF instance
(all areas). However, areas without any FULL adjacency is restricted by the initial area limit.
Note Adjacency stagger and OSPF nonstop forwarding (NSF) are mutually exclusive. Adjacency stagger will not
be activated if nsf is configured under router ospf configuration.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
953
OSPF Commands
adjacency stagger
Examples The following example shows how to configure adjacency stagger for a 2 neighbors initially and for
a maximum of 3 neighbors:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# adjacency stagger 2 3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
954
OSPF Commands
area (OSPF)
area (OSPF)
To configure an Open Shortest Path First (OSPF) area, use the area command in the appropriate mode. To
terminate an OSPF area, use the no form of this command.
area area-id
no area area-id
Syntax Description area-id Identifier of an OSPF area. The area-id argument can be specified as either a decimal value or an
IP address (dotted decimal) format. Range is 0 to 4294967295.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the area command to explicitly configure an area. Commands configured under the area configuration
mode (such as the interface [OSPF] and authentication commands), are automatically bound to that area.
To modify or remove the area, the area-id argument format must be the same as the format used when
creating the area. Otherwise, even if the actual 32-bit value matches, the area is not matched. For example, if
you create an area with an area-id of 10 it would not match an area-id of 0.0.0.10.
Note To remove the specified area from the router configuration, use the no area area-id command. The no
area area-id command removes the area and all area options, such as authentication , default-cost ,
nssa , range , stub , virtual-link , and interface.
ospf read,
write
Examples The following example shows how to configure area 0 and GigabitEthernet interface 0/2/0/0.
GigabitEthernet interface 0/2/0/0 is bound to area 0 automatically.
RP/0/RSP0/CPU0:router# configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
955
OSPF Commands
area (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
956
OSPF Commands
authentication (OSPF)
authentication (OSPF)
To enable plain-text authentication, Message Digest 5 (MD5) authentication, Keychain-based authentication
or null authentication for an Open Shortest Path First (OSPF) interface, use the authentication command
in the appropriate mode. To remove such authentication, use the no form of this command.
null (Optional) Specifies that no authentication is used. Useful for overriding password
or MD5 authentication if configured for an area.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the authentication
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the authentication
parameter specified for the process.
If this command is not specified at any level, then the interface does not use authentication.
If no keyword is specified, plain text authentication is used.
Area configuration
Router configuration
Virtual-link configuration
VRF configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the authentication command to specify an authentication type for the interface, which overrides the
authentication specified for the area to which this interface belongs. If this command is not included in the
configuration file, the authentication configured in the area to which the interface belongs is assumed (as
specified by the area authentication command).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
957
OSPF Commands
authentication (OSPF)
The authentication type and password must be the same for all OSPF interfaces that are to communicate with
each other through OSPF. If you specified plain text authentication, use the authentication-key command
to specify the plain text password.
If you enable MD5 authentication with the message-digest keyword, you must configure a key with the
message-digest-key interface command.
To manage the rollover of keys and enhance MD5 authentication for OSPF, you can configure a container of
keys called a keychain with each key comprising the following attributes: generate/accept time, key
identification, and authentication algorithm. The keychain management feature is always enabled.
Note Changes to the system clock will impact the validity of the keys in the existing configuration.
ospf read,
write
Examples The following example shows how to set authentication for areas 0 and 1 of OSPF routing process
201. Authentication keys are also provided.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# router-id 10.1.1.1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# authentication
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# authentication-key mykey
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# exit
RP/0/RSP0/CPU0:router(config-ospf)# area 1
RP/0/RSP0/CPU0:router(config-ospf-ar)# authentication
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# authentication-key mykey1
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# router-id 10.1.1.1
RP/0/RSP0/CPU0:router(config-ospf)# authentication message-digest keychain mykeychain
authentication-key (OSPF), on page 959 Assigns a password to be used by neighboring routers that are using
the simple password authentication of OSPF.
message-digest-key, on page 1030 Specifies a key used with OSPF MD5 authentication.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
958
OSPF Commands
authentication-key (OSPF)
authentication-key (OSPF)
To assign a password to be used by neighboring routers that are using the Open Shortest Path First (OSPF)
simple password authentication, use the authentication-key command in the appropriate mode. To remove
a previously assigned OSPF password, use the no form of this command.
Syntax Description clear (Optional) Specifies that the key be clear text.
encrypted (Optional) Specifies that the key be encrypted using a two-way algorithm.
password Any contiguous string up to 8 characters in length that can be entered from the keyboard. For
example, mypswd2.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the OSPF password
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the OSPF password
parameter specified for the process.
If this command is not specified at any level, then no password is specified.
Clear is the default if the clear or encrypted keyword is not specified.
Area configuration
Router configuration
Virtual-link configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The password created by this command is inserted directly into the OSPF header when the Cisco IOS XR
software originates routing protocol packets. A separate password can be assigned to each network on an
individual interface basis. All neighboring routers on the same network must have the same password to be
able to exchange OSPF information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
959
OSPF Commands
authentication-key (OSPF)
The authentication-key command must be used with the authentication command. If the authentication
command is not configured, the password provided by the authentication-key command is ignored and no
authentication is adopted by the OSPF interface.
Note The authentication-key command cannot be used with the authentication command when the
message-digest or null keyword is configured.
ospf read,
write
Examples The following example shows how to configure an authentication password as the string yourpass:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# authentication-key yourpass
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
960
OSPF Commands
auto-cost (OSPF)
auto-cost (OSPF)
To control how the Open Shortest Path First (OSPF) protocol calculates default metrics for the interface, use
the auto-cost command in the appropriate mode. To revert to the default reference bandwidth, use the no
form of this command.
Syntax Description reference-bandwidth mbps Specifies a rate in Mbps (bandwidth). Range is 1 to 4294967.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default OSPF calculates the OSPF metric for an interface according to the bandwidth of the interface.
The OSPF metric is calculated as the mbps value divided by bandwidth, with mbps equal to 108 by default.
If you have multiple links with high bandwidth (such as OC-192), you might want to use a larger number to
differentiate the cost on those links. That is, the metric calculated using the default mbps value is the same
for all high-bandwidth links.
Recommended usage of cost configuration for OSPF interfaces with high bandwidth is to be consistent: Either
explicitly configure (by using the cost command) or choose the default (by using the auto-cost command).
The value set by the cost command overrides the cost resulting from the auto-cost command.
ospf read,
write
Examples The following example shows how to set the reference value for the auto cost calculation to 1000
Mbps:
RP/0/RSP0/CPU0:router# configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
961
OSPF Commands
auto-cost (OSPF)
cost (OSPF), on page 971 Explicitly specifies the cost of the interface (network) for OSPF path calculation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
962
OSPF Commands
capability opaque disable
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The capability opaque disable command prevents flooded MPLS TE information (Types 1 and 4) through
opaque LSAs of all scope (Types 9, 10, and 11).
Control opaque LSA support capability must be enabled for OSPF to support MPLS TE.
The MPLS TE topology information is flooded to the area through opaque LSAs by default.
ospf read,
write
Examples The following example shows how to prevent OSPF from supporting opaque services:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# capability opaque disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
963
OSPF Commands
clear ospf process
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospf command. If this argument is included, only the specified routing
process is affected. Otherwise, all OSPF processes are reset.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the OSPF router process is reset, OSPF releases all resources allocated, cleans up the internal database,
and shuts down and restarts all interfaces that belong to the process.
Note The clear ospf process command may change the router ID unless the OSPF router ID is explicitly configured
through the router-id (OSPF), on page 1088 command.
ospf read,
write
Examples The following example shows how to reset all OSPF processes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
964
OSPF Commands
clear ospf process
router-id (OSPF), on page 1088 Configures a router ID for the OSPF process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
965
OSPF Commands
clear ospf redistribution
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospf command. If this argument is included, only the specified routing
process is affected. Otherwise, all OSPF routes are cleared.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear ospf redistribution command to cause the routing table to be read again. OSPF regenerates
and sends Type 5 and Type 7 link-state advertisements (LSAs) to its neighbors. If an unexpected route has
appeared in the OSPF redistribution, using this command corrects the issue.
Note Use of this command can cause a significant number of LSAs to flood the network. We recommend that you
use this command with caution.
ospf read,
write
Examples The following example shows how to clear all redistributed routes across all processes from other
protocols:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
966
OSPF Commands
clear ospf redistribution
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
967
OSPF Commands
clear ospf routes
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospf command. If this argument is included, only the specified routing
process is affected. Otherwise, all OSPF routes are cleared.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to clear all OSPF routes from the OSPF routing table and
recompute valid routes. When the OSPF routing table is cleared, OSPF routes in the global routing
table are also recalculated.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
968
OSPF Commands
clear ospf statistics
clear ospf [process-name [vrf {vrf-name | all}]] statistics [neighbor [type interface-path-id]
[ip-address]]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospf command. If this argument is included, only the specified
routing process is affected. Otherwise, all OSPF statistics of neighbor state transitions
are cleared.
neighbor (Optional) Clears the state transition counters of the specified neighbor only.
type (Optional) Interface type. For more information, use the question mark (?) online help
function.
ip-address (Optional) IP address of a specified neighbor for whom you want to clear the state
transition counter.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear ospf statistics command to reset OSPF counters. Reset is useful to detect changes in counter
values.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
969
OSPF Commands
clear ospf statistics
ospf read,
write
Examples The following example shows how to reset the OSPF transition state counters for all neighbors on
Packet-over-SONET/SDH (POS) interface 0/2/0/0:
RP/0/RSP0/CPU0:router# clear ospf statistics neighbor POS 0/2/0/0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
970
OSPF Commands
cost (OSPF)
cost (OSPF)
To explicitly specify the interface (network) for Open Shortest Path First (OSPF) path calculation, use the
cost command in the appropriate mode. To remove the cost, use the no form of this command.
cost cost
no cost
Syntax Description cost Unsigned integer value expressed as the link-state metric. Range is 1 to 65535.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the cost parameter
specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the cost parameter
specified for the process.
If this command is not specified at any level, then the cost is calculated by the auto-cost command.
Area configuration
Router configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The link-state metric is advertised as the link cost in the router link advertisement. Cisco IOS XR software
does not support type of service (ToS), so you can assign only one cost for each interface.
In general, the path cost is calculated using the following formula:
108 / bandwidth (the default auto cost is set to 100 Mbps)
This calculation is the default reference bandwidth used by the auto-costing calculation which establishes the
interface auto-cost The auto-cost command can set this reference bandwidth to some other value. The cost
command is used to override the auto-costing calculated default value for interfaces.
Using this formula, the default path cost is 1 for any interface that has a link bandwidth of 100 Mbps or higher.
If this value does not suit the network, configure the reference bandwidth for auto calculating costs based on
the link bandwidth.
The value set by the cost command overrides the cost resulting from the auto-cost (OSPF) command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
971
OSPF Commands
cost (OSPF)
ospf read,
write
Examples The following example shows how to set the cost value to 65 for GigabitEthernet interface 0/1/0/1:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# cost 65
auto-cost (OSPF), on page 961 Controls how the OSPF protocol calculates default metrics for the interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
972
OSPF Commands
cost-fallback (OSPF)
cost-fallback (OSPF)
To apply higher cost than the normal interface cost when the cumulative bandwidth of a bundle interface goes
below the threshold specified and to revert to the original cost if the cumulative bandwidth goes above the
configured threshold, use the cost-fallback command. To remove the cost-fallback, use the no form of this
command.
Syntax Description cost threshold Unsigned integer value expressed as the link-state metric. Range is 1 to 65535, but
typically, cost-fallback value is supposed to be set to a value higher than the normal cost.
bandwidth Unsigned integer value expressed in Mbits per second. Range is 1 to 4294967.
Command Default If this command is not specified in interface configuration mode, the currently effective interface cost takes
effect even when the cumulative bandwidth goes down below the maximum bandwidth. Unlike the interface
cost command, this cost-fallback command is available only under interface configuration mode; it is not
available in area or process level. Unlike other interface specific parameters, no inheritance will take place
from area or process level if this command is not specified at interface level.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The fallback cost must be set to a higher value than the normal interface cost. The motivation of setting the
fallback cost is to cost out an interface or disfavor an interface without shutting it down when its cumulative
bandwidth goes below the user specified threshold, so that the traffic can take an alternative path. The normal
interface cost will take over when the cumulative bandwidth reaches or exceeds user-specified threshold.
ospf read,
write
Examples The following example shows how to set the cost-fallback value:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#router-id 2.2.2.2
RP/0/RSP0/CPU0:router(config-ospf)#area 0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
973
OSPF Commands
cost-fallback (OSPF)
RP/0/RSP0/CPU0:router(config-ospf-ar)#interface bundle-a
RP/0/RSP0/CPU0:router(config-ospf-ar-if)#cost-fallback 1000 threshold 300
auto-cost (OSPF), on page 961 Controls how the OSPF protocol calculates default metrics for the interface.
cost (OSPF), on page 971 Specifies the cost of the interface (network) for OSPF path calculation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
974
OSPF Commands
database-filter all out (OSPF)
Area configuration
Router configuration
VRF configuration
Multi-area configuration
ospf read,
write
Examples The following example shows how to prevent flooding of OSPF LSAs to broadcast, nonbroadcast,
and point-to-point networks reachable through GigabitEthernet interface 0/1/0/1:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# database-filter all out
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
975
OSPF Commands
dead-interval (OSPF)
dead-interval (OSPF)
To set the interval after which a neighbor is declared dead when no hello packets are observed, use the
dead-interval command in the appropriate mode. To return to the default time, use the no form of this
command.
dead-interval seconds
no dead-interval
Syntax Description seconds Integer that specifies the interval (in seconds). Range is 1 to 65535. The value must be the same
for all nodes on the network.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the dead interval
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the dead interval
parameter specified for the process.
If this command is not specified at any level, then the dead interval is four times the interval set by the
hello-interval (OSPF) command.
Area configuration
Router configuration
Virtual-link configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The dead interval value must be the same for all routers and access servers on a specific network.
If the hello interval is configured, the dead interval value must be larger than the hello interval value. The
dead interval value is usually configured four times larger than the hello interval value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
976
OSPF Commands
dead-interval (OSPF)
ospf read,
write
Examples The following example shows how to set the OSPF dead interval to 40 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# dead-interval 40
hello-interval (OSPF), on page 1010 Specifies the interval between hello packets that the Cisco IOS XR
software sends on the interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
977
OSPF Commands
default-cost (OSPF)
default-cost (OSPF)
To specify a cost for the default summary route sent into a stub area or not-so-stubby area (NSSA), use the
default-cost command in area configuration mode. To remove the assigned default route cost, use the no
form of this command.
default-cost cost
no default-cost cost
Syntax Description cost Cost for the default summary route used for a stub or NSSA area. The acceptable value is a 24-bit
number.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-cost command only on an Area Border Router (ABR) attached to a stub or an NSSA area.
In all routers and access servers attached to the stub area, the area should be configured as a stub area using
the stub command in the area submode. Use the default-cost command only on an ABR attached to the
stub area. The default-cost command provides the metric for the summary default route generated by the
ABR into the stub area.
ospf read,
write
Examples The following example shows how to assign a default cost of 20 to a stub area. The GigabitEthernet
interface 0/4/0/3 is also configured in the stub area:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# area 10.15.0.0
RP/0/RSP0/CPU0:router(config-ospf-ar)# stub
RP/0/RSP0/CPU0:router(config-ospf-ar)# default-cost 20
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/4/0/3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
978
OSPF Commands
default-cost (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
979
OSPF Commands
default-information originate (OSPF)
Syntax Description always (Optional) Always advertises the default route regardless of whether the routing
table has a default route.
metric metric-value (Optional) Specifies the metric used for generating the default route. The default
metric value is 1. Range is 1 to 16777214.
metric-type type-value (Optional) Specifies the external link type associated with the default route
advertised into the OSPF routing domain. It can be one of the following values:
1—Type 1 external route
2—Type 2 external route
tag tag-value (Optional) 32-bit dotted-decimal value attached to each external route. This is
not used by the OSPF protocol itself. It may be used to communicate
information between autonomous system boundary routers (ASBRs). If a tag
is not specified, then the configured OSPF process number is used.
route-policy policy-name (Optional) Specifies that a routing policy be used and the routing policy name.
Command Default When you do not use this command in router configuration mode, no default external route is generated into
an OSPF routing domain.
metric-value : 1
type-value : 2
tag-value: configured OSPF process number
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
980
OSPF Commands
default-information originate (OSPF)
Whenever you use the redistribute or default-information originate command to redistribute routes into
an OSPF routing domain, the software automatically becomes an Autonomous System Boundary Router
(ASBR). However, an ASBR does not, by default, generate a default route into the OSPF routing domain.
The software still must have a default route for itself before it generates one, except when you have specified
the always keyword.
The default-information originate route-policy attach point conditionally injects the default route 0.0.0.0/0
into the OSPF link-state database, and is done by evaluating the attached policy. If any routes specified in the
policy exist in the global RIB, then the default route is inserted into the link-state database. If there is no match
condition specified in the policy, the policy passes and the default route is generated into the link-state database.
For information about the default-information originate attach point, see the OSPF Policy Attach Points section
in the Implementing Routing Policy chapter in Routing Configuration Guide for Cisco ASR 9000 Series
Routers.
For information about routing policies, see the Routing Policy Commands chapter in the Routing Command
Reference for Cisco ASR 9000 Series Routers.
ospf read,
write
Examples The following example shows how to specify a metric of 100 for the default route redistributed into
the OSPF routing domain and an external metric type of Type 1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)#redistribute igrp 108 metric 100
RP/0/RSP0/CPU0:router(config-ospf)#default-information originate metric 100 metric-type 1
redistribute (OSPF), on page 1080 Redistributes routes from one routing domain into a specified OSPF
process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
981
OSPF Commands
default-metric (OSPF)
default-metric (OSPF)
To set default metric values for routes redistributed from another protocol into the Open Shortest Path First
(OSPF) protocol, use the default-metric command in the appropriate mode. To return to the default state,
use the no form of this command.
default-metric value
no default-metric value
Syntax Description value Default metric value appropriate for the specified routing protocol. Range is 1 to 16777214.
Command Default Built-in, automatic metric translations, as appropriate for each routing protocol.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-metric command with the redistribute command to cause the current routing protocol to
use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing
routes with incompatible metrics. Whenever metrics do not convert, use a default metric to provide a reasonable
substitute and enable the redistribution to proceed.
The default-metric value configured in OSPF configuration does not apply to connected routes that are
redistributed to OSPF using the redistribute connected command. To set a non-default metric for connected
routes, configure OSPF with the redistribute connected metric metric-value command.
ospf read,
write
Examples The following example shows how to advertise Intermediate System-to-Intermediate System (IS-IS)
protocol-derived routes into OSPF and assign a metric of 10:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# default-metric 10
RP/0/RSP0/CPU0:router(config-ospf)# redistribute isis IS-IS_isp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
982
OSPF Commands
default-metric (OSPF)
redistribute (OSPF), on page 1080 Redistributes routes from one routing domain into a specified OSPF
process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
983
OSPF Commands
demand-circuit (OSPF)
demand-circuit (OSPF)
To configure the Open Shortest Path First (OSPF) protocol to treat the interface as an OSPF demand circuit,
use the demand-circuit command in the appropriate mode. To remove the demand circuit designation from
the interface, use the no form of this command.
Syntax Description disable (Optional) Disables the interface as an OSPF demand circuit.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the demand circuit
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the demand circuit
parameter specified for the process.
If this command is not specified at any level, then the circuit is not a demand circuit.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
On point-to-point interfaces, only one end of the demand circuit must be configured with this command.
Periodic hello messages are suppressed and periodic refreshes of link-state advertisements (LSAs) do not
flood the demand circuit. Use the demand-circuit command to allow the underlying data link layer to be
closed when the topology is stable. In point-to-multipoint topology, only the multipoint end must be configured
with this command.
ospf read,
write
Examples The following example shows how to set the configuration for an OSPF demand circuit:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
984
OSPF Commands
demand-circuit (OSPF)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# demand-circuit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
985
OSPF Commands
disable-dn-bit-check
disable-dn-bit-check
To specify that down bits should be ignored, use the disable-dn-bit-check command in VPN routing and
forwarding (VRF) configuration mode. To specify that down bits should be considered, use the no form of
this command.
disable-dn-bit-check
no disable-dn-bit-check
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to specify that down bits be ignored:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# vrf v1
RP/0/RSP0/CPU0:router(config-ospf-vrf)# disable-dn-bit-check
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
986
OSPF Commands
distance (OSPF)
distance (OSPF)
To define an administrative distance, use the distance command in an appropriate configuration mode. To
remove the distance command from the configuration file and restore the system to its default condition in
which the software removes a distance definition, use the no form of this command.
Syntax Description weight Administrative distance. Range is 10 to 255. Used alone, the weight argument specifies
a default administrative distance that the software uses when no other specification exists
for a routing information source. Routes with a distance of 255 are not installed in the
routing table. lists the default administrative distances. Table 90: Default Administrative
Distances, on page 988
wildcard-mask (Optional) Wildcard mask in four-part, dotted decimal format. A bit set to 1 in the mask
argument instructs the software to ignore the corresponding bit in the address value.
Command Default If this command is not specified, then the administrative distance is the default, as specified in Table 90:
Default Administrative Distances, on page 988.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An administrative distance is an integer from 10 to 255. In general, the higher the value, the lower the trust
rating. An administrative distance of 255 means that the routing information source cannot be trusted at all
and should be ignored. Weight values are subjective; no quantitative method exists for choosing weight values.
If an access list is used with this command, it is applied when a network is being inserted into the routing
table. This behavior allows you to filter networks based on the IP prefix supplying the routing information.
For example, you could filter possibly incorrect routing information from networking devices not under your
administrative control.
The order in which you enter distance commands can affect the assigned administrative distances in
unexpected ways (see the “Examples” section for further clarification).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
987
OSPF Commands
distance (OSPF)
Connected interface 0
External BGP 20
Internal EIGRP 90
OSPF 110
IS-IS 115
Unknown 255
ospf read,
write
Examples In the following example, the router ospf command sets up OSPF routing instance1. The first
distance command sets the default administrative distance to 255, which instructs the software to
ignore all routing updates from networking devices for which an explicit distance has not been set.
The second distance command sets the administrative distance for all networking devices on the
Class C network 192.168.40.0 0.0.0.255 to 90.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# distance 255
RP/0/RSP0/CPU0:router(config-ospf)# distance 90 192.168.40.0 0.0.0.255
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
988
OSPF Commands
distance (OSPF)
distance bgp Allows the use of external, internal, and local administrative distances that could
be a better route to a BGP node.
distance ospf Allows the use of external, internal, and local administrative distances that could
be a better route to an OSPF node.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
989
OSPF Commands
distance ospf
distance ospf
To define Open Shortest Path First (OSPF) route administrative distances based on route type, use the distance
ospf command in router configuration mode. To restore the default value, use the no form of this command.
Syntax Description intra-area | inter-area | Sets the type of area. It can be one of the following values:
external
intra-area —All routes within an area.
inter-area —All routes from one area to another area.
external —All routes from other routing domains, learned by redistribution.
Any combination of the above areas is allowed.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must specify one of the keywords.
Use the distance ospf command to perform the same function as the distance command used with an access
list. However, the distance ospf command sets a distance for an entire group of routes, rather than a specific
route that passes an access list.
A common reason to use the distance ospf command is when you have multiple OSPF processes with mutual
redistribution, and you want to prefer internal routes from one over external routes from the other.
ospf read,
write
Examples The following example shows how to change the external distance to 200, making the route less
reliable:
RP/0/RSP0/CPU0:router# configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
990
OSPF Commands
distance ospf
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
991
OSPF Commands
distribute-list
distribute-list
To filter networks received or transmitted in Open Shortest Path First (OSPF) updates, use the distribute-list
command in the appropriate mode. To change or cancel the filter, use the no form of this command.
distribute-list {access-list-name {in | out [{bgp number | connected | ospf instance | static}]} |
route-policy route-policy-name in}
no distribute-list {access-list-name {in | out} | route-policy route-policy-name in}
Syntax Description access-list-name Standard IP access list name. The list defines which networks are to be
received and which are to be suppressed in routing updates.
out Applies the access list to outgoing routing updates. The out keyword is
available only in router configuration mode.
ospf (Optional) Applies the access list to OSPF routes (not the current OSPF
process).
Command Default If this command is not specified in interface configuration mode, then the interface adopts the distribute list
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the distribute list
parameter specified for the process.
If this command is not specified at any level, then the distribute list is disabled.
Area configuration
Router configuration
VRF configuration
Multi-area configuration
Release 4.2.1 The route-policy route-policy-name keyword and argument were added to allow use of route
policies to filter OSPF prefixes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
992
OSPF Commands
distribute-list
Release Modification
Release 4.3.1 Support was added for "if tag..." statements in distribute-list in route-policy.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the distribute-list command to limit which OSPF routes are installed on this router. The distribute-list
command does not affect the OSPF protocol itself.
The distribute-list in is configurable at instance (process), area, and interface levels. Regular OSPF
configuration inheritance applies. Configuration is inherited from instance > area > interface levels.
Use the route-policy route-policy-name keyword and argument to allow use of route policies to filter OSPF
prefixes.
Note Either an access-list, or a route-policy can be used in a single command, not both. Configuring the command
with access-list removes the route-policy configuration, and vice versa.
The "if tag..." statements can be used in distribute-list in route-policy. The matching on route tag supports
operators "eq/ge/is/le". Operator "in" is not supported.
ospf read,
write
Examples The following example shows how to prevent OSPF routes from the 172.17.10.0 network from being
installed if they are learned in area 0:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# ipv4 access-list 3
RP/0/RSP0/CPU0:router(config-ipv4-acl)# deny 172.17.10.0 0.0.0.255
RP/0/RSP0/CPU0:router(config-ipv4-acl)# permit any any
!
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# distribute-list 3 in
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
993
OSPF Commands
domain-id (OSPF)
domain-id (OSPF)
To specify the Open Shortest Path First (OSPF) VPN routing and forwarding (VRF) domain ID, use the
domain-id command in VRF configuration mode. To remove an OSPF VRF domain ID, use the no form
of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An OSPF domain id must be explicitly configured. The OSPF domain ID helps OSPF determine how to
translate a prefix received through Border Gateway Protocol (BGP) from the remote provider edge (PE). If
the domain IDs match, OSPF generates a Type 3 link state advertisement (LSA). If the domain IDs do not
match, OSPF generates a Type 5 LSA.
There is only one primary domain ID. There can be multiple secondary domain IDs.
Note When an IOS XR router and an IOS router are configured as peers, the two Domain IDs must match. Manually
configure the IOS XR Domain ID value to match the IOS default Domain ID value. This ensures that the
routes have route code "OIA" because they are learned as inter-area routes. If the Domain IDs do not match,
the routes have route code, "O-E2" because they are learned as external routes. Use the show ip ospf command
to get the OSPF Domain ID from the IOS router. Then, set the IOS XR Domain ID to the same value using
the domain-id command.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
994
OSPF Commands
domain-id (OSPF)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf o1
RP/0/RSP0/CPU0:router(config-ospf)# vrf v1
RP/0/RSP0/CPU0:router(config-ospf-vrf)# domain-id type 0105 value AABBCCDDEEFF
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
995
OSPF Commands
domain-tag
domain-tag
To specify the Open Shortest Path First (OSPF) VPN routing and forwarding (VRF) domain tag, use the
domain-tag command in VRF configuration mode. To remove an OSPF VRF domain tag, use the no form
of this command.
domain-tag tag
no domain-tag
Syntax Description tag OSPF domain tag as a 32-bit value. The valid range is 0 to 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The domain tag is added to any Type 5 link state advertisements (LSAs) generated as a result of VPN-IP
routes received from Border Gateway Protocol (BGP). The domain-tag is derived from BGP autonomous
system number (ASN).
ospf read,
write
Examples The following example shows how to specify the domain tag:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf o1
RP/0/RSP0/CPU0:router(config-ospf)# domain-tag 234
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
996
OSPF Commands
fast-reroute (OSPFv2)
fast-reroute (OSPFv2)
To enable IP fast reroute loop-free alternate (LFA) computation, use the fast-reroute command in the
appropriate OSPF configuration mode. To disable the IP fast reroute loop-free alternate computation, use the
no form of this command.
To disable loop-free alternate computation that is enabled on a higher level, use the fast-reroute command
with disable keyword.
disable (Optional) Disables loop-free alternate computation that was enabled on a higher level.
Interface configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Only one mode of computation can be configured on an interface - per-link or per-prefix. Different modes of
computations can be enabled on different interfaces; one set of interface using per-link and other set using
per-prefix computation. Based on the outgoing interface of the primary path, per-link or per-prefix backup
path will be computed.
This example shows how to enable per-link computation of loop-free alternates under interface POS
0/3/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
997
OSPF Commands
fast-reroute (OSPFv2)
This example shows how to enable per-prefix computation of loop-free alternates under area 0:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)#area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)#fast-reroute per-prefix
This example shows how to disable computation of loop-free alternates that was configured under
area 0:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)#area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)#fast-reroute per-prefix
RP/0/RSP0/CPU0:router(config-ospf-ar)#interface GigabitEthernet 0/3/0/0
RP/0/RSP0/CPU0:router(config-ospf-ar-if)#fast-reroute disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
998
OSPF Commands
fast-reroute per-link exclude interface
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to exclude an interface from IP fast reroute loop-free alternate
(LFA) computation:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
999
OSPF Commands
fast-reroute per-link exclude interface
fast-reroute (OSPFv2), on page 997 Enables IP fast reroute loop-free alternate (LFA) computation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1000
OSPF Commands
fast-reroute per-prefix exclude interface (OSPFv2)
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online help
function.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Backup paths via the excluded interfaces will not be computed.
This example shows how to exclude interface POS0/6/0/1 from being used as a backup path:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1001
OSPF Commands
fast-reroute per-prefix exclude interface (OSPFv2)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1002
OSPF Commands
fast-reroute per-prefix lfa-candidate (OSPFv2)
Syntax Description interface-name Specifies name of the interface to add to the LFA candidate list.
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#fast-reroute per-prefix lfa-candidate interface
GigabitEthernet 0/6/0/0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1003
OSPF Commands
fast-reroute per-prefix remote-lfa (OSPFv2)
maximum-cost path-cost Sets the cost option to limit the range of remote LFAs. Range for path-cost is 1
to 4294967295.
disable Selectively disables remote LFA calculation under one or more areas.
Area configuration
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Fast-reroute per-prefix LFA must be enabled for remote LFA to be operational. The OSPF configuration
hierarchy at process level and area level are applicable for remote LFA configuration. For example, it is
possible to enable remote-LFA for all OSPF areas and selectively disable (using disable keyword) the
computation under one or more area.
This example shows how to enable fast-reroute per-prefix remote LFA computation for tunnel
interfaces:
RP/0/RSP0/CPU0:router(config)#router ospf 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1004
OSPF Commands
fast-reroute per-prefix remote-lfa (OSPFv2)
This example shows how to configure cost option to limit the range of remote LFAS:
RP/0/RSP0/CPU0:router(config)#router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)#fast-reroute per-prefix remote-lfa maximum-cost 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1005
OSPF Commands
fast-reroute per-prefix ti-lfa
Syntax Description enable Enables per-prefix Topology Independent Loop-Free Alternate Fast Reroute (TI-LFAFRR)
computation to reroute traffic around link failures.
disable Disables per-prefix Topology Independent Loop-Free Alternate Fast Reroute (TI-LFAFRR)
computation.
Area configuration
Router configuration
Usage Guidelines OSPFv2 Loop-Free Alternate Fast Reroute TI-LFA is built on top of per-prefix LFA and as such requires
per-prefix LFA to be enabled on the interface, where TI-LFA is enabled.
This example shows how to enable per-prefix Topology Independent Loop-Free Alternate Fast
Reroute computation for the interface:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf
RP/0/RSP0/CPU0:router(config-ospf)#area 1
RP/0/RSP0/CPU0:router(config-ospf-ar)#interface
GigabitEternet0/5/0/0 fast-reroute per-prefix ti-lfa enable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1006
OSPF Commands
fast-reroute per-prefix use-candidate-only (OSPFv2)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to restrict the backup interfaces to those that are present on the LFA
candidate list:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#fast-reroute per-prefix use-candidate-only
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1007
OSPF Commands
flood-reduction (OSPF)
flood-reduction (OSPF)
To suppress the unnecessary flooding of link-state advertisements (LSAs) in stable topologies, use the
flood-reduction command in the appropriate mode. To remove this functionality from the configuration, use
the no form of this command.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the flood reduction
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the flood reduction
parameter specified for the process.
If this command is not specified at any level, then flood reduction is disabled.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
All routers supporting the OSPF demand circuit are compatible and can interact with routers supporting
flooding reduction.
ospf read,
write
Examples The following example shows how to reduce the flooding of unnecessary LSAs for area 0:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1008
OSPF Commands
flood-reduction (OSPF)
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# flood-reduction
show ospf neighbor, on page 1132 Displays OSPF neighbor information on an individual interface basis.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1009
OSPF Commands
hello-interval (OSPF)
hello-interval (OSPF)
To specify the interval between consecutive hello packets that are sent on the Open Shortest Path First (OSPF)
interface, use the hello-interval command in the appropriate mode. To return to the default time, use the
no form of this command.
hello-interval seconds
no hello-interval
Syntax Description seconds Interval (in seconds). The value must be the same for all nodes on a specific network. Range is 1
to 65535.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the hello interval
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the hello interval
parameter specified for the process.
If this command is not specified at any level, then the hello interval is 10 seconds (broadcast) or 30 seconds
(non-broadcast).
Area configuration
Router configuration
Virtual-link configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The hello interval value is advertised in the hello packets. The shorter the hello interval, the faster topological
changes are detected, but more routing traffic occurs. This value must be the same for all routers and access
servers on a specific network.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1010
OSPF Commands
hello-interval (OSPF)
Examples The following example shows how to set the interval between hello packets to 15 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# hello-interval 15
dead-interval (OSPF), on page 976 Sets the time period for which hello packets are suspended before
neighbors declare the router down.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1011
OSPF Commands
ignore lsa mospf
Command Default When you do not specify this command in router configuration mode, each MOSPF packet received by the
router causes the router to send a syslog message.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco routers do not support LSA Type 6 (MOSPF), and they generate syslog messages if they receive such
packets. If the router is receiving many MOSPF packets, you might want to configure the router to ignore the
packets and thus prevent a large number of syslog messages.
ospf read,
write
Examples The following example shows how to configure the router to suppress the sending of syslog messages
when it receives MOSPF packets:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# ignore lsa mospf
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1012
OSPF Commands
interface (OSPF)
interface (OSPF)
To define the interfaces on which the Open Shortest Path First (OSPF) protocol runs, use the interface
command in area configuration mode. To disable OSPF routing for interfaces, use the interface form of this
command.
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Command Default When you do not specify this command in configuration mode, OSPF routing for interfaces is not enabled.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the interface command to associate a specific interface with an area. The interface remains associated
with the area even when the IP address of the interface changes.
ospf read,
write
Examples The following example shows how the OSPF routing process 109 defines four OSPF areas (0, 2, 3,
and 10.9.50.0), and associates an interface with each area:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 4/0/0/3
!
RP/0/RSP0/CPU0:router(config-ospf)# area 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1013
OSPF Commands
interface (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1014
OSPF Commands
log adjacency changes (OSPF)
Syntax Description detail Provides all (DOWN, INIT, 2WAY, EXSTART, EXCHANGE, LOADING, FULL) adjacency
state changes.
Command Default The router sends a syslog message when the state of an OSPF neighbor changes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the log adjacency changes command to display high-level changes to the state of the peer relationship.
Configure this command if you want to know about OSPF neighbor changes.
ospf read,
write
Examples The following example shows how to configure the software to send a syslog message for any OSPF
neighbor state changes:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# log adjacency changes detail
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1015
OSPF Commands
loopback stub-network
loopback stub-network
To enable advertising loopback as stub networks, use the loopback stub-network command in an appropriate
configuration mode. To disable advertising loopback as stubnetworks, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In the interface submode, the command can be enabled only on loopback interfaces.
Examples The following example shows how to enable advertising loopback as a stub network, under OSPF
interface configuration:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1016
OSPF Commands
lpts punt excessive-flow-trap penalty-timeout ospf
Syntax Description timeout The penalty timeout value for the ospf protocol in minutes. It is the period of time at which ospf
bad flow remains to be in bad actor state.
Value ranges from 1 to 1000.
Usage Guidelines You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
If the penalty-timeout value for ospf is configured as 20, then ospf packets are dropped for 20 minutes.
lpts read
basic-services read-write
Examples This example shows to set penalty time out for OSPF bad actor:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1017
OSPF Commands
max-lsa
max-lsa
To limit the number of nonself-generated link-state advertisements (LSAs) that an Open Shortest Path First
(OSPF) routing process can keep in the OSPF link-state database (LSDB), use the max-lsa command in
router configuration mode. To remove the limit of non self-generated LSAs that an OSPF routing process can
keep in the OSPF LSDB, use the no form of this command.
max-lsa max [threshold] [warning-only] [ignore-time value] [ignore-count value] [reset-time value]
no max-lsa max [threshold] [warning-only] [ignore-time value] [ignore-count value] [reset-time
value]
Syntax Description max Maximum number of nonself-generated LSAs the OSPF process can keep in the
OSPF LSBD.
threshold (Optional) The percentage of the maximum LSA number, as specified by the
maximum-number argument, at which a warning message is logged. The default is
75 percent.
warning-only (Optional) Specifies that only a warning message is sent when the maximum limit
for LSAs is exceeded. Disabled by default.
ignore-time value (Optional) Specifies the time, in minutes, to ignore all neighbors after the maximum
limit of LSAs has been exceeded. The default is 5 minutes.
ignore-count value (Optional) Specifies the number of times the OSPF process can consecutively be
placed into the ignore state. The default is 5 times.
reset-time value (Optional) Specifies the time, in minutes, after which the ignore count is reset to
zero. The default is 2 times ignore-time .
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This command allows you to protect the OSPF routing process from the large number of received LSAs that
can result from a misconfiguration on another router in the OSPF domain (for example, the redistribution of
a large number of IP prefixes to OSPF).
When this feature is enabled, the router keeps count of the number of all received (nonself-generated) LSAs.
When the configured threshold value is reached, an error message is logged. When the configured max
number of received LSAs is exceeded, the router stops accepting new LSAs.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1018
OSPF Commands
max-lsa
If the count of received LSAs is higher than the configured max number after one minute, the OSPF process
disables all adjacencies in the given context and clears the OSPF database. This state is called the ignore state.
In this state, all OSPF packets received on all interfaces belonging to the OSPF instance are ignored and no
OSPF packets are generated on its interfaces. The OSPF process remains in the ignore state for the duration
of the configured ignore-time . When the ignore-time expires, the OSPF process returns to normal operation
and starts building adjacencies on all its interfaces.
To prevent the OSPF instance from endlessly oscillating between its normal state and the ignore state, as a
result of the LSA count immediately exceeding the max number again after it returns from the ignore state,
the OSPF instance keeps a count of how many times it has been in the ignore state. This counter is called the
ignore-count . If the ignore-count exceeds its configured value, the OSPF instance remains in the ignore
state permanently.
To return the OSPF instance to its normal state, you must issue the clear ip ospf command. The ignore-count
is reset to zero if the LSA count does not exceed the max number again during the time configured by the
reset-time keyword.
If you use the warning-only keyword, the OSPF instance never enters the ignore state. When LSA count
exceeds the max number, the OSPF process logs an error message and the OSPF instance continues in its
normal state operation.
ospf read,
write
Examples The following example shows how to configure the OSPF instance to accept 12000 nonself-generated
LSAs in the global routing table, and 1000 nonself-generated LSAs in VRF V1.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 0
RP/0/RSP0/CPU0:router(config-ospf)# max-lsa 12000
RP/0/RSP0/CPU0:router(config-ospf)# vrf V1
RP/0/RSP0/CPU0:router(config-ospf)# max-lsa 1000
The following example shows how to display the current status of the OSPF instance:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1019
OSPF Commands
max-lsa
show ospf, on page 1101 Displays general information about Open Shortest Path First (OSPF) routing
processes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1020
OSPF Commands
max-metric
max-metric
To configure the Open Shortest Path First (OSPF) protocol to signal other networking devices not to prefer
the local router as an intermediate hop in their shortest path first (SPF) calculations, use the max-metric
command in router configuration mode. To disable this function, use the no form of this command.
Syntax Description router-lsa Always originates router link-state advertisements (LSAs) with the maximum
metric.
external-lsa overriding (Optional) Overrides the external-lsa metric with the max-metric value.The
metric overriding metric argument specifies the number of in-summary-LSAs. The
range is 1 to 16777215>. The default is 16711680.
include-stub (Optional) Advertises stub links in router-LSA with the max-metric value
(0xFFFF).
on-proc-migration time (Optional) Sets the maximum metric temporarily after a process migration to
originate router-LSAs with the max-metric value. The time range is 5 to 86400
seconds.
on-proc-restart time (Optional) Sets the maximum metric temporarily after a process restart to
originate router-LSAs with the max-metric value. The time range is 5 to 86400
seconds.
on-startup time (Optional) Sets the maximum metric temporarily after a reboot to originate
router-LSAs with the max-metric value. The time range is 5 to 86400 seconds.
on-switchover time (Optional) Sets the maximum metric temporarily after a switchover to originate
router-LSAs with the max-metric value. The time range is 5 to 86400 seconds.
Note OSPF will not populate maximum metric on the router's generated
LSAs, when the OSPF routing process is configured to support
Nonstop Routing (NSR) or Nonstop Forwarding/Graceful restart
(NSF/GR).
wait-for-bgp (Optional) Causes OSPF to originate router LSAs with the maximum metric
and allows Border Gateway Protocol (BGP) to decide when to start originating
router LSAs with a normal metric instead of the maximum metric.
Command Default Router LSAs are originated with normal link metrics.
overriding-metric :16711680
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1021
OSPF Commands
max-metric
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the max-metric command to cause the software to originate router LSAs with router link metrics set to
LSInfinity (0XFFFF). This feature can be useful in Internet backbone routers that run both OSPF and BGP
because OSPF converges more quickly than BGP and may begin attracting traffic before BGP has converged,
resulting in dropped traffic.
If this command is configured, the router advertises its locally generated router LSAs with a metric of 0XFFFF.
This action allows the router to converge but not attract transit traffic if there are better, alternative paths
around this router. After the specified announce-time value or notification from BGP has expired, the router
advertises the local router LSAs with the normal metric (interface cost).
If this command is configured with the on-startup keyword, then the maximum metric is temporarily set
only after reboot is initiated. If this command is configured without the on-startup keyword, then the
maximum metric is permanently used until the configuration is removed.
If the include-stub keyword is enabled, the stub-links in the router LSA will be sent with the max-metric. If
the summary-lsa keyword is enabled, all self-generated summary LSAs will have a metric set to 0xFF0000,
unless the metric value is specified with the max-metric value parameter. If the external-lsa keyword is
enabled, all self-generated external LSAs will have a metric set to 0xFF0000, unless the metric value is
specified with the max-metric value parameter.
This command might be useful when you want to connect a router to an OSPF network, but do not want real
traffic flowing through it if there are better, alternative paths. If there are no alternative paths, this router still
accepts transit traffic as before.
Some cases where this command might be useful are as follows:
• During a router reload, you prefer that OSPF wait for BGP to converge before accepting transit traffic.
If there are no alternative paths, the router still accepts transit traffic.
• A router is in critical condition (for example, it has a very high CPU load or does not have enough memory
to store all LSAs or build the routing table).
• When you want to gracefully introduce or remove a router to or from the network.
• When you have a test router in a lab, connected to a production network.
Note For older OSPF implementations (RFC 1247), router links in received router LSAs with a metric and cost of
LSInfinity are not used during SPF calculations. Hence, no transit traffic is set to the routers originating such
router LSAs.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1022
OSPF Commands
max-metric
ospf read,
write
Examples The following example shows how to configure OSPF to originate router LSAs with the maximum
metric until BGP indicates that it has converged:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# max-metric router-lsa on-startup wait-for-bgp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1023
OSPF Commands
maximum interfaces (OSPF)
VRF configuration
Release 4.1.1 The range for number of interfaces was changed to 1 to 4294967295 from 1 to 1024. The
default number of interfaces was changed to 1024 from 255.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum interface command to increase or decrease the limit on the number of interfaces configured
for an OSPF process.
You cannot configure a limit lower than the number of interfaces currently configured for the OSPF process.
To lower the limit, remove interfaces from the OSPF configuration until the number of configured interfaces
is at or below the desired limit. You may then apply the new, lower limit.
ospf read,
write
Examples This example shows how to configure a maximum interface limit of 1500 on a router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# maximum interfaces 1500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1024
OSPF Commands
maximum interfaces (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1025
OSPF Commands
maximum paths (OSPF)
Syntax Description maximum-routes-number Maximum number of parallel routes that OSPF can install in a routing table. Range
is 1 to 64.
Note The maximum number of paths that can be configured is 64.
Command Default The default value for maximum-paths depends on the platform supported maximum-paths value.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The default value for maximum-path depends on the platform supported maximum-path value. Any custom
value you define for the maximum-path parameter must be within the maximum value supported by platform.
The configuration will be rejected if the value you have specified is more then what the platform supports.
When the maximum number of parallel routes is reduced, all existing paths are pruned and paths reinstalled
at the new maximum number. During this route-reduction period, you may experience some packet loss for
a few seconds. This may impact route traffic.
ospf read,
write
Examples The following example shows how to allow a maximum of two paths to a destination:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1026
OSPF Commands
maximum paths (OSPF)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# maximum paths 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1027
OSPF Commands
maximum redistributed-prefixes (OSPF)
threshold-value (Optional) Threshold value (as a percentage) at which to generate a warning message.
Range is 1 to 100.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum redistributed-prefixes command to increase or decrease the maximum number of
prefixes (also referred to as routes) redistributed for an OSPF process.
If the maximum value is less than the existing number of routes, existing routes remain configured, but no
new routes are redistributed.
ospf read,
write
Examples The following example shows how to configure a maximum number of routes that can be redistributed
for an OSPF routing process:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1028
OSPF Commands
maximum redistributed-prefixes (OSPF)
show ospf routes, on page 1144 Displays the OSPF topology table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1029
OSPF Commands
message-digest-key
message-digest-key
To specify a key used with Open Shortest Path First (OSPF) Message Digest 5 (MD5) authentication, use the
message-digest-key command in the appropriate mode. To remove an old MD5 key, use the no form of
this command.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the message digest
key parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the message digest key
parameter specified for the process.
If this command is not specified at any level, then OSPF MD5 authentication is disabled.
Area configuration
Router configuration
Virtual-link configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Usually, one key individual interface is used to generate authentication information when packets are sent
and to authenticate incoming packets. The same key identifier on the neighbor router must have the same key
value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1030
OSPF Commands
message-digest-key
For authentication to be enabled, you must configure the message-digest-key command together with the
authentication command and its message-digest keyword. Both the message-digest-key and
authentication commands can be inherited from a higher configuration level.
The process of changing keys is as follows. Suppose the current configuration is:
The system assumes its neighbors do not have the new key yet, so it begins a rollover process. It sends multiple
copies of the same packet, each authenticated by different keys. In this example, the system sends out two
copies of the same packet—the first one authenticated by key 100 and the second one authenticated by key
101.
Rollover allows neighboring routers to continue communication while the network administrator is updating
them with the new key. Rollover stops after the local system finds that all its neighbors know the new key.
The system detects that a neighbor has the new key when it receives packets from the neighbor authenticated
by the new key.
After all neighbors have been updated with the new key, the old key should be removed. In this example, you
would enter the following:
interface ethernet 1
no ospf message-digest-key 100
Note The MD5 key is always stored in encrypted format on the router. The clear and encrypted keywords inform
the router whether the value that is entered is encrypted or unencrypted.
ospf read,
write
Examples The following example shows how to set a new key 19 with the password 8ry4222 :
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1031
OSPF Commands
message-digest-key
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# area 0
authentication (OSPF), on page 957 Enables plain text, MD5 authentication, or null authentication for an
OSPF interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1032
OSPF Commands
mpls ldp auto-config (OSPF)
Area configuration
Router configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to enable LDP-IGP interface automatic configuration:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf o1
RP/0/RSP0/CPU0:router(config-ospf)# mpls ldp auto-config
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1033
OSPF Commands
mpls ldp sync (OSPF)
Syntax Description disable (Optional) Disables MPLS LDP synchronization from within the OSPF interface and area
configuration submodes only. For the OSPF router configuration mode, use the no form of the
command.
Area configuration
Router configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf o1
RP/0/RSP0/CPU0:router(config-ospf)# mpls ldp sync
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1034
OSPF Commands
mpls traffic-eng (OSPF)
mpls traffic-eng
no mpls traffic-eng
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must configure the mpls traffic-eng command for OSPF to support MPLS traffic engineering. OSPF
provides the flooding mechanism that is used to flood TE link information.
We recommend that you configure the mpls traffic-eng router-id command instead of using the router-id
command in global configuration mode.
OSPF support for MPLS TE is a component of the overall MPLS TE feature. Other MPLS TE software
components must also be configured for this feature to be fully supported.
ospf read,
write
Examples The following example shows how to associate loopback interface 0 with area 0, and area 0 is declared
to be an MPLS area:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# router-id 10.10.10.10
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1035
OSPF Commands
mpls traffic-eng (OSPF)
capability opaque disable, on page 963 Controls the OSPF opaque LSA support capability.
mpls traffic-eng multicast-intact (OSPF), on Specifies that the traffic engineering router identifier for the
page 1039 node is the IP address associated with a given interface.
router-id (OSPF), on page 1088 Configures a router ID for the OSPF process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1036
OSPF Commands
mpls traffic-eng igp-intact (OSPF)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The OSPF protocol adds both tunnel next-hops (igp-shortcuts) and IPv4 next-hops to the next-hop list in the
Routing Information Base (RIB), until it reaches the maximum number of paths. When IGP-intact is enabled,
it ensures that the Routing Information Base (RIB) always has at least one IPv4 next-hop present in the list
of next-hops when the number of paths is at maximum.
Note IGP-intact should be used only when Policy-Based Tunnel Selection (PBTS) is in use.
Configure IGP-intact only when Policy-Based Tunnel Selection (PBTS) is in use. This ensures that at least
one IPv4 next-hop is available for the default Differentiated Services Code Point (DSCP) traffic class. It also
prevents traffic loss for other DSCP traffic classes by diverting such traffic to an IPv4 next-hop when the
corresponding tunnel is unavailable for forwarding.
ospf read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# mpls traffic-eng igp-intact
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1037
OSPF Commands
mpls traffic-eng igp-intact (OSPF)
maximum paths (OSPF), on page 1026 Configures the maximum number of parallel routes that the Open
Shortest Path First (OSPF) protocol can support.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1038
OSPF Commands
mpls traffic-eng multicast-intact (OSPF)
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPF support for MPLS TE is a component of the overall MPLS TE feature. Other MPLS TE software
components must also be configured for this feature to be fully supported.
ospf read,
write
Examples The following example shows how to enable publishing of multicast-intact paths to RIB:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# mpls traffic-eng multicast-intact
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1039
OSPF Commands
mpls traffic-eng ldp-sync-update (OSPF)
Interface configuration
Area configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Whenever there is a change in the network (link failure, addition, new nodes, cost change or router cost out),
the Type 1 and Type 10 LSA should be in sync. In most of the cases Type 1 and Type 10 are in sync, however
it was observed that when IGP-LDP sync is not established, the Type 1 indicates the high cost while the Type
10 shows the normal cost. Use the mpls traffic-eng ldp-sync-update command to synchronize Label
Distribution Protocol (LDP)-OSPF Type 1 and Type 10 link-state advertisement (LSA).
ospf read,
write
Examples The following example shows how to enable LDP-IGP OSPF Type 1 and Type 10 link-state
advertisement (LSA) synchronization:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf o1
RP/0/RSP0/CPU0:router(config-ospf)# mpls traffic-eng ldp-sync-update
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1040
OSPF Commands
mpls traffic-eng router-id (OSPF)
Syntax Description router-id The 32-bit router ID value specified in four-part, dotted-decimal notation (must be in
the valid IP address range of 0.0.0.0 to 255.255.255.255).
type Interface type. For more information, use the question mark (?) online help function.
Command Default If this command is specified in router configuration mode, then the traffic engineering router identifier for
the node is the IP address associated with a given interface.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This identifier of the router acts as a stable IP address for the traffic engineering configuration. This IP address
is flooded to all nodes. For all traffic engineering tunnels originating at other nodes and ending at this node,
you must set the tunnel destination to the traffic engineering router identifier of the destination node, because
that is the address that the traffic engineering topology database at the tunnel head uses for its path calculation.
Note We recommend that loopback interfaces be used for Multiprotocol Label Switching traffic engineering (MPLS
TE), because they are more stable than physical interfaces.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1041
OSPF Commands
mpls traffic-eng router-id (OSPF)
ospf read,
write
Examples The following example shows how to specify the traffic engineering router identifier as the IP address
associated with loopback interface 0:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# mpls traffic-eng router-id loopback 0
mpls traffic-eng (OSPF), on page 1035 Configures an OSPF area for MPLS TE.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1042
OSPF Commands
mtu-ignore (OSPF)
mtu-ignore (OSPF)
To prevent Open Shortest Path First (OSPF) from checking whether neighbors are using the same maximum
transmission unit (MTU) on a common interface when exchanging database descriptor (DBD) packets, use
the mtu-ignore command in the appropriate mode. To reset to default, use the no form of this command.
Syntax Description disable (Optional) Enables checking for whether OSPF neighbors are using the MTU on a common
interface.
enable (Optional) Disables checking for whether OSPF neighbors are using the MTU on a common
interface.
Command Default The default is mtu-ignore with no keywords, which disables MTU checking.
If this command is not specified in interface configuration mode,
then the interface adopts the MTU ignore parameter specified by the area.
If this command is not specified in area configuration mode,
then the interface adopts the MTU ignore parameter specified for the process.
If this command is not specified at any level,
then OSPF checks the MTU received from neighbors when exchanging DBD packets.
Area configuration
Router configuration
VRF configuration
Multi-area configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPF checks whether OSPF neighbors are using the same MTU on a common interface. This check is
performed when neighbors exchange DBD packets. If the receiving MTU in the DBD packet is higher than
the MTU configured on the incoming interface, OSPF adjacency is not established.
The keywords, disable and enable , do not need to be used. If no keywords are used, the mtu-ignore
command disables MTU checking. You can then use the no mtu-ignore command to activate MTU checking.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1043
OSPF Commands
mtu-ignore (OSPF)
ospf read,
write
Examples The following example shows how to disable MTU mismatch detection on receiving DBD packets:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# mtu-ignore
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1044
OSPF Commands
multi-area-interface
multi-area-interface
To enable multiple adjacencies for different Open Shortest Path First (OSPF) areas and enter multi-area
interface configuration mode, use the multi-area-interface command in the area configuration mode. To
reset to the default, use the no form of this command.
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the multi-area-interface command to enable area border routers (ABRs) to establish multiple adjacencies
for different OSPF areas.
Each multiple area adjacency is announced as a point-to-point unnumbered link in the configured area. This
point-to-point link provides a topological path for that area. The first or primary adjacency using the link
advertises the link consistent with draft-ietf-ospf-multi-area-adj-06.txt.
You can configure multi-area adjacency on any interface where only two OSF speakers are attached. In the
case of native broadcast networks, the interface must be configured as an OPSF point-to-point type using the
network point-to-point command to enable the interface for a multi-area adjacency.
ospf read,
write
Examples The following example shows how to enable multiple area adjacency for OSPF 109:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1045
OSPF Commands
multi-area-interface
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# area 1
RP/0/RSP0/CPU0:router(config-ospf-ar)# multi-area-interface GigabitEthernet 0/1/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-mif)# ?
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1046
OSPF Commands
neighbor (OSPF)
neighbor (OSPF)
To configure Open Shortest Path First (OSPF) routers interconnecting to nonbroadcast networks, use the
neighbor command in interface configuration mode. To remove a configuration, use the no form of this
command.
cost number (Optional) Assigns a cost to the neighbor, in the form of an integer from 1 to 65535.
Neighbors with no specific cost configured assume the cost of the interface, based
on the cost command. On point-to-multipoint interfaces, cost number is the only
keyword and argument combination that works. The cost keyword does not apply
to nonbroadcast multiaccess (NBMA) networks.
priority number (Optional) Specifies an 8-bit number indicating the router priority value of the
nonbroadcast neighbor associated with the IP address specified. The priority
keyword does not apply to point-to-multipoint interfaces.
poll-interval seconds (Optional) Specifies an unsigned integer value (in seconds) reflecting the poll
interval. RFC 1247 recommends that this value be much larger than the hello
interval. The poll-interval keyword does not apply to point-to-multipoint interfaces.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must include one neighbor entry in the software configuration for each known nonbroadcast network
neighbor. The neighbor address must be on the primary address of the interface.
If a neighboring router has become inactive (hello packets have not been received for the router dead interval
period), it may still be necessary to send hello packets to the dead neighbor. These hello packets are sent at a
reduced rate called the poll interval.
When the router starts up, it sends only hello packets to those routers with nonzero priority; that is, routers
that are eligible to become designated routers (DRs) and backup designated routers (BDRs). After the DR
and BDR are selected, the DR and BDR start sending hello packets to all neighbors to form adjacencies.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1047
OSPF Commands
neighbor (OSPF)
To filter all outgoing OSPF link-state advertisement (LSA) packets for the neighbor, use the neighbor
database-filter all out command.
ospf read,
write
Examples The following example shows how to declare a router at address 172.16.3.4 on a nonbroadcast
network, with a priority of 1 and a poll interval of 180 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet1/0/0/3
RP/0/RSP0/CPU0:router(config-if)# ip address 172.16.3.10 255.255.255.0
neighbor database-filter all out, on page 1049 Filters all outgoing LSAs to an OSPF neighbor.
network (OSPF), on page 1050 Configures the OSPF network type to a type other than the
default for a given medium.
priority (OSPF), on page 1066 Sets the router priority, which helps determine the designated
router for this network.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1048
OSPF Commands
neighbor database-filter all out
Syntax Description ip-address IP address of the neighbor to which outgoing LSAs are blocked.
Command Default Instead of all outgoing LSAs being filtered to the neighbor, they are flooded to the neighbor.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the neighbor database-filter all out command to filter all outgoing OSPF LSA packets during
synchronization and flooding for point-to-multipoint neighbors on nonbroadcast networks. More neighbor
options are available with the neighbor command.
ospf read,
write
Examples The following example shows how to prevent flooding of OSPF LSAs from point-to-multipoint
networks to the neighbor at IP address 10.2.3.4:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet1/0/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# neighbor 10.2.3.4 database-filter all out
neighbor (OSPF), on page 1047 Configures OSPF routers interconnecting to nonbroadcast networks.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1049
OSPF Commands
network (OSPF)
network (OSPF)
To configure the Open Shortest Path First (OSPF) network type to a type other than the default for a given
medium, use the network command in the appropriate mode. To return to the default value, use the no
form of this command.
non-broadcast (Optional) Sets the point-to-multipoint network to be nonbroadcast. If you use this
keyword, the neighbor command is required.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the network
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the network parameter
specified for the process.
If this command is not specified at any level, then the OSPF network type is the default of the given medium.
GigabitEthernt and TenGigEthernet interfaces default to broadcast.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the network command to configure broadcast networks as NBMA networks when, for example, routers
in your network do not support multicast addressing.
Configuring NBMA networks as either broadcast or nonbroadcast assumes that there are virtual circuits from
every router to every router or fully meshed network. However, there are other configurations where this
assumption is not true; for example, a partially meshed network. In these cases, you can configure the OSPF
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1050
OSPF Commands
network (OSPF)
network type as a point-to-multipoint network. Routing between two routers that are not directly connected
go through the router that has virtual circuits to both routers.
If this command is issued on an interface that does not allow it, this command is ignored.
OSPF has two features related to point-to-multipoint networks. One feature applies to broadcast networks;
the other feature applies to nonbroadcast networks:
• On point-to-multipoint, broadcast networks, you can use the neighbor command, and you must specify
a cost to that neighbor.
• On point-to-multipoint, nonbroadcast networks, you must use the neighbor command to identify
neighbors. Assigning a cost to a neighbor is optional.
ospf read,
write
Examples The following example shows how to configure the OSPF network as a nonbroadcast network:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# network non-broadcast
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# neighbor 172.16.3.4 priority 1 poll-interval
180
neighbor (OSPF), on page 1047 Configures OSPF routers interconnecting to nonbroadcast networks.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1051
OSPF Commands
nsf (OSPF)
nsf (OSPF)
To configure nonstop forwarding (NSF) for the Open Shortest Path First (OSPF) protocol, use the nsf
command in the appropriate mode. To remove this command from the configuration file and restore the system
to its default condition, use the no form of this command.
enforce global (Optional) Cancels NSF restart when non-NSF network device neighbors are detected.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The NSF feature allows for the forwarding of data packets to continue along known routes while routing
protocol information (such as OSPF) is being restored following a switchover.
Use the nsf command if the router is expected to perform NSF during restart. To experience the full benefits
of this feature, configure all neighboring routers with NSF.
When this command is used without the optional cisco enforce global keywords and non-NSF neighbors
are detected, the NSF restart mechanism aborts on the interfaces of those neighbors and functions properly
on others.
When this command is used with the optional cisco enforce global keywords and non-NSF neighbors are
detected, NSF restart is canceled for the entire OSPF process.
IETF graceful restart provides an NSF mechanism to allow data traffic to flow seamlessly with no packet
drops during the transient period when OSPF attempts to recover after a process restart or RP failover, within
the guidelines of RFC 3623.
By default, neighbors in helper mode listen to both the NSF Cisco- and NSF IETF-type LSAs. The nsf
command enables one type of mechanism that would undergo an RP failover or, anticipating an OSPF process
restart. If the cisco or ietf keyword is not entered, NSF is not enabled, irrespective of neighbors in listening
mode for both NSF Cisco and NSF IETF.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1052
OSPF Commands
nsf (OSPF)
ospf read,
write
Examples The following example shows how to cancel NSF restart for the entire OSPF process if non-NSF
neighbors are detected on any network interface during restart:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# nsf cisco enforce global
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1053
OSPF Commands
nsf flush-delay-time (OSPF)
Syntax Description seconds Length of time (in seconds) allowed for NSF external route queries. Range is 1 to 3600 seconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to configure the maximum time for NSF to learn external routes
for OSPF at 60 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# nsf flush-delay-time 60
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1054
OSPF Commands
nsf interval (OSPF)
Syntax Description seconds Length of time (in seconds) between consecutive restart attempts. Range is 90 to 3600 seconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When you use the nsf interval command, the OSPF process must be up for at least 90 seconds before OSPF
attempts to perform an NSF restart.
ospf read,
write
Examples The following example shows how to configure the minimum time between consecutive NSF restart
attempts at 120 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:routerr(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# nsf interval 120
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1055
OSPF Commands
nsf lifetime (OSPF)
Syntax Description seconds The length of time (in seconds) that routes are held in the RIB. Range is 90 to 3600 seconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When you use this command, the OSPF process must reconverge within the maximum length of time configured.
If the convergence exceeds this length of time, routes are purged from RIB and nonstop forwarding (NSF)
restart may fail.
ospf read,
write
Examples The following example shows how to configure the maximum lifetime for OSPF NSF at 120 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# nsf lifetime 120
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1056
OSPF Commands
nsr (OSPF)
nsr (OSPF)
To configure nonstop routing (NSR) for the Open Shortest Path First (OSPF) protocol, use the nsr command
in OSPF router configuration mode. To remove this command from the configuration file, use the no form
of this command.
nsr[disable]
no nsr[disable]
Syntax Description disable (Optional) Disables NSR for all VRFs in this process.
Release 6.0.0 This command was modified. NSR was enabled by default.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The NSR feature allows an OSPF process on the active RP to synchronize all necessary data and states with
the OSPF process on the standby RP. When the switchover happens, the OSPF process on the newly active
RP has all the necessary data and states to continue running and does not require any help from its neighbors.
ospf read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# nsr
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# nsr disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1057
OSPF Commands
nsr (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1058
OSPF Commands
nssa (OSPF)
nssa (OSPF)
To configure an area as a not-so-stubby area (NSSA), use the nssa command in area configuration mode.
To remove the NSSA distinction from the area, use the no form of this command.
Syntax Description no-redistribution (Optional) Imports routes only into the normal areas, but not into the NSSA
area, by the redistribute command when the router is an NSSA Area Border
Router (ABR).
default-information- (Optional) Generates a Type 7 default into the NSSA area. This keyword takes
originate effect only on an NSSA ABR or NSSA Autonomous System Boundary Router
(ASBR).
metric metric-value (Optional) Specifies the metric used for generating the default route. If you
omit a value and do not specify a value using the defaultmetric command,
the default metric value is 10. Range is 1 to 16777214.
metric-type type-value (Optional) Specifies the external link type associated with the default route
advertised into the OSPF routing domain. It can be one of the following values:
1—Type 1 external route
2—Type 2 external route
no-summary (Optional) Prevents an ABR from sending summary link advertisements into
the NSSA.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An NSSA does not flood Type 5 external LSAs from the core into the area, but can import autonomous system
external routes in a limited fashion within the area.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1059
OSPF Commands
nssa (OSPF)
ospf read,
write
Examples The following example shows how to configure area 1 as an NSSA area:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 1
RP/0/RSP0/CPU0:router(config-ospf-ar)# nssa
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1060
OSPF Commands
ospf name-lookup
ospf name-lookup
To configure the Open Shortest Path First (OSPF) protocol to look up Domain Name System (DNS) names,
use the ospf name-lookup command in global configuration mode. To disable this function, use the no
form of this command.
ospf name-lookup
no ospf name-lookup
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the ospf name-lookup command to easily identify a router when executing all OSPF show command
displays. The router is displayed by name rather than by its router ID or neighbor ID.
ospf read,
write
Examples The following example shows how to configure OSPF to identify a router by name:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# ospf name-lookup
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1061
OSPF Commands
packet-size (OSPF)
packet-size (OSPF)
To configure the size of Open Shortest Path First (OSPF) packets up to the size specified by the maximum
transmission unit (MTU), use the packet-size command in the appropriate configuration mode. To disable
this function and reestablish the default packet size, use the no form of this command.
packet-size bytes
no packet-size
Command Default If the command is not specified, the default packet size is either the interface IP MTU size (if that is lower
than 9000 bytes) or 9000 bytes.
Area configuration
Interface configuration
VRF configuration
Multi-area configuration
Release 3.9.0 The default packet size was changed to the lower interface IP MTU size or 9000 bytes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the packet-size command to customize the size of OSPF packets. The OSPF protocol compares the
packet size and the MTU size and uses the lower packet size value.
If the command is not configured, the default packet size is equal to the interface IP MTU size (if that is lower
than 9000 bytes) or 9000 bytes. For example, if the interface IP MTU size is 1500 bytes, OSPF uses packet
size of 1500 bytes on the interface because the byte size is lower than 9000 bytes. If the interface IP MTU
size is 9500 bytes, OSPF uses packet size of 9000 bytes on the interface because the byte size exceeds 9000
bytes. The interface IP MTU size depends on the interface and the platform. In most cases, the default interface
IP MTU value will be lower than 9000 bytes.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1062
OSPF Commands
packet-size (OSPF)
Examples The following example shows how to configure the packet size on an interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 1/0/0/2
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# packet-size 3500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1063
OSPF Commands
passive (OSPF)
passive (OSPF)
To suppress the sending of Open Shortest Path First (OSPF) protocol operation on an interface, use the passive
command in the appropriate mode. To remove the passive configuration, use the no form of this command.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the passive parameter
specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the passive parameter
specified for the process.
If this command is not specified at any level, then the passive parameter is disabled and OSPF updates are
sent on the interface.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPF routing information is neither sent nor received through the specified interface. The interface appears
as a stub network in the OSPF router (Type 1) link-state advertisement (LSA).
ospf read,
write
Examples The following example shows that GigabitEthernet interface 1/0/0/2 reduces OSPF updates because
passive mode is enabled; however, GigabitEthernet interface 0/1/0/3 receives normal OSPF traffic
flow:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1064
OSPF Commands
passive (OSPF)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet1/0/0/2
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# passive
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# exit
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet1/0/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# end
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1065
OSPF Commands
priority (OSPF)
priority (OSPF)
To set the router priority for an interface, which helps determine the designated router for an Open Shortest
Path First (OSPF) link, use the priority command in the appropriate mode. To return to the default value,
use the no form of this command.
priority value
no priority value
Syntax Description value 8-bit unsigned integer indicating the router priority value. Range is 0 to 255.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the priority parameter
specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the priority parameter
specified for the process.
If this command is not specified at any level, then the default priority is 1.
Area configuration
Router configuration
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When two routers attached to a network both attempt to become the designated router, the one with the higher
router priority takes precedence. If there is a tie, the router with the higher router ID takes precedence. A
router with a router priority set to zero is ineligible to become the designated router or backup designated
router. Router priority is configured only for interfaces to multiaccess networks (in other words, not
point-to-point networks).
This priority value is used when you configure the Open Shortest Path First (OSPF) protocol for nonbroadcast
networks using the neighbor command for OSPF.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1066
OSPF Commands
priority (OSPF)
Examples The following example shows that priority is set through the priority and neighbor commands
for Routers A and B and that the neighbor priority value must reflect that of the neighbor router:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-if)# ipv4 address 10.0.0.2 255.255.255.0
RP/0/RSP0/CPU0:router(config-if)# exit
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# network non-broadcast
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# priority 4
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# neighbor 10.0.0.1 priority 6
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet POS 0/2/0/1
RP/0/RSP0/CPU0:router(config-if)# ipv4 address 10.0.0.1 255.255.255.0
RP/0/RSP0/CPU0:router(config-if)# exit
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/2/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# network non-broadcast
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# priority 6
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# neighbor 10.0.0.2 priority 4
neighbor (OSPF), on page 1047 Configures OSPF routers interconnecting to nonbroadcast networks.
network (OSPF), on page 1050 Configures the OSPF network type to a type other than the default for a given
medium.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1067
OSPF Commands
protocol shutdown
protocol shutdown
To disable an instance of the Open Shortest Path First (OSPF) protocol so that it cannot form an adjacency
on any interface, use the protocol shutdown command in the router configuration mode. To reenable the
OSPF protocol, use the no form of this command.
protocol shutdown
no protocol shutdown
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the protocol shutdown command to disable the OSPF protocol for a specific routing instance without
removing any existing OSPF configuration parameters.
The OSPF protocol continues to run on the router and you can use the current OSPF configuration, but OSPF
does not form any adjacencies on any interface.
This command is similar to performing the no router ospf command.
ospf read,
write
Examples The following example shows how to disable the OSPF 1 instance:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospfv3 1
RP/0/RSP0/CPU0:router(config-ospf)# protocol shutdown
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1068
OSPF Commands
queue dispatch flush-lsa
Syntax Description count Maximum number of LSAs flushed per run. Range is 30 to 3000.
Command Default The default LSAs flushed per run is 150 (when the count is not configured).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to limit the number of LSAs flushed per run to 30:
Use the show ospf message-queue, on page 1129 command to see the queue dispatch values, peak
lengths, and limits.
queue dispatch incoming, on page 1071 Limits the number of continuous incoming events processed.
queue dispatch rate-limited-lsa, on page Sets the maximum number of rate-limited link-state
1073 advertisements (LSAs) processed per run.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1069
OSPF Commands
queue dispatch flush-lsa
Command Description
queue dispatch spf-lsa-limit, on page 1075 Limits the number of summary or external Type 3 to Type 7
link-state advertisements (LSAs) processed per shortest path
first (SPF) run.
queue limit, on page 1076 Sets the high watermark for incoming priority events.
show ospf message-queue, on page 1129 Displays the information about the queue dispatch values, peak
lengths, and limits.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1070
OSPF Commands
queue dispatch incoming
Syntax Description count Maximum number of continuous events processed. Range is 30 to 3000.
Command Default The default incoming count is 300 packets (when the count is not configured).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how limit the number of incoming packets processed to 500:
Use the show ospf message-queue, on page 1129 command to see the queue dispatch values, peak
lengths, and limits.
queue dispatch rate-limited-lsa, on page Sets the maximum number of rate-limited link-state
1073 advertisements (LSAs) processed per run.
queue dispatch spf-lsa-limit, on page 1075 Limits the number of summary or external Type 3 to Type 7
link-state advertisements (LSAs) processed per shortest path first
(SPF) run.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1071
OSPF Commands
queue dispatch incoming
Command Description
queue limit, on page 1076 Sets the high watermark for incoming priority events.
show ospf message-queue, on page 1129 Displays the information about the queue dispatch values, peak
lengths, and limits.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1072
OSPF Commands
queue dispatch rate-limited-lsa
Syntax Description count Maximum number of rate-limited LSAs processed per run. Range is 30 to 3000.
Command Default The default number of rate-limited LSAs processed per run is 300 (when this count is not configured).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to set the maximum number of rate-limited LSA (re-)originations
processed per run to 300:
queue dispatch incoming, on page 1071 Limits the number of continuous incoming events processed.
queue dispatch spf-lsa-limit, on page 1075 Limits the number of summary or external Type 3 to Type 7
link-state advertisements (LSAs) processed per shortest path first
(SPF) run.
queue limit, on page 1076 Sets the high watermark for incoming priority events.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1073
OSPF Commands
queue dispatch rate-limited-lsa
Command Description
show ospf message-queue, on page 1129 Displays the information about the queue dispatch values, peak
lengths, and limits.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1074
OSPF Commands
queue dispatch spf-lsa-limit
Syntax Description count Maximum number of continuous Type 3-4 and Type 5-7 LSAs processed per SPF in each scheduled
iteration within a single SPF run. Range is 30 to 3000.
Command Default The default number of Type 3-4 and Type 5-7 processed per run is 150 LSAs (when this command is not
configured).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to limit the number of continuous Type 3-4 and Type 5-7 LSAs
processed by SPF per scheduling run, to 100:
RP/0/RSP0/CPU0:router(config-ospf)# queue dispatch spf-lsa-limit 100
queue dispatch incoming, on page 1071 Limits the number of continuous incoming events processed.
queue dispatch rate-limited-lsa, on page 1073 Sets the maximum number of rate-limited link-state
advertisements (LSAs) processed per run
queue limit, on page 1076 Sets the high watermark for incoming priority events.
show ospf message-queue, on page 1129 Displays the information about the queue dispatch values, peak
lengths, and limits.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1075
OSPF Commands
queue limit
queue limit
To set the high watermark for incoming events by priority, use the queue limit in router configuration mode.
To return to the system default values, use the no form of this command.
Syntax Description high High watermark for incoming high-priority events (state-changing Hellos).
count Maximum number of events per queue. Events are dropped when the priority queue size exceeds
this value. Range is 1000 to 30000.
Command Default High watermark: 9500 (when the corresponding configuration is not present).
Medium watermark: 9000 (when the corresponding configuration is not present).
Low watermark: 8000 (when the corresponding configuration is not present).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Always keep the limits in the following order of priority:
Limit for High > Limit for Medium > Limit for Low
ospf read,
write
Examples The following examples show how to set the maximum number of events per queue:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1076
OSPF Commands
queue limit
queue dispatch incoming, on page 1071 Limits the number of continuous incoming events processed.
queue dispatch rate-limited-lsa, on page Sets the maximum number of rate-limited link-state
1073 advertisements (LSAs) processed per run.
queue dispatch spf-lsa-limit, on page 1075 Limits the number of summary or external Type 3 to Type 7
link-state advertisements (LSAs) processed per shortest path
first (SPF) run.
show ospf message-queue, on page 1129 Displays the information about the queue dispatch values, peak
lengths, and limits.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1077
OSPF Commands
range (OSPF)
range (OSPF)
To consolidate and summarize routes at an area boundary, use the range command in area configuration
mode. To disable this function, use the no form of this command.
advertise (Optional) Sets the address range status to advertise and generates a Type 3 summary
link-state advertisement (LSA).
not-advertise (Optional) Sets the address range status to DoNotAdvertise. The Type 3 summary LSA is
suppressed and the component networks remain hidden from other networks.
Command Default When this command is not specified for Area Border Routers (ABRs), routes at an area boundary are not
consolidated or summarized.
Advertise is the default.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the range command only with Area Border Router (ABRs). Use the command to consolidate or summarize
routes for an area. The result is that a single summary route is advertised to other areas by the ABR. Routing
information is condensed at area boundaries. External to the area, a single route is advertised for each address
range. This process is called route summarization .
Multiple range configurations specifying the range command can be configured. Thus, the OSPF protocol
can summarize addresses for many different sets of address ranges.
The summarized route uses the maximum cost of the routes assumed in the range.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1078
OSPF Commands
range (OSPF)
Examples The following example shows area 36.0.0.0 consisting of interfaces whose IP addresses have
“10.31.x.x” as the first two octets. The range command summarizes interfaces. Instead of advertising
eight networks individually, the single route 10.31.0.0 255.255.0.0 is advertised:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet 0/3/0/2
!
RP/0/RSP0/CPU0:router(config-ospf)# area 36.0.0.0
RP/0/RSP0/CPU0:router(config-ospf-ar)# range 10.31.0.0 255.255.0.0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/1/0/0
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/1/0/0
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/1/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/1/0/2
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/1/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/2/0/0
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/2/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/2/0/2
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# interface GigabitEthernet0/2/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# end
summary-prefix (OSPF), on page 1165 Creates aggregate addresses for routes being redistributed from another
routing protocol into the OSPF protocol.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1079
OSPF Commands
redistribute (OSPF)
redistribute (OSPF)
To redistribute routes from one routing domain into Open Shortest Path First (OSPF), use the redistribute
command in the appropriate mode. To remove the redistribute command from the configuration file and
restore the system to its default condition in which the software does not redistribute routes, use the no form
of this command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1080
OSPF Commands
redistribute (OSPF)
IP Static Routes
redistribute static [metric metric-value] [metric-type {1 | 2}] [route-policy policy-name] [tag
tag-value]
no redistribute static [metric metric-value] [metric-type {1 | 2}] [route-policy policy-name] [tag
tag-value]
process-id For the bgp keyword, an autonomous system number has the following ranges:
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format
is 1 to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is
1.0 to 65535.65535.
For the isis keyword, an IS-IS instance name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be
entered, but it is stored internally as a string.
For the ospf keyword, an OSPF instance name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be
entered, but it is stored internally as a string.
preserve-med (Optional) Preserves the Multi Exit Discriminator (MED) of BGP routes.
metric metric-value (Optional) Specifies the metric used for the redistributed route. Range is 1 to
16777214. Use a value consistent with the source protocol.
metric-type { 1 | 2 } (Optional) Specifies the external link type associated with the route advertised
into the OSPF routing domain. It can be one of two values:
• 1 —Type 1 external route
• 2 —Type 2 external route
tag tag-value (Optional) Specifies the value attached to each external route. This value is not
used by the OSPF protocol itself, but is carried in the external LSAs. Range is
0 to 4294967295.
route-policy policy-name (Optional) Specifies the identifier of a configured policy. A policy is used to
filter the importation of routes from this source routing protocol to OSPF.
connected Distributes routes that are established automatically by virtue of having enabled
IP on an interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1081
OSPF Commands
redistribute (OSPF)
l evel-1-2 (Optional) Distributes both Level 1 and Level 2 routes into other IP routing
protocols.
match { internal | (Optional) Specifies the criteria by which OSPF routes are redistributed into
external [1 | 2 ] | other routing domains. It can be one or more of the following:
nssa-external [ 1 | 2] }
• internal —Routes that are internal to a specific autonomous system (intra-
and inter-area OSPF routes).
• external [ 1 | 2 ]—Routes that are external to the autonomous system, but
are imported into OSPF as Type 1 or Type 2 external routes.
• nssa-external [ 1 | 2 ]—Routes that are external to the autonomous system,
but are imported into OSPF as Type 1 or Type 2 not-so-stubby area (NSSA)
external routes.
For the external and nssa-external options, if a type is not specified, then
both Type 1 and Type 2 are assumed.
If no match is specified, the default is no filtering.
VRF configuration
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Support was added for redistribution from directed-attached gateway redundancy (DAGR).
The keyword dagr was added.
The instance keywrod and instance-name argument were added for connected routes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1082
OSPF Commands
redistribute (OSPF)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note When redistributing routes (into OSPF) using both command keywords for setting or matching of attributes
and a route policy, the routes are run through the route policy first, followed by the keyword matching and
setting.
Redistributed routing information should always be filtered by the policy policy-name keyword and
argument. This filtering ensures that only those routes intended by the administrator are redistributed into
OSPF.
For information about routing policies, see the Routing Policy Commands on the Cisco ASR 9000 Series
Router module of Routing Command Reference for Cisco ASR 9000 Series Routers.
Whenever you use the redistribute or default-information originate (OSPF), on page 980 command to
redistribute routes into an OSPF routing domain, the router automatically becomes an ASBR. However, an
ASBR does not, by default, generate a default route into the OSPF routing domain.
When routes are redistributed between OSPF processes, no OSPF metrics are preserved.
When routes are redistributed into OSPF and no metric is specified with the metric keyword, OSPF uses 20
as the default metric for routes from all protocols except BGP routes, which get a metric of 1.
ospf read,
write
Examples The following example shows how to cause BGP routes to be redistributed into an OSPF domain:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 110
RP/0/RSP0/CPU0:router(config-ospf)# redistribute bgp 100
The following example shows how to redistribute the specified IS-IS process routes into an OSPF
domain. The IS-IS routes are redistributed with a metric of 100.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# redistribute isis 108 metric 100
In the following example, network 10.0.0.0 appears as an external link-state advertisement (LSA)
in OSPF 1:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet 0/1/0/1
RP/0/RSP0/CPU0:router(config-if)# ip address 10.0.0.0 255.0.0.0
!
RP/0/RSP0/CPU0:router(config)# interface GigabitEthernet 0/2/0/2
RP/0/RSP0/CPU0:router(config)# ip address 10.99.0.0 255.0.0.0
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1083
OSPF Commands
redistribute (OSPF)
default-information originate (OSPF), on page 980 Generates a default external route into an OSPF routing
domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1084
OSPF Commands
retransmit-interval (OSPF)
retransmit-interval (OSPF)
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the
Open Shortest Path First (OSPF) interface, use the retransmit-interval command in the appropriate mode.
To return to the default value, use the no form of this command.
retransmit-interval seconds
no retransmit-interval
Syntax Description seconds Time (in seconds) between retransmissions. It must be greater than the expected round-trip delay
between any two routers on the attached network. Range is 1 to 65535 seconds.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the retransmit
interval parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the retransmit interval
parameter specified for the process.
If this command is not specified at any level, then the default retransmit interval is 5 seconds.
Area configuration
Router configuration
Virtual-link configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When a router sends an LSA to its neighbor, it keeps the LSA until it receives the acknowledgment message.
If the router receives no acknowledgment, it resends the LSA.
The setting of this parameter should be conservative, or needless retransmission results. The value should be
larger for serial lines and virtual links.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1085
OSPF Commands
retransmit-interval (OSPF)
ospf read,
write
Examples The following example shows how to set the retransmit interval value to 8 seconds in interface
configuration mode:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/2/0/1
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# retransmit-interval 8
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1086
OSPF Commands
route-policy (OSPF)
route-policy (OSPF)
To specify a routing policy to filter Type 3 link-state advertisements (LSA), use the route-policy command
in area configuration mode. To disable the routing policy, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-policy command to specify an OSPF routing policy for an inbound or outbound route. The
policy can be used to filter routes or modify route attributes.
ospf read,
write
Examples The following example shows how to specify an OSPF route policy for inbound routes in area 0:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-area)# route-policy area0_in in
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1087
OSPF Commands
router-id (OSPF)
router-id (OSPF)
To configure a router ID for the Open Shortest Path First (OSPF) process, use the router-id command in
the appropriate mode. To cause the software to use the default method of determining the router ID, use the
no form of this command after clearing or restarting the OSPF process.
router-id router-id
no router-id router-id
Syntax Description router-id 32-bit router ID value specified in four-part, dotted-decimal notation.
Command Default If this command is not configured, the router ID is the highest IP version 4 (IPv4) address for an interface on
the router, with any loopback interface taking precedence.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
It is good practice to use the router-id command to explicitly specify a unique 32-bit numeric value for the
router ID. This action ensures that OSPF can function regardless of the interface address configuration. Clear
the OSPF process using the clear ospf process command or restart the OSPF process for the no router-id
command to take effect.
OSPF attempts to obtain a router ID in the following ways (in order of preference):
1. By default, when the OSPF process initializes, it checks if there is a router-id in the checkpointing database.
2. The 32-bit numeric value specified by the OSPF router-id command in router configuration mode. (This
value can be any 32-bit value. It is not restricted to the IPv4 addresses assigned to interfaces on this router,
and need not be a routable IPv4 address.)
3. The ITAL selected router-id.
4. The primary IPv4 address of an interface over which this OSPF process is running. The first interface
address in the OSPF interface is selected.
Note Unlike OSPF version 3, OSPF version 2 is guaranteed to have at least one interface with an IPv4 address
configured.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1088
OSPF Commands
router-id (OSPF)
ospf read,
write
Examples The following example shows how to assign the IP address of 172.20.10.10 to the OSPF process
109:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config-ospf)# router-id 172.20.10.10
clear ospf process, on page 964 Resets an OSPF router process without stopping and restarting it.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1089
OSPF Commands
router ospf
router ospf
To configure an Open Shortest Path First (OSPF) routing process, use the router ospf command in global
configuration mode. To terminate an OSPF routing process, use the no form of this command.
Syntax Description process-name Name that uniquely identifies an OSPF routing process. The process name is any
alphanumeric string no longer than 40 characters without spaces.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You can specify multiple OSPF routing processes in each router. Up to 10 processes can be configured. The
recommendation is not to exceed 4 OSPF processes.
All OSPF configuration commands must be configured under an OSPF routing process. For example, two of
these commands are the default-metric command and the router-id command.
ospf read,
write
rib read,
write
Examples The following example shows how to instantiate an OSPF routing process called 109:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1090
OSPF Commands
router ospf
Command Description
default-metric (OSPF), on page 982 Sets default metric values for routes redistributed from another protocol
into the OSPF protocol.
interface (OSPF), on page 1013 Defines the interfaces on which the OSPF protocol runs.
router-id (OSPF), on page 1088 Configures a router ID for the OSPF process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1091
OSPF Commands
security ttl (OSPF)
Syntax Description hops hops-number IP hops. Maximum number of hops allowed. Range is 1 to 254 hops.
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The security ttl command is used for the Generalized TTL Security Mechanism (GTSM) feature to prevent
network attacks.
During the act of receiving Link State Advertisement (LSA) from neighbors, network attacks can occur because
there are no checks that unicast or multicast packets are originating from a neighbor that is one hop away or
multiple hops away over virtual links.
For virtual links, OSPF packets travel multiple hops across the network; hence, the TTL value can be
decremented several times. For these type of links, a minimum TTL value must be allowed and accepted for
multiple-hop packets.
To filter network attacks originating from invalid sources traveling over multiple hops, the GTSM, RFC
3682, is used to prevent the attacks. GTSM filters link-local addresses and allows for only one-hop neighbor
adjacencies through the configuration of TTL value 255. The TTL value in the IP header is set to when OSPF
packets are originated and checked on the received OSPF packets against the default GTSM TTL value 255
or the user configured GTSM TTL value, blocking unauthorized OSPF packets originated from TTL hops
away.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1092
OSPF Commands
security ttl (OSPF)
Examples The following example shows how to set the security TTL for an interface:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# area 0
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet0/6/0/3
RP/0/RSP0/CPU0:router(config-ospf-ar-if)# security ttl 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1093
OSPF Commands
segment-routing prefix-sid-map advertise-local
Syntax Description advertise-local OSPF advertises the SRMS mapping entries that are locally configured.
Area configuration
ospf read,
write
Examples
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#ipv4 prefix-list foo
RP/0/RSP0/CPU0:router(config)#router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)#segment-routing prefix-sid-map advertise-local
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1094
OSPF Commands
segment-routing prefix-sid-map receive disable
Syntax Description receive Only remote SRMS mapping entries are used for SID calculation.
disable Disables OSPF to the client to use remote SRMS mapping entries received by flooding.
Area configuration
ospf read,
write
Examples
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)#segment-routing prefix-sid-map receive disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1095
OSPF Commands
segment-routing sr-prefer prefix-list
Note If ACL is used, OSPF signals preference of SR labels over LDP labels only for prefixes that match the ACL.
If ACL is not used, SR labels preference is signaled for all prefixes.
Area configuration
ospf read,
write
Examples
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#ipv4 prefix-list foo
RP/0/RSP0/CPU0:router(config)#router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# segment-routing sr-prefer prefix-list foo
area 0
interface Loopback0
prefix-sid index 1
!
interface GigabitEthernet0/0/0/0
!
interface GigabitEthernet0/2/0/0
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1096
OSPF Commands
segment-routing sr-prefer prefix-list
interface GigabitEthernet0/2/0/3
!
!
area 1
interface GigabitEthernet0/2/0/7
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1097
OSPF Commands
sham-link
sham-link
To configure an Open Shortest Path First OSPF sham link between two provider edge routers, use the
sham-link command in VRF area configuration mode. To terminate an (OSPF) sham link, use the no form
of this command.
Syntax Description source-address IP address of the local (source) sham-link endpoint specified in four-part,
dotted-decimal notation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the sham-link command to configure a point-to-point connection between two provider edge (PE)
routers creating an interconnect between two VPN sites (VPN backbone). Sham links are configured on PE
provider edge (PE) routers in a Multiprotocol Label Switching (MPLS) VPN backbone.
ospf read,
write
Examples The following example shows how to configure an OSPF sham link:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 109
RP/0/RSP0/CPU0:router(config_ospf)# vrf vrf_a
RP/0/RSP0/CPU0:router(config_ospf_vrf)# area 0
RP/0/RSP0/CPU0:router(config_ospf_vrf_ar)# sham-link 192.168.40.0 172.16.30.0
RP/0/RSP0/CPU0:router(config_ospf_vrf_ar_sl)# cost 23
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1098
OSPF Commands
sham-link
cost (OSPF), on page 971 Explicitly specifies the cost of the interface (network) for OSPF path calculation.
vrf (OSPF), on page 1178 Configures an OSPF VPN routing and forwarding (VRF) instance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1099
OSPF Commands
show lpts punt excessive-flow-trap ospf
Usage Guidelines You must be in a user group associated with a task group that includes the proper task IDs. The command
reference guides include the task IDs required for each command. If you suspect user group assignment is
preventing you from using a command, contact your AAA administrator for assistance.
lpts read
basic-services read-write
Examples This example shows to the details of bad actor identified for ospf protocol:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1100
OSPF Commands
show ospf
show ospf
To display general information about Open Shortest Path First (OSPF) routing processes, use the show ospf
command in EXEC mode.
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved values of the vrf-name argument.
OSPFv3
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 5.1 The output of the command was modified to include OSPFv3 status.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospf command to provide basic information about the OSPF processes running on the router.
Additional options provide in-depth information.
ospf read
Examples The following is sample output from the show ospf command:
RP/0/RSP0/CPU0:router#show ospf
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1101
OSPF Commands
show ospf
Field Description
Minimum LSA arrival Minimum elapsed time between accepting an update for the same
link-state advertisement (LSA).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1102
OSPF Commands
show ospf
Field Description
DCbitless...AS LSA Total number of Demand Circuit Type 5 and Type 11 LSAs.
DoNotAge...AS LSA Total number of Type 5 and Type 11 LSAs with the DoNotAge
bit set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1103
OSPF Commands
show ospf border-routers
Syntax Description process-name (Optional) OSPF process name. If this argument is included, only information for the
specified routing process is included.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved vrf-names.
router-id (Optional) Router ID associated with the border router. The value of the router-id
argument can be any 32-bit router ID value specified in four-part, dotted-decimal
notation. No default exists.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospf border-routers command to list all OSPF border routers visible to the specified processes
and to ascertain the OSPF topology of the router.
ospf read
Examples The following is sample output from the show ospf border-routers command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1104
OSPF Commands
show ospf border-routers
Field Description
GigabitEthernet 3/0/0/0 Packets destined for 172.16.1.53 are sent over GigabitEthernet interface 3/0/0/0.
ABR/ASBR Router type of the destination; it is either an Area Border Router (ABR) or
Autonomous System Boundary Router (ASBR) or both.
SPF 3 Internal number of the shortest path first (SPF) calculation that installs this route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1105
OSPF Commands
show ospf database
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1106
OSPF Commands
show ospf database
show ospf [process-name] [vrf {vrf-name | all}] [area-id] database [summary] [link-state-id]
show ospf [process-name] [vrf {vrf-name | all}] [area-id] database [summary] [link-state-id]
[internal] [adv-router [ip-address]]
show ospf [process-name] [vrf {vrf-name | all}] [area-id] database [summary] [link-state-id]
[internal] [self-originate] [link-state-id]
Syntax Description process-name (Optional) OSPF process name that uniquely identifies an OSPF routing process.
The process name is any alphanumeric string no longer than 40 characters. If this
argument is included, only information for the specified routing process is included.
vrf (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance.
vrf-name (Optional) Name of the OSPF VRF. The vrf-name argument can be specified as
an arbitrary string. The strings “default” and “all” are reserved VRF names.
asbr-summary (Optional) Displays information only about the Autonomous System Boundary
Router (ASBR) summary LSAs.
link-state-id (Optional) Portion of the Internet environment that is being described by the
advertisement. The value entered depends on the link-state type of the
advertisement. It must be entered in the form of an IP address.
When the link-state advertisement (LSA) is describing a network, the link-state-id
can take one of two forms:
• The network IP address (as in Type 3 summary link advertisements and in
autonomous system external link advertisements).
• A derived address obtained from the link-state ID.
Note Masking the link-state ID of a network link advertisement with the
subnet mask of the network yields the IP address of the network.
When the LSA is describing a router, the link-state ID is always the OSPF router
ID of the described router.
When an autonomous system external advertisement (LS Type = 5) is describing
a default route, its link-state ID is set to Default Destination (0.0.0.0).
self-originate (Optional) Displays only self-originated LSAs (from the local router).
database-summary (Optional) Displays how many of each type of LSA for each area there are in the
database and the total.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1107
OSPF Commands
show ospf database
nssa-external (Optional) Displays information only about the not-so-stubby area (NSSA) external
LSAs.
opaque-area (Optional) Displays information about the opaque Type 10 LSAs. Type 10 denotes
an area-local scope. Refer to RFC 2370 for more information on the opaque LSA
options.
opaque-as (Optional) Displays information about the opaque Type 11 LSAs. Type 11 denotes
that the LSA is flooded throughout the autonomous system.
opaque-link (Optional) Displays information about the opaque Type 9 LSAs. Type 9 denotes
a link-local scope.
Release 5.3.0 show ospf database opaque-area command is extended to display extended Link LSA
information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The various forms of the show ospf database command deliver information about different OSPF link-state
advertisements. This command can be used to examine the link-state database (LSD) and its contents. Each
router participating in an area having identical database entries pertaining to that area (with the exception of
LSAs that are being flooded). Numerous options (such as network and router ) are used to display portions
of the database.
ospf read
Examples The following is sample output from the show ospf database command when no arguments or
keywords are used:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1108
OSPF Commands
show ospf database
Field Description
The following is sample output from the show ospf database command with the asbr-summary
keyword:
LS age: 1463
Options: (No TOS-capability)
LS Type: Summary Links (AS Boundary Router)
Link State ID: 172.17.245.1 (AS Boundary Router address)
Advertising Router: 172.17.241.5
LS Seq Number: 80000072
Checksum: 0x3548
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1109
OSPF Commands
show ospf database
Length: 28
Network Mask: /0
TOS: 0 Metric: 1
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
The following is sample output from the show ospf database command with the external
keyword:
LS age: 280
Options: (No TOS-capability)
LS Type: AS External Link
Link State ID: 172.17.0.0 (External Network Number)
Advertising Router: 172.17.70.6
LS Seq Number: 80000AFD
Checksum: 0xC3A
Length: 36
Network Mask: 255.255.0.0
Metric Type: 2 (Larger than any link state path)
TOS: 0
Metric: 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1110
OSPF Commands
show ospf database
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Forward Address Forwarding address. Data traffic for the advertised destination is forwarded
to this address. If the forwarding address is set to 0.0.0.0, data traffic is
forwarded instead to the originator of the advertisement.
External Route Tag External route tag, a 32-bit field attached to each external route. This tag is
not used by the OSPF protocol itself.
The following is sample output from the show ospf database command with the network
keyword:
LS age: 1367
Options: (No TOS-capability)
LS Type: Network Links
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1111
OSPF Commands
show ospf database
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
The following is sample output, carrying Multiprotocol Label Switching traffic engineering (MPLS
TE) specification information, from the show ospf database command with the opaque-area
keyword and a link-state-id of adv-router:
LS age: 224
Options: (No TOS-capability, DC)
LS Type: Opaque Area Link
Link State ID: 1.0.0.0
Opaque Type: 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1112
OSPF Commands
show ospf database
Opaque ID: 0
Advertising Router: 172.20.1.12
LS Seq Number: 80000081
Checksum: 0xF659
Length: 132
Fragment number : 0
Number of Links : 1
The following is the sample output from the show ospf database opaque-area command displaying
the extended link LSA information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1113
OSPF Commands
show ospf database
SID : 24000
The following is sample output from the show ospf database command that displays a Type 10,
Router Information LSA:
LS age: 105
Options: (No TOS-capability, DC)
LS Type: Opaque Area Link
Link State ID: 4.0.0.0
Opaque Type: 4
Opaque ID: 0
Advertising Router: 3.3.3.3
LS Seq Number: 80000052
Checksum: 0x34e2
Length: 52
Fragment number: 0
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1114
OSPF Commands
show ospf database
Field Description
Fragment number Arbitrary value used to maintain multiple traffic engineering LSAs.
Capabilities Some router capabilities include stub router, traffic engineering, graceful
restart, and graceful restart helper.
PCE Discovery TLV PCE address and capability information is advertised in this TLV.
Inter-area default (RD-bit) PCE compute capabilities such as intra-area, inter-area, inter-area default,
inter-AS, inter-AS default and inter-layer.
Compute Preferences Order or preference of path computation that includes intra-area, inter-area,
inter-AS, and inter-layer preferences.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1115
OSPF Commands
show ospf database
The following is sample output from the show ospf database command with the router keyword:
LS age: 1176
Options: (No TOS-capability)
LS Type: Router Links
Link State ID: 172.23.21.6
Advertising Router: 172.23.21.6
LS Seq Number: 80002CF6
Checksum: 0x73B7
Length: 120
AS Boundary Router
Number of Links: 8
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1116
OSPF Commands
show ospf database
Field Description
The following is sample output from show ospf database command with the summary keyword:
LS age: 1401
Options: (No TOS-capability)
LS Type: Summary Links (Network)
Link State ID: 172.23.240.0 (Summary Network Number)
Advertising Router: 172.23.241.5
LS Seq Number: 80000072
Checksum: 0x84FF
Length: 28
Network Mask: /24
TOS: 0 Metric: 1
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1117
OSPF Commands
show ospf database
The following is sample output from show ospf database command with the database-summary
keyword:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1118
OSPF Commands
show ospf flood-list
show ospf [process-name] [vrf {vrf-name | all}] [area-id] flood-list [type interface-path-id]
Syntax Description process-name (Optional) OSPF process name that uniquely identifies an OSPF routing process. The
process name is any alphanumeric string no longer than 40 characters. If this argument
is included, only information for the specified routing process is included.
vrf (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance.
vrf-name (Optional) Name of the OSPF VRF. The vrf-name argument can be specified as an
arbitrary string. The strings “default” and “all” are reserved VRF names.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospf flood-list command to display LSAs in flood queue and queue length.
Flood list information is transient and normally the flood lists are empty.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1119
OSPF Commands
show ospf flood-list
Examples The following is sample output from the show ospf flood-list command for interface GigabitEthernet
3/0/0/0:
Field Description
Link state retransmission due in Length of time (in milliseconds) before next link-state transmission.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1120
OSPF Commands
show ospf interface
show ospf [process-name] [vrf {vrf-name | all}] [area-id] interface [brief] [type interface-path-id]
Syntax Description process-name (Optional) OSPF process name that uniquely identifies an OSPF routing process. The
process name is any alphanumeric string no longer than 40 characters. If this argument
is included, only information for the specified routing process is included.
vrf (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance.
vrf-name (Optional) Name of the OSPF VRF. The vrf-name argument can be specified as an
arbitrary string. The strings “default” and “all” are reserved VRF names.
type Interface type. For more information, use the question mark (?) online help function.
Release 5.3.0 Command output extended to display the status of topology independent fast reroute (TI-FRR)
on an interface.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1121
OSPF Commands
show ospf interface
Examples The following is sample output from the show ospf interface command which includes the topology
independent loop free alternates (TI LFA) related information:
Field Description
Process ID OSPF process ID, router ID, network type, and link-state cost.
Hello Number of seconds until next hello packet is sent over this interface.
Next 0 (0) /0 (0) Next area and autonomous system flood information, data pointer, and index.
Last flood scan time Time (in milliseconds) of last flood scan.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1122
OSPF Commands
show ospf interface
Field Description
Multi-area interface Multiple area interface information for the primary interface, such as count and
area/neighbor locations.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1123
OSPF Commands
show ospf mpls traffic-eng
show ospf [process-name] [vrf {vrf-name | all}] [area-id] [type interface-path-id] mpls traffic-eng
{link | fragment}
Syntax Description process-name (Optional) OSPF process name that uniquely identifies an OSPF routing process. The
process name is any alphanumeric string no longer than 40 characters. If this argument
is included, only information for the specified routing process is included.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved VRF names.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
link Provides detailed information about the links over which traffic engineering is supported
on the local router.
fragment Provides detailed information about the traffic engineering fragments on the local
router.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1124
OSPF Commands
show ospf mpls traffic-eng
Examples The following is sample output from the show ospf mpls traffic-eng command when the link
keyword is specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1125
OSPF Commands
show ospf mpls traffic-eng
Field Description
Maximum global pool reservable Maximum amount of bandwidth that is available for reservation in
bandwidth the global pool.
Maximum sub pool reservable Maximum amount of bandwidth that is available for reservation in
bandwidth the subpool.
Global pool unreserved BW Amount of unreserved bandwidth that is available in the global pool.
Sub pool unreserved BW Amount of unreserved bandwidth that is available in the subpool.
Affinity Bit Used by MPLS TE. Attribute values required for links carrying this
tunnel. A 32-bit dotted-decimal number. Valid values are from 0x0
to 0xFFFFFFFF, representing 32 attributes (bits), where the value
of an attribute is 0 or 1.
The following is sample output from the show ospf mpls traffic-eng command when the fragment
keyword is specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1126
OSPF Commands
show ospf mpls traffic-eng
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1127
OSPF Commands
show ospf mpls traffic-eng
Field Description
Maximum global pool reservable Maximum amount of bandwidth that is available for reservation in
bandwidth the global pool.
Maximum sub pool reservable Maximum amount of bandwidth that is available for reservation in
bandwidth the subpool.
Global pool unreserved BW Amount of unreserved bandwidth that is available in the global
pool.
Sub pool unreserved BW Amount of unreserved bandwidth that is available in the subpool.
Affinity Bit Used by MPLS TE. Attribute values required for links carrying this
tunnel. A 32-bit dotted-decimal number. Valid values are from 0x0
to 0xFFFFFFFF, representing 32 attributes (bits), where the value
of an attribute is 0 or 1.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1128
OSPF Commands
show ospf message-queue
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Examples The following is sample output from the show ospf message-queue command:
OSPF 1
Hello Input Queue:
Current queue length: 0
Event scheduled: 0
Total queuing failures: 0
Maximum length : 102
Pkts pending processing: 0
Limit: 5000
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1129
OSPF Commands
show ospf message-queue
TE Message Queue
Current queue length: 0
Total queuing failures: 0
Maximum length : 0
Field Description
Hello Input Queue This section provides statistics on the number of events and incoming packets
processed in the Hello (incoming packet) thread of the OSPF process.
Router Message Queue This section provides statistics on the events and messages processed in the Router
(primary) thread of the OSPF process.
TE Message Queue This section provides statistics on traffic-engineering events and messages received
by OSPF from TE (the te_control process). These events are processed in the Router
thread of the OSPF process.
Number of Dlink errors The number of enqueuing or dequeuing errors seen across all the linked-lists in the
OSPF process.
queue dispatch incoming, on page 1071 Limits the number of continuous incoming events processed.
queue dispatch rate-limited-lsa, on page Sets the maximum number of rate-limited link-state
1073 advertisements (LSAs) processed per run.
queue dispatch spf-lsa-limit, on page 1075 Limits the number of summary or external Type 3 to Type 7
link-state advertisements (LSAs) processed per shortest path
first (SPF) run.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1130
OSPF Commands
show ospf message-queue
Command Description
queue limit, on page 1076 Sets the high watermark for incoming priority events.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1131
OSPF Commands
show ospf neighbor
show ospf [process-name] [vrf {vrf-name | all}] [area-id] neighbor [{[type interface-path-id]
[neighbor-id] [detail] | area-sorted}]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved VRF names.
area-id (Optional) Area ID. If you do not specify an area, all areas are displayed.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
detail (Optional) Displays all neighbors given in detail (lists all neighbors).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1132
OSPF Commands
show ospf neighbor
Examples The following is sample output from the show ospf neighbor command showing two lines of
summary information for each neighbor:
Field Description
Dead time Time (in hh:mm:ss) that must elapse before OSPF declares the neighbor dead.
Neighbor is Amount of time (in hh:mm:ss) that the OSPF neighbor has been up.
up
The following is sample output showing summary information about the neighbor that matches the
neighbor ID:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1133
OSPF Commands
show ospf neighbor
Field Description
In the area Area and interface through which the OSPF neighbor is known.
Options Hello packet options field contents(E-bit only; possible values are 0 and 2; 2
indicates area is not a stub; 0 indicates area is a stub.)
Dead timer Time (in hh:mm:ss) to elapse before OSPF declares the neighbor dead.
Neighbor is up Amount of time (in hh:mm:ss) that the OSPF neighbor has been up.
Index Index and the remaining lines of this command give detailed information about
flooding information received from the neighbor.
If you specify the interface along with the neighbor ID, the software displays the neighbors that
match the neighbor ID on the interface, as in the following sample display:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1134
OSPF Commands
show ospf neighbor
Table 108: show ospf neighbor GigabitEthernet 0/3/0/2 192.168.199.137 Field Descriptions
Field Description
In the area Area and interface through which the OSPF neighbor is known.
Options Hello packet options field contents (E-bit only; possible values are 0 and 2; 2
indicates area is not a stub; 0 indicates area is a stub)
Dead timer Time (in hh:mm:ss) to elapse before OSPF declares the neighbor dead.
Neighbor is up Amount of time (in hh:mm:ss) that the OSPF neighbor has been up.
Index Index and the remaining lines of this command give detailed information about
flooding information received from the neighbor.
You can also specify the interface without the neighbor ID to show all neighbors on the specified
interface, as in the following sample display:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1135
OSPF Commands
show ospf neighbor
Field Description
Dead Time Time (in hh:mm:ss) to elapse before OSPF declares the neighbor dead.
Neighbor is up Time (in hh:mm:ss) that the OSPF neighbor has been up.
Options Hello packet options field contents (E-bit only; possible values are 0 and 2; 2
indicates area is not a stub; 0 indicates area is a stub)
Dead timer Time (in hh:mm:ss) to elapse before OSPF declares the neighbor dead.
Neighbor is up Amount of time (in hh:mm:ss) that the OSPF neighbor has been up.
Index Index and the remaining lines of this command give detailed information about
flooding information received from the neighbor.
The following samples are from output from the show ospf neighbor detail command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1136
OSPF Commands
show ospf neighbor
Field Description
In the area Area and interface through which the OSPF neighbor is known.
Options Hello packet options field contents. (E-bit only; possible values are 0 and 2; 2
indicates that the area is not a stub; 0 indicates that the area is a stub).)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1137
OSPF Commands
show ospf neighbor
Field Description
Dead timer Time (in hh:mm:ss) to elapse before OSPF declares the neighbor dead.
Neighbor is up Amount of time (in hh:mm:ss) that the OSPF neighbor has been up.
Index Index and the remaining lines of this command give detailed information about
flooding information received from the neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1138
OSPF Commands
show ospf request-list
show ospf [process-name] [vrf {vrf-name | all}] [area-id] request-list [type interface-path-id]
[neighbor-id]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospf command. If this argument is included, only information for
the specified routing process is displayed.
vrf (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance.
vrf-name (Optional) Name of the OSPF VRF. The vrf-name argument can be specified as an arbitrary
string. The strings “default” and “all” are reserved VRF names.
area-id (Optional) Area ID. If you do not specify an area, all areas are displayed.
type Interface type. For more information, use the question mark (?) online help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You might use this command when the databases of two neighboring routers are out of synchronization or if
the adjacency does not form between them. Adjacency means that the routers synchronize their databases
when they discover each other.
You can look at the list to determine if one router is trying to request a particular database update. Entries that
are suspended in the list usually indicate that updates are not being delivered. One possible reason for this
behavior is a maximum transmission unit (MTU) mismatch between the routers.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1139
OSPF Commands
show ospf request-list
You might also look at this list to make sure it is not corrupted. The list should refer to database entries that
actually exist.
Request list information is transient and normally the lists are empty.
ospf read
Examples The following is sample output from the show ospf request-list command:
Field Description
Neighbor Specific neighbor receiving the request list from the local router.
Interface Specific interface over which the request list is being sent.
Address Address of the interface over which the request list is being sent.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1140
OSPF Commands
show ospf request-list
Command Description
show ospf retransmission-list, on page 1142 Displays the first ten link-state entries in the retransmission list
that the local router sends to the specified neighbor over the
specified interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1141
OSPF Commands
show ospf retransmission-list
show ospf [process-name] [vrf {vrf-name | all}] [area-id] retransmission-list [type interface-path-id]
[neighbor-id]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved VRF names.
area-id (Optional) Area ID. If you do not specify an area, all areas are displayed.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You might use this command when the databases of two neighboring routers are out of synchronization or if
the adjacency is not forming between them. Adjacency means that the routers synchronize their databases
when they discover each other.
You can look at the list to determine if one router is trying to request a particular database update. Entries that
appear to be suspended in the list usually indicate that updates are not being delivered. One possible reason
for this behavior is a maximum transmission unit (MTU) mismatch between the routers.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1142
OSPF Commands
show ospf retransmission-list
You might also look at this list to make sure it is not corrupted. The list should refer to database entries that
actually exist.
Retransmission list information is transient, and normally the lists are empty.
ospf read
Examples The following is sample output from the show ospf retransmission-list command:
Field Description
Neighbor Specified neighbor receiving the retransmission list from the local router.
Interface Specified interface over which the retransmission list is being sent.
show ospf request-list, on page 1139 Displays the first ten link-state requests pending that the local router is
making to the specified neighbor and interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1143
OSPF Commands
show ospf routes
show ospf [process-name] [vrf {vrf-name | all}] routes [{connected | external | local}] [prefix mask]
[prefix/length] [multicast-intact]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved VRF names.
local (Optional) Displays the local routes redistributed from the Routing Information Base
(RIB).
/ length (Optional) Prefix length, which can be indicated as a slash (/) and number. For example,
/8 indicates that the first eight bits in the IP prefix are network bits. If length is used,
the slash is required.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines Use the show ospf routes command to display the OSPF private routing table (which contains only routes
calculated by OSPF). If there is something wrong with a route in the RIB, then it is useful to check the OSPF
copy of the route to determine if it matches the RIB contents. If it does not match, there is a synchronization
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1144
OSPF Commands
show ospf routes
problem between OSPF and the RIB. If the routes match and the route is incorrect, OSPF has made an error
in its routing calculation.
ospf read
O 2.2.2.2/32, metric 3
10.1.0.2, from 2.2.2.2, via GigabitEthernet0/0/0/7, path-id 1
Backup path: TI-LFA, P node: 4.4.4.4, Labels: 16004, 123
10.0.3.2, from 2.2.2.2, via GigabitEthernet0/0/0/3, protected bitmap 0x1
Attribues: Metric: 104, SRLG Disjoint
Field Description
O OSPF route.
N NSSA Type 1 or 2
2.2.2.2/32 Network and subnet mask to which the local router has a route.
from 2.2.2.2 Router ID 172.16.10.1 is the router that advertised this route.
via GigabitEthernet0/0/0/7 Packets destined for the given prefix (10.3.1.0/24) are sent over GigabitEthernet
interface 0/0/0/7.
Backup path Indicates the topology independent loop-free alternate backup path. Here, the
backup path uses the P node 4.4.4.4.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1145
OSPF Commands
show ospf routes
show route, on page 1403 Displays current routes information in the Routing Information Base (RIB).
show rib opaques, on page Displays opaque data installed in the Routing Information Base (RIB).
1386
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1146
OSPF Commands
show ospf sham-links
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospf command. If this argument is included, only information for the
specified routing process is displayed.
vrf (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance.
vrf-name (Optional) Name of the OSPF VRF. The vrf-name argument can be specified as an arbitrary
string. The strings “default” and “all” are reserved VRF names.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospf sham-links command to display OSPF sham-link information.
ospf read
Examples The following is sample output from the show ospf sham-links command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1147
OSPF Commands
show ospf sham-links
Field Description
Sham Link OSPF_SL0 to address Address of the destination endpoint of the sham link.
DoNotAge LSA allowed DoNotAge LSAs are allowed to be flooded over the sham link.
Hello due in Time before the next Hello is sent over the sham link.
Adjacency State State of the adjacency with the neighbor over the sham link.
Number of DBD retrans during last Number of DBD retransmissions during the last exchange over
exchange the sham link.
Last retransmission scan length is Last retransmission scan length on the sham-link interface.
Last retransmission scan time is Last retransmission scan time on the sham-link interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1148
OSPF Commands
show ospf sham-links
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1149
OSPF Commands
show ospf summary-prefix
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved VRF names.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospf summary-prefix command if you configured summarization of external routes with the
summary-prefix command and you want to display configured summary addresses.
ospf read
Examples The following is sample output from the show ospf summary-prefix command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1150
OSPF Commands
show ospf summary-prefix
Field Description
10.1.0.0/255.255.0.0 Summary address designated for a range of addresses. The IP subnet mask used for
the summary route.
Tag Tag value that can be used as a “match” value for controlling redistribution through
route maps.
summary-prefix (OSPF), on page 1165 Creates aggregate addresses for routes being redistributed from another
routing protocol into the OSPF protocol.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1151
OSPF Commands
show ospf virtual-links
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
vrf vrf-name all (Optional) Specifies an OSPF VPN routing and forwarding (VRF) instance. The
vrf-name argument can be specified as an arbitrary string. The strings “default” and
“all” are reserved VRF names.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospf virtual-links command to display useful information for debugging OSPF routing
operations.
ospf read
Examples The following is sample output from the show ospf virtual-links command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1152
OSPF Commands
show ospf virtual-links
Field Description
Virtual Link to router 172.31.101.2 is up OSPF neighbor and whether the link to that neighbor is up or down.
Transit area 0.0.0.1 Transit area through which the virtual link is formed.
via interface GigabitEthernet 0/3/0/0 Interface through which the virtual link is formed.
Cost of usingusing 10 Cost of reaching the OSPF neighbor through the virtual link.
Transmit Delay is 1 sec Transmit delay (in seconds) on the virtual link.
Timer intervals Various timer intervals (in seconds) configured for the link.
Hello due in 0:00:08 When the next hello message is expected from the neighbor (in
hh:mm:ss).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1153
OSPF Commands
show protocols (OSPF)
protocol (Optional) Specifies a routing protocol. For the IPv4 address family, the options are:
• bgp
• eigrp
• isis
• ospf
• rip
For the IPv6 address family, the options are:
• bgp
• eigrp
• isis
• ospfv3
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1154
OSPF Commands
show protocols (OSPF)
Task Operations
ID
rib read
Examples The following is an OSPF configuration and the resulting show protocols ospf display:
router ospf 1
router-id Loopback0
nsf
redistribute connected
redistribute isis 3
area 0
mpls traffic-eng
interface Loopback0
!
interface Loopback1
!
interface Loopback2
!
interface GigabitEthernet 0/3/0/0
!
interface GigabitEthernet 0/3/0/1
!
interface GigabitEthernet 0/3/0/2
!
interface GigabitEthernet 0/3/0/3
!
!
mpls traffic-eng router-id Loopback0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1155
OSPF Commands
show protocols (OSPF)
Field Description
Distance Administrative distance of OSPF routes relative to routes from other protocols.
Area Information about the current area including list of interfaces and the status of
Multiprotocol Label Switching traffic engineering (MPLS TE).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1156
OSPF Commands
snmp context (OSPF)
Syntax Description context_name Specifies name of the SNMP context for OSPF instance.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The snmp-server commands need to be configured to perform SNMP request for the OSPF instance. Refer
SNMP Server Commands module in System Management Command Reference for Cisco ASR 9000 Series
Routers for information on using the snmp-server commands.
Note To map an SNMP context with a protocol instance, topology or VRF entity, use the snmp-server context
mapping command. However, the feature option of this command does not work with OSPF protocol.
This example shows how to configure an SNMP context foo for OSPF instance 100:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#snmp context foo
This example shows how to configure snmp-server commands to be used with the snmp context
command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1157
OSPF Commands
snmp context (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1158
OSPF Commands
snmp trap (OSPF)
snmp trap
no snmp trap
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable SNMP trap for OSPF instance 100 under VRF vrf-1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#vrf vrf-1
RP/0/RSP0/CPU0:router(config-ospf-vrf)#snmp trap
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1159
OSPF Commands
snmp trap rate-limit (OSPF)
Syntax Description window-size Specifies the trap rate limit sliding window size.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples The following example shows how to set the trap rate limit sliding window size to 30 and the maximum
number of traps sent to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1160
OSPF Commands
spf prefix-priority (OSPFv2)
Syntax Description route-policy policy-name Specifies the route policy to apply to OSPFv2 prefix prioritization.
Note If SPF prefix prioritization is configured, /32 prefixes are no longer
preferred by default. To retain the /32 prefixes in higher-priority
queues, define the route-policy accordingly.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
SPF prefix prioritization is disabled, by default. In disabled mode, the /32 prefixes are installed into the global
RIB before other prefixes.
If SPF prefix prioritization is enabled, routes are matched against the route-policy criteria and are assigned
to the appropriate priority queue based on the spf-priority set. Unmatched prefixes, including the /32 prefixes,
are placed in the low-priority queue.
If all /32 prefixes are desired in the high-priority queue or medium-priority queue, configure the following
single route map:
prefix-set ospf-medium-prefixes
0.0.0.0/0 ge 32
end-set
ospf read,
write
Examples The following example shows how to configure OSPFv2 SPF prefix prioritization:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1161
OSPF Commands
spf prefix-priority (OSPFv2)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# prefix-set ospf-critical-prefixes
RP/0/RSP0/CPU0:router(config-pfx)# 66.0.0.0/16
RP/0/RSP0/CPU0:router(config-pfx)# end-set
RP/0/RSP0/CPU0:router(config)# route-policy ospf-spf-priority
RP/0/RSP0/CPU0:router(config-rpl)# if destination in ospf-critical-prefixes then set
spf-priority critical
endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# router-id 66.0.0.1
RP/0/RSP0/CPU0:router(config-ospf)# spf prefix-priority route-policy ospf-spf-priority
prefix-set Enters prefix set configuration mode and defines a prefix set.
route-policy (RPL) Defines a route policy and enters route-policy configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1162
OSPF Commands
stub (OSPF)
stub (OSPF)
To define an area as a stub area, use the stub command in area configuration mode. To disable this function,
use the no form of this command.
stub [no-summary]
no stub
Syntax Description no-summary (Optional) Prevents an Area Border Router (ABR) from sending summary link advertisements
into the stub area.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must configure the stub command on all routers in the stub area.
Use the default-cost command on the ABR of a stub area to specify the cost of the default route advertised
into the stub area by the ABR.
To further reduce the number of link-state advertisements (LSAs) sent into a stub area, you can configure the
no-summary keyword on the ABR to prevent it from sending summary LSAs (LSA Type 3) into the stub
area.
ospf read,
write
Examples The following example shows how to assign a default cost of 20 to stub network 10.0.0.0:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# area 10.0.0.0
RP/0/RSP0/CPU0:router(config-ospf-ar)# stub
RP/0/RSP0/CPU0:router(config-ospf-ar)# default-cost 20
RP/0/RSP0/CPU0:router(config-ospf-ar)# interface GigabitEthernet 0/3/0/3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1163
OSPF Commands
stub (OSPF)
default-cost (OSPF), on page 978 Specifies a cost for the default summary route sent into a stub area.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1164
OSPF Commands
summary-prefix (OSPF)
summary-prefix (OSPF)
To create aggregate addresses for routes being redistributed from another routing protocol into the Open
Shortest Path First (OSPF) protocol, use the summary-prefix command in the appropriate mode. To stop
summarizing redistributed routes, use the no form of the command.
not-advertise (Optional) Suppresses summary routes that match the address and mask pair from being
advertised.
tag tag (Optional) Tag value that can be used as a “match” value for controlling redistribution
through route policies.
Command Default When this command is not used, specific addresses are created for each route from another route source being
distributed into the OSPF protocol.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the summary-prefix command to cause an OSPF Autonomous System Boundary Router (ASBR) to
advertise one external route as an aggregate for all redistributed routes that are covered by the address. This
command summarizes only routes from other routing protocols that are being redistributed into OSPF.
You can use this command multiple times to summarize multiple groups of addresses. The metric used to
advertise the summary is the lowest metric of all the more specific routes. This command helps reduce the
size of the routing table.
If you want to summarize routes between OSPF areas, use the range command.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1165
OSPF Commands
summary-prefix (OSPF)
Examples In the following example, summary address 10.1.0.0 includes address 10.1.1.0, 10.1.2.0, 10.1.3.0,
and so on. Only the address 10.1.0.0 is advertised in an external link-state advertisement.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# summary-prefix 10.1.0.0 255.255.0.0
range (OSPF), on page 1078 Consolidates and summarizes routes at an area boundary.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1166
OSPF Commands
timers lsa group-pacing
Syntax Description seconds Interval (in seconds) at which LSAs are grouped and refreshed, checksummed, or aged. Range is
10 seconds to 1800 seconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPF LSA group pacing is enabled by default. For typical customers, the default group pacing interval for
refreshing, checksumming, and aging is appropriate and you need not configure this feature.
The duration of the LSA group pacing is inversely proportional to the number of LSAs the router is handling.
For example, if you have approximately 10,000 LSAs, decreasing the pacing interval would benefit you. If
you have a very small database (40 to 100 LSAs), increasing the pacing interval to 10 to 20 minutes might
benefit you slightly.
ospf read,
write
Examples The following example shows how to change the OSPF pacing between LSA groups to 60 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# timers lsa group-pacing 60
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1167
OSPF Commands
timers lsa min-arrival
Syntax Description milliseconds Minimum interval (in milliseconds) between accepting same LSA.
Range is 0 to 600000 milliseconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to change the minimum interval between accepting the same
LSA to 2 seconds:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# timers lsa min-arrival 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1168
OSPF Commands
timers throttle lsa all (OSPF)
Syntax Description start-interval Delay to generate first occurance of LSA in milliseconds. Range is 0 to 600000 milliseconds.
hold-interval Minimum delay between originating the same LSA in milliseconds. Range is 1 to 600000
milliseconds.
max-interval Maximum delay between originating the same LSA in milliseconds. Range is 1 to 600000
milliseconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The lsa-start time is the delay before flooding the first instance of an LSA. The lsa-hold interval is the
minimum time to elapse before flooding an updated instance of an LSA. The lsa-max-wait time is the
maximum time that can elapse before flooding an updated instance of an LSA.
For quick convergence, use smaller times for the lsa-start time and lsa-hold interval. However, in relatively
large networks, this may result in a large number of LSAs being flooded in a relatively short time. A balance
with the lsa-start time and lsa-hold interval can be iteratively arrived at for the size of your network. The
lsa-max-wait time can be used to ensure that OSPF reconverges within a reasonable amount of time.
Note LSA throttling is always enabled. You can change the timer values with the timers throttle lsa all command
or specify the no keyword to revert back to the default settings.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1169
OSPF Commands
timers throttle lsa all (OSPF)
ospf read,
write
Examples The following example shows how to change the start, hold, and maximum wait interval values to
500, 1000, and 90,000 milliseconds, respectively:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# timers throttle lsa all 500 1000 90000
The following example is output from the show ospf command that displays the modified LSA
throttle settings:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1170
OSPF Commands
timers throttle lsa all (OSPF)
show ospf, on page 1101 Displays generic information about OSPF routing processes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1171
OSPF Commands
timers throttle spf (OSPF)
Syntax Description spf-start Initial SPF schedule delay (in milliseconds). Range is 1 to 600000 milliseconds.
spf-hold Minimum hold time (in milliseconds) between two consecutive SPF calculations. Range is
1 to 600000 milliseconds.
spf-max-wait Maximum wait time (in milliseconds) between two consecutive SPF calculations. Range is
1 to 600000 milliseconds.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The spf-start time is the delay before running SPF for the first time. The spf-hold interval is the minimum
time to elapse between subsequent SPF runs. The spf-max-wait time is the maximum time that can elapse
before running SPF again.
Tip Setting a low spf-start time and spf-hold time causes routing to switch to the alternate path more quickly
if there is a failure; however, it consumes more CPU processing time.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1172
OSPF Commands
timers throttle spf (OSPF)
Examples The following example shows how to change the start, hold, and maximum wait interval values to
5, 1000, and 90000 milliseconds, respectively:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
RP/0/RSP0/CPU0:router(config-ospf)# timers throttle spf 5 1000 90000
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1173
OSPF Commands
transmit-delay (OSPF)
transmit-delay (OSPF)
To set the estimated time required to send a link-state update packet on the interface, use the transmit-delay
command in the appropriate mode. To return to the default value, use the no form of this command.
transmit-delay seconds
no transmit-delay seconds
Syntax Description seconds Time (in seconds) required to send a link-state update. Range is 1 to 65535 seconds.
Area configuration
Interface configuration
Virtual-link configuration
VRF configuration
Multi-area configuration
Sham-link configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Link-state advertisements (LSAs) in the update packet must have their ages incremented by the amount
specified in the seconds argument before transmission. The value assigned should take into account the
transmission and propagation delays for the interface.
If the delay is not added before transmission over a link,the time in which the LSA propagates over the link
is not considered. This setting has significance only on very low-speed networks not supported in Cisco IOS
XR software or on networks such as satellite circuits that incur a very long (greater than one second) delay
time.
ospf read,
write
Examples The following example shows how to configure a transmit delay for interface GigabitEthernet 0/3/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1174
OSPF Commands
transmit-delay (OSPF)
show ospf, on page 1101 Displays general information about OSPF routing processes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1175
OSPF Commands
virtual-link (OSPF)
virtual-link (OSPF)
To define an Open Shortest Path First (OSPF) virtual link, use the virtual-link command in area configuration
mode. To remove a virtual link, use the no form of this command.
virtual-link router-id
no virtual-link router-id
Syntax Description router-id Router ID associated with the virtual link neighbor. The router ID appears in the show ospf
command display. The router ID can be any 32-bit router ID value specified in four-part,
dotted-decimal notation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
All areas in an OSPF autonomous system must be physically connected to the backbone area (area 0). In some
cases in which this physical connection is not possible, you can use a virtual link to connect to the backbone
through a nonbackbone area. You can also use virtual links to connect two parts of a partitioned backbone
through a nonbackbone area. The area through which you configure the virtual link, known as a transit area,
must have full routing information. The transit area cannot be a stub or not-so-stubby area.
ospf read,
write
Examples The following example shows how to establish a virtual link with default values for all optional
parameters:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# area 10.0.0.0
RP/0/RSP0/CPU0:router(config-ospf-ar)# virtual-link 10.3.4.5
RP/0/RSP0/CPU0:router(config-ospf-ar-vl)#
The following example shows how to establish a virtual link with clear text authentication called
mykey:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1176
OSPF Commands
virtual-link (OSPF)
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 201
RP/0/RSP0/CPU0:router(config-ospf)# area 10.0.0.0
RP/0/RSP0/CPU0:router(config-ospf-ar)# virtual-link 10.3.4.5
RP/0/RSP0/CPU0:router(config-ospf-ar-vl)# authentication-key 0 mykey
show ospf virtual-links, on page 1152 Displays parameters and the current state of OSPF virtual links
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1177
OSPF Commands
vrf (OSPF)
vrf (OSPF)
To configure an Open Shortest Path First (OSPF) VPN routing and forwarding (VRF) instance, use the vrf
command in router configuration mode. To terminate an OSPF VRF, use the no form of this command.
vrf vrf-name
no vrf vrf-name
Syntax Description vrf-name Identifier of an OSPF VRF. The vrf-name argument can be specified as an arbitrary string. The
strings “default” and “all” are reserved VRF names.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vrf command to explicitly configure a VRF. Commands configured under the VRF configuration
mode (such as the interface [OSPF] and authentication commands) are automatically bound to that VRF.
To modify or remove the VRF, the vrf-id argument format must be the same as the format used when creating
the area.
Note To remove the specified VRF from the router configuration, use the no vrf vrf-id command. The no vrf
vrf-id command removes the VRF and all VRF options, such as authentication , default-cost , nssa ,
range , stub , virtual-link , and interface.
To avoid possibly having the router ID change under a VRF, explicitly configure the router ID using the
router-id command.
ospf read,
write
Examples The following example shows how to configure VRF vrf1 and GigabitEthernet interface 0/2/0/0.
GigabitEthernet interface 0/2/0/0 is bound to VRF vrf1 automatically.
RP/0/RSP0/CPU0:router# configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1178
OSPF Commands
vrf (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1179
OSPF Commands
vrf (OSPF)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1180
OSPFv3 Commands
This module describes the commands used to configure and monitor the IP Version 6 (IPv6) Open Shortest
Path First Version 3 (OSPFv3) routing protocol.
For detailed information about OSPFv3 concepts, configuration tasks, and examples, see the Implementing
OSPF on Cisco ASR 9000 Series Router module in the Routing Configuration Guide for Cisco ASR 9000
Series Routers.
• address-family (OSPFv3), on page 1184
• area (OSPFv3), on page 1185
• authentication (OSPFv3) , on page 1187
• auto-cost (OSPFv3), on page 1189
• capability vrf-lite (OSPFv3), on page 1191
• clear ospfv3 process, on page 1193
• clear ospfv3 redistribution, on page 1195
• clear ospfv3 routes, on page 1196
• clear ospfv3 statistics, on page 1197
• cost (OSPFv3), on page 1199
• database-filter all out (OSPFv3), on page 1201
• dead-interval (OSPFv3), on page 1203
• default-cost (OSPFv3), on page 1205
• default-information originate (OSPFv3), on page 1207
• default-metric (OSPFv3), on page 1209
• demand-circuit (OSPFv3), on page 1211
• distance ospfv3, on page 1213
• distribute-list prefix-list in, on page 1215
• distribute-list prefix-list out, on page 1217
• domain-id (OSPFv3), on page 1219
• encryption, on page 1221
• flood-reduction (OSPFv3), on page 1223
• graceful-restart (OSPFv3), on page 1225
• hello-interval (OSPFv3), on page 1227
• instance (OSPFv3), on page 1229
• interface (OSPFv3), on page 1231
• log adjacency changes (OSPFv3), on page 1233
• maximum interfaces (OSPFv3), on page 1235
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1181
OSPFv3 Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1182
OSPFv3 Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1183
OSPFv3 Commands
address-family (OSPFv3)
address-family (OSPFv3)
To enter address family configuration mode for Open Shortest Path First Version 3 (OSPFv3), use the
address-family command in the router ospv3 configuration mode. To disable address family configuration
mode, use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to configure the OSPFv3 router process with IPv6 unicast address
prefixes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1184
OSPFv3 Commands
area (OSPFv3)
area (OSPFv3)
To configure an Open Shortest Path First Version 3 (OSPFv3) area, use the area command in an appropriate
configuration mode. To remove an OSPFv3 area, use the no form of this command.
area area-id
no area area-id
Syntax Description area-id Identifier of an OSPFv3 area. The area-id argument can be specified as either a decimal value or
as an IPv4 address.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
An area must be explicitly configured with the area command.
Use the area command to place the router in area configuration mode (prompt: config-router-ar), from which
you can configure area-specific settings. Commands configured under this mode (such as the interface
command) are automatically bound to that area.
Note To remove the specified OSPFv3 area from the router ospfv3 configuration, use the no area area-id
command. The no area area-id command removes the OSPFv3 area including all OSPFv3 area options,
and all the OSPFv3 interfaces and interface options that are configured under the area.
ospf read,
write
Examples The following example shows how to configure area 0 for OSPFv3 process 1. The GigabitEthernet
0/1/0/1 interface also is configured:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1185
OSPFv3 Commands
area (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1186
OSPFv3 Commands
authentication (OSPFv3)
authentication (OSPFv3)
To enable plain text, Message Digest 5 (MD5) authentication, or null authentication for an Open Shortest
Path First Version 3 (OSPFv3) interface, use the authentication command in an appropriate configuration
mode. To remove such authentication, use the no form of this command.
authentication {ipsec spi spi-value {md5 | sha1} [{clear | password}] password | disable}
no authentication
spi spi-value Specifies a security policy index (SPI) value. Range is 256 to 4294967295.
password (Optional) Specifies that the key be encrypted using a two-way algorithm.
password Any contiguous string that can be entered from the keyboard.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the authentication
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the authentication
parameter specified for the process.
If this command is not specified at any level, then the interface does not use authentication.
Area configuration
Router configuration
Virtual-link configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1187
OSPFv3 Commands
authentication (OSPFv3)
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the authentication command to specify an authentication type for the interface, which overrides the
authentication specified for the area to which this interface belongs. If this command is not included in the
configuration file, the authentication configured in the area to which the interface belongs is assumed (as
specified by the area authentication command).
The authentication type and password must be the same for all OSPFv3 interfaces that are to communicate
with each other through OSPFv3.
Note • IPSec is supported only for Open Shortest Path First version 3 (OSPFv3). IPSec is supported only for
Open Shortest Path First version 3 (OSPFv3).
• If OSPFv3 is configured along with IPsec authentication, then it is likely that adjacencies may flap on a
Route Processor Fail Over (RPFO) even when NSR and/or Graceful Restart is enabled.
ospf read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospfv3 201
RP/0/RSP0/CPU0:router(config-ospfv3)# router-id 10.1.1.1
RP/0/RSP0/CPU0:router(config-ospfv3)# authentication ipsec spi 500 md5
1234567890abcdef1234567890abcdef
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1188
OSPFv3 Commands
auto-cost (OSPFv3)
auto-cost (OSPFv3)
To control how the Open Shortest Path First Version 3 (OSPFv3) protocol calculates default metrics for an
interface, use the auto-cost command in an appropriate configuration mode. To set link cost based only on
the interface type, use the disable form of this command. To re-enable OSPFv3 metric calculation for an
interface according to the bandwidth of the interface, use the no form of this command.
Syntax Description reference-bandwidth mbps (Optional) Sets the rate in Mbps (bandwidth). Range is 1 to 4294967.
disable (Optional) Sets the link cost based only on the interface type.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default OSPFv3 calculates the OSPFv3 metric for an interface according to the bandwidth of the interface.
The no auto-cost disable form of this command reenables OSPFv3 metric calculation for an interface
according to the bandwidth of the interface.
To set link cost based only on the interface type, use the disable keyword.
If you have multiple links with high bandwidth, you might want to use a larger number to differentiate the
cost on those links.
Recommended usage of cost configuration for all OSPFv3 configured interfaces is to be consistent: Either
explicitly configure link costs (by using the cost command) or choose an appropriate default (by using the
auto-cost command).
The value set by the cost command overrides the cost resulting from the auto-cost command.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1189
OSPFv3 Commands
auto-cost (OSPFv3)
Examples The following example shows how to set the reference value for the auto cost to 64:
cost (OSPFv3), on page 1199 Explicitly specifies the cost of the interface (network) for OSPF path calculation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1190
OSPFv3 Commands
capability vrf-lite (OSPFv3)
capability vrf-lite
no capability vrf-lite
This command has no keywords or arguments.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the capability vrf-lite command when routers (sometimes called multi-vrf CE routers) are directly
connected through interfaces associated with a VRF, but without being connected to other PEs through the
MPLS/VPN BGP Backbone.
When OSPFv3 is enabled in a VRF, the router is always an ABR. With the capability vrf-lite command
enabled, the router becomes an ABR only if it is connected to area 0 (backbone area), and there are other
(non-backbone) areas enabled on this router in the given VRF.
Note Routes may be re-introduced to the VPN backbone when this command is used.
This example shows how to enable VRF-lite capability for OSPFv3 instance 1 under VRF vrf1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 1
RP/0/RSP0/CPU0:router(config-ospfv3)#vrf vrf1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1191
OSPFv3 Commands
capability vrf-lite (OSPFv3)
RP/0/RSP0/CPU0:router(config-ospfv3-vrf)#capability vrf-lite
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1192
OSPFv3 Commands
clear ospfv3 process
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only the specified
routing process is affected. Otherwise, all OSPFv3 processes are reset.
Release 4.1.0 The vrf vrf-name keyword and argument were added to support OSPFv3 VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the OSPFv3 router process is reset, OSPFv3 releases all resources allocated, cleans up the internal
database, uninstalls routes, and resets all OSPFv3 adjacencies.
Note The clear ospfv3 process command might clear the router ID configuration if the OSPF router ID is not
explicitly configured through the router-id (OSPFv3), on page 1264 command.
ospf read,
write
Examples The following example shows how to reset all OSPFv3 processes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1193
OSPFv3 Commands
clear ospfv3 process
router-id (OSPFv3), on page 1264 Configures a router ID for the OSPFv3 process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1194
OSPFv3 Commands
clear ospfv3 redistribution
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only the specified
routing process is affected. Otherwise, all OSPFv3 processes are reset.
Release 4.1.0 The vrf vrf-name keyword and argument were added to support OSPFv3 VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear ospfv3 redistribution command to cause the routing table to be read again. OSPFv3 regenerates
and sends Type 5 and Type 7 link-state advertisements (LSAs) to its neighbors. If an unexpected route has
appeared in the OSPFv3 redistribution, using this command corrects the issue.
Note Use of this command can cause a significant number of LSAs to flood the network. We recommend that you
use this command with caution.
ospf read,
write
Examples The following example shows how to clear all OSPFv3 redistributed routes from other protocols:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1195
OSPFv3 Commands
clear ospfv3 routes
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only the specified
routing process is affected. Otherwise, all OSPFv3 processes are reset.
Release 4.1.0 The vrf vrf-name keyword and argument were added to support OSPFv3 VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear ospfv3 routes command to force the internal route table to be repopulated by causing
recalculation of the shortest path first (SPF) routing table. When the OSPFv3 routing table is cleared, OSPFv3
routes in the global routing table are also recalculated.
ospf read,
write
Examples The following example shows how to clear all OSPFv3 routes from the OSPFv3 routing table and
recomputes valid routes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1196
OSPFv3 Commands
clear ospfv3 statistics
clear ospfv3 [process-name] [vrf vrf-name] statistics [neighbor [type interface-path-id] [router-id]]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name
is defined by the router ospfv3 command. If this argument is included, only the specified
routing process is affected.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
router-id (Optional) Specified router ID. This argument must be in 32-bit dotted-decimal notation,
similar to an IPv4 address. This argument clears the counters of the specified neighbor
only.
Release 4.1.0 The vrf vrf-name keyword and argument were added to support OSPFv3 VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear ospfv3 statistics command to reset statistics so that subsequent changes are easily observed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1197
OSPFv3 Commands
clear ospfv3 statistics
ospf read,
write
Examples The following example shows how to clear the OSPFv3 statistical counters of all neighbors on
GigabitEthernet interface 0/2/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1198
OSPFv3 Commands
cost (OSPFv3)
cost (OSPFv3)
To explicitly specify the cost of the interface (network) for OSPF path calculations, use the cost command
in an appropriate configuration mode. To remove the cost, use the no form of this command.
cost cost
no cost
Syntax Description cost Unsigned integer value expressed as the link-state metric. Range is 1 to 65535.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the cost parameter
specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the cost parameter
specified for the process.
If this command is not specified at any level, then the cost is based on the interface bandwidth, as specified
by the auto-cost command.
Area configuration
Release This command was supported under OSPFv3 VRF configuration submode.
4.1.0
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The link-state metric is advertised as the link cost in the router link advertisement.
In general, the path cost is calculated using the following formula:
10^8 / bandwidth
If this value does not suit your network, you can use your own method of calculating path costs.
The value set by the cost command overrides the cost resulting from the auto-cost command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1199
OSPFv3 Commands
cost (OSPFv3)
ospf read,
write
Examples The following example shows how to set the cost value to 65 for GigabitEthernet interface 0/1/0/1:
auto-cost (OSPFv3), on page 1189 Controls how the OSPFv3 protocol calculates default metrics for an
interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1200
OSPFv3 Commands
database-filter all out (OSPFv3)
Command Default If this command is not specified in interface configuration mode, then the interface adopts the database filter
parameter specified for the area.
If this command is not specified in area configuration mode, then the interface adopts the database filter
parameter specified for the process.
If this command is not specified in router ospfv3 configuration mode, then the database filter is disabled and
all outgoing LSAs are flooded to the interface.
Area configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the database-filter all out command to perform the same function that the neighbor command (with
the database-filter keyword) performs on a neighbor basis.
ospf read,
write
Examples The following example shows how to prevent flooding of OSPFv3 LSAs to neighbors reachable
through GigabitEthernet interface 0/2/0/3:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1201
OSPFv3 Commands
database-filter all out (OSPFv3)
neighbor (OSPFv3), on page 1241 Configures OSPFv3 routers interconnecting to nonbroadcast networks.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1202
OSPFv3 Commands
dead-interval (OSPFv3)
dead-interval (OSPFv3)
To set the interval after which a neighbor is declared dead when no hello packets are observed, use the
dead-interval command in an appropriate configuration mode. To return to the default time, use the no
form of this command.
dead-interval seconds
no dead-interval
Syntax Description seconds Unsigned integer that specifies the interval (in seconds). The value must be the same for all nodes
on the same network link. Range is 1 to 65535.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the dead interval
parameter specified for the area.
If this command is not specified in area configuration mode, then the interface adopts the dead interval
parameter specified for the process.
If this command is not specified in router ospfv3 configuration mode, then the dead interval is four times the
interval set by the hello-interval (OSPFv3) command.
Area configuration
Virtual-link configuration
Release This command was supported under OSPFv3 VRF configuration submode.
4.1.0
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Two Open Shortest Path First Version 3 (OSPFv3) routers do not become adjacent if their dead interval values
differ.
If the hello interval is configured, the dead interval value must be larger than the hello interval value. The
dead interval value is usually configured four times larger than the hello interval value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1203
OSPFv3 Commands
dead-interval (OSPFv3)
ospf read,
write
Examples The following example shows how to set the OSPFv3 dead interval on GigabitEthernet interface
0/2/0/3 to 40 seconds:
hello-interval (OSPFv3), on page 1227 Specifies the interval between hello packets that the Cisco IOS XR
software sends on the interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1204
OSPFv3 Commands
default-cost (OSPFv3)
default-cost (OSPFv3)
To specify a cost for the default summary route sent into a stub area or not-so-stubby area (NSSA) for Open
Shortest Path First Version 3 (OSPFv3) packets, use the default-cost command in area configuration mode.
To remove the assigned default route cost, use the no form of this command.
default-cost cost
no default-cost
Syntax Description cost Cost for the default summary route used for a stub or NSSA area. The acceptable value is a 24-bit
number ranging from 1 to 16777214.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-cost command only on an Area Border Router (ABR) attached to a stub or an NSSA area.
In all routers and access servers attached to the stub area, the area should be configured as a stub area using
the stub (OSPFv3) command in the area configuration submode. Use the default-cost command only on
an ABR attached to the stub area. The default-cost command provides the metric for the summary default
route generated by the ABR into the stub area.
ospf read,
write
Examples The following example shows how to assign a cost of 20 to the default route sent into area 10.15.0.0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1205
OSPFv3 Commands
default-cost (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1206
OSPFv3 Commands
default-information originate (OSPFv3)
Syntax Description route-policy policy-name (Optional) Specifies the route policy to apply to default information origination.
always (Optional) Always advertises the default route regardless of whether the
software has a default route.
metric metric-value (Optional) Specifies a metric used for generating the default route. The default
metric value is 1. The value used is specific to the protocol.
metric-type type-value (Optional) Specifies an external link type associated with the default route
advertised into the OSPFv3 routing domain. It can be one of the following
values:
1—Type 1 external route
2—Type 2 external route
tag tag-value (Optional) 32-bit dotted-decimal value attached to each external route. This is
not used by the OSPFv3 protocol itself. It may be used to communicate
information between autonomous system boundary routers (ASBRs). If a tag
is not specified, then zero (0) is used.
Command Default A default external route into an OSPFv3 routing domain is not generated.
metric-value : 1
type-value : Type 2
tag-value: 0
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Whenever you use the redistribute or default-information command to redistribute routes into an OSPFv3
routing domain, the software automatically becomes an ASBR. However, an ASBR does not, by default,
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1207
OSPFv3 Commands
default-information originate (OSPFv3)
generate a default route into the OSPFv3 routing domain. The software still must have a default route for
itself before it generates one, except when you have specified the always keyword.
The default-information originate route-policy attach point conditionally injects the default route 0.0.0.0/0
into the OSPF link-state database, and is done by evaluating the attached policy. If any routes specified in the
policy exist in the global RIB, then the default route is inserted into the link-state database. If there is no match
condition specified in the policy, the policy passes and the default route is generated into the link-state database.
For information about the default-information originate attach point, see the OSPF v3 Policy Attach Points
section in the Implementing Routing Policy chapter in Routing Configuration Guide for Cisco ASR 9000
Series Routers.
When you use the default-information originate command for the OSPFv3 process, the default network
must reside in the routing table.
For information about routing policies, see the Routing Policy Commands chapter in the Routing Command
Reference for Cisco ASR 9000 Series Routers.
ospf read,
write
Examples The following example shows how to specify a metric of 100 for the default route redistributed into
the OSPFv3 routing domain and an external metric type of Type 1:
redistribute (OSPFv3), on page 1258 Redistributes routes from one routing domain into another routing
domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1208
OSPFv3 Commands
default-metric (OSPFv3)
default-metric (OSPFv3)
To set default metric values for routes redistributed from another protocol into Open Shortest Path First
Version 3 (OSPFv3), use the default-metric command in an appropriate configuration mode. To return to
the default state, use the no form of this command.
default-metric value
no default-metric value
Syntax Description value Default metric value appropriate for the specified routing protocol.
Command Default Built-in, automatic metric translations, as appropriate for each routing protocol
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-metric command with the redistribute command to cause the current routing protocol to
use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing
routes with incompatible metrics. Whenever metrics do not convert, use a default metric to provide a reasonable
substitute and enable the redistribution to proceed.
The default-metric value configured in OSPF configuration does not apply to connected routes that are
redistributed to OSPF using the redistribute connected command. To set a non-default metric for connected
routes, configure OSPF with the redistribute connected metric metric-value command.
ospf read,
write
Examples The following example shows how to configure a router with both the Intermediate
System-to-Intermediate System (IS-IS) and the OSPFv3 routing protocols. The OSPFv3 routing
protocol advertises IS-IS derived routes and assigns the routes a metric of 10:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1209
OSPFv3 Commands
default-metric (OSPFv3)
redistribute (OSPFv3), on page 1258 Redistributes routes from one routing domain into another routing
domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1210
OSPFv3 Commands
demand-circuit (OSPFv3)
demand-circuit (OSPFv3)
To configure the Open Shortest Path First Version 3 (OSPFv3) router process to treat the interface as an
OSPFv3 demand circuit, use the demand-circuit command in an appropriate configuration mode. To remove
the demand circuit designation from the interface, use the no form of this command.
demand-circuit [disable]
no demand-circuit
Syntax Description disable (Optional) Disables the demand circuit configuration that may have been specified at a higher
level in the configuration.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the demand circuit
parameter specified for the area.
If this command is not specified in area configuration mode, then the interface adopts the demand circuit
parameter specified for the process.
If this command is not specified at any level, then the interface is not a demand circuit.
Area configuration
Virtual-link configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
On point-to-point interfaces, only one end of the demand circuit must be configured with the demand-circuit
command. Periodic hello messages are suppressed and periodic refreshes of link-state advertisements (LSAs)
do not flood the demand circuit. This command allows the underlying data link layer to be closed when the
topology is stable. In point-to-multipoint topology, only the multipoint end must be configured with this
command.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1211
OSPFv3 Commands
demand-circuit (OSPFv3)
Examples The following example shows how to configure GigabitEthernet interface 0/3/0/1 as an on-demand
circuit:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1212
OSPFv3 Commands
distance ospfv3
distance ospfv3
To define the Open Shortest Path First Version 3 (OSPFv3) route administrative distances based on route
type, use the distance ospfv3 command in router ospfv3 configuration mode. To restore the default value,
use the no form of this command.
Syntax Description intra-area | inter-area | Type of area. It can be one of the following values:
external
intra-area —All routes within an area.
inter-area —All routes from one area to another area.
external —All routes from other routing domains, learned by redistribution.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must specify one of the keywords.
Use the distance ospfv3 command to perform the same function as the distance command used with an
access list. However, the distance ospfv3 command sets a distance for an entire group of routes, rather than
a specific route that passes an access list.
A common reason to use the distance ospfv3 command is when you have multiple OSPFv3 processes with
mutual redistribution, and you want to prefer internal routes from one over external routes from the other.
ospf read,
write
Examples The following example shows how to change the external distance to 200, making it less reliable:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1213
OSPFv3 Commands
distance ospfv3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1214
OSPFv3 Commands
distribute-list prefix-list in
distribute-list prefix-list in
To filter the routes that Open Shortest Path First Version 3 (OSPFv3) installs in the Routing Information Base
(RIB), use the distribute-list prefix-list in command in an appropriate configuration mode. To remove the
filter, use the no form of this command.
Syntax Description prefix-list-name IP Version 6 (IPv6) prefix list name. The list defines which IPv6 prefixes are installed in
the RIB.
Command Default All routes learned by OSPFv3 are installed in the RIB.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the distribute-list prefix-list command to limit the routes that OSPFv3 installs in the RIB of your
router. This command does not affect the information sent to other OSPFv3 routers or the routes that these
routers compute and install.
Note Because the other OSPFv3 routers are not aware of any omissions in the RIB, they may send traffic addressed
to the missing prefixes. If no other provision has been made for these prefixes, the packets are dropped.
When this command is specified in router ospfv3 configuration mode, the filter applies to all routes computed
by OSPFv3.
When this command is specified in interface configuration mode, the filter applies only to routes that forward
outgoing traffic over that interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1215
OSPFv3 Commands
distribute-list prefix-list in
ospf read,
write
Examples The following example shows how to prevent OSPFv3 from installing any routes that have 2001:e624
as the first 32 bits of the address. OSPFv3 is also prevented from installing routes to 2002::/16 that
use GigabitEthernet interface 0/2/0/0 as the next-hop interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1216
OSPFv3 Commands
distribute-list prefix-list out
Syntax Description prefix-list-name IP Version 6 (IPv6) prefix list name. The list defines which IPv6 prefixes are installed in
the RIB.
protocol (Optional) Source protocol from which routes are being redistributed. It can be one of the
following keywords: bgp, eigrp, isis, ospfv3, static, and connected.
The static keyword is used to redistribute IPv6 static routes.
The connected keyword refers to routes that are established automatically because IPv6 is
enabled on an interface. For routing protocols such as OSPFv3 and Intermediate
System-to-Intermediate System (IS-IS), these routes are redistributed as external to the
autonomous system.
process-id (Optional) For the bgp keyword, an autonomous system number has the following ranges:
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
For the eigrp keyword, an autonomous system number.
For the isis keyword, an optional argument that defines a meaningful name for a routing
process. You can specify only one IS-IS process for each router. Creating a name for a
routing process means that you use names when configuring routing.
For the ospfv3 keyword, an appropriate OSPFv3 process name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be entered, but it
is stored internally as a string.
Command Default All routes from protocols specified in the redistribute (OSPFv3), on page 1258 command are redistributed into
OSPFv3.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1217
OSPFv3 Commands
distribute-list prefix-list out
Release Modification
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Routes may be redistributed into OSPFv3 from several other routing protocols or from other OSPFv3 processes.
These routes are then communicated to other OSPFv3 routes through Type 5 (External) or Type 7 not-so-stubby
area (NSSA) link-state advertisements (LSAs). Use the distribute-list prefix-list out command to control
redistribution by matching redistributed routes against an IPv6 prefix list. Only routes permitted by the prefix
list are redistributed into OSPFv3.
Each protocol being redistributed into OSPFv3 can have a separate prefix list. In addition, a prefix list can be
defined that applies to all protocols.
ospf read,
write
Examples The following example shows how to prevent OSPFv3 from redistributing routes that have 2001:e624
as the first 32 bits of the address. In addition, routes with a prefix beginning with 2064 are not
redistributed from Border Gateway Protocol (BGP) autonomous system 1, and only those routes are
redistributed from BGP autonomous system 5.
redistribute (OSPFv3), on page 1258 Redistributes routes from one routing domain into another routing
domain for OSPFv3.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1218
OSPFv3 Commands
domain-id (OSPFv3)
domain-id (OSPFv3)
To specify the Open Shortest Path First Version 3 (OSPFv3) VPN routing and forwarding (VRF) domain ID,
use the domain-id command in VRF configuration mode. To remove the OSPFv3 VRF domain ID, use the
no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If no value is specified for the domain ID, the default is Null (all zeros) primary domain ID. One or more
secondary domain IDs can be specified.
This example shows how to specify a domain ID with type 0105 and value AABBCCDDEEFF:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1219
OSPFv3 Commands
domain-id (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1220
OSPFv3 Commands
encryption
encryption
To encrypt and authenticate Open Shortest Path First Version 3 (OSPFv3) packets, use the encryption
command in an appropriate configuration mode. To remove the encryption, use the no form of this command.
encryption {disable | ipsec spi spi-value esp {3des | aes [{192 | 256}] | des | null [{clear | password}]
encrypt-password} [authentication {md5 | sha1} [{clear | password}] auth-password]}
no encryption
ipsec spi Specifies IPSec ESP encryption and authentication with the Security Parameter Index
(SPI) value.
IPSec supported only for OSPFv3.
encrypt-password Any contiguous string that can be entered from the keyboard as the encryption password.
auth-password Any contiguous string that can be entered from the keyboard as the authentication
password.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1221
OSPFv3 Commands
encryption
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the encryption command to encrypt and authenticate OSPFv3 packets.
Note • IPSec is supported only for Open Shortest Path First version 3 (OSPFv3).
• If OSPFv3 is configured along with IPsec authentication, then it is likely that adjacencies may flap on a
Route Processor Fail Over (RPFO) even when NSR and/or Graceful Restart is enabled.
ospf read,
write
Examples The following example shows how to encrypt and authenticate OSPFv3 packets:
RP/0/RSP0/CPU0:router(config)#router ospfv3 1
RP/0/RSP0/CPU0:router(config-ospfv3)#encryption ipsec spi 256 esp 3des clear
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1222
OSPFv3 Commands
flood-reduction (OSPFv3)
flood-reduction (OSPFv3)
To suppress the unnecessary flooding of link-state advertisements (LSAs) in stable topologies, use the
flood-reduction command in an appropriate configuration mode. To disable this feature, use the no form of
this command.
flood-reduction [disable]
no flood-reduction
Syntax Description disable (Optional) Turns off this functionality at a specific level.
Note The disable keyword is not available in router ospfv3
configuration mode.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the flood reduction
parameter specified by area.
If this command is not specified in area configuration mode, then the interface adopts the flood reduction
parameter specified for the process.
If this command is not specified at any level, then flood reduction is disabled.
Area configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
All routers that support Open Shortest Path First Version 3 (OSPFv3) demand circuits are compatible with
routers supporting flooding reduction.
ospf read,
write
Examples The following example shows how to reduce the flooding of unnecessary LSAs for area 0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1223
OSPFv3 Commands
flood-reduction (OSPFv3)
show ospfv3 neighbor, on page 1296 Displays OSPFv3 neighbor information on an individual interface basis.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1224
OSPFv3 Commands
graceful-restart (OSPFv3)
graceful-restart (OSPFv3)
To enable graceful restart, use the graceful-restart command in an appropriate configuration mode. To
disable this feature, use the no form of this command.
Syntax Description helper disable (Optional) Disables the routers helper support level.
interval interval (Optional) Specifies the minimum interval between graceful restarts. Range is 90 to
3600 seconds.
lifetime lifetime (Optional) Specifies the maximum route lifetime following a restart. Range is 90 to
3600 seconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples The following example shows how to enable the Graceful Restart feature with a minimum interval
between restarts of 300 seconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1225
OSPFv3 Commands
graceful-restart (OSPFv3)
Command Description
show ospfv3 neighbor, on page 1296 Displays OSPFv3 neighbor information on an individual interface basis.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1226
OSPFv3 Commands
hello-interval (OSPFv3)
hello-interval (OSPFv3)
To specify the interval between hello packets that Open Shortest Path First Version 3 (OSPFv3) sends on an
interface, use the hello-interval command in an appropriate configuration mode. To return to the default
time, use the no form of this command.
hello-interval seconds
no hello-interval
Syntax Description seconds Interval (in seconds). The value must be the same for all nodes on a specific network.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the hello interval
parameter specified by area.
If this command is not specified in area configuration mode, then the interface adopts the hello interval
parameter specified for the process.
If this command is not specified at any level, then the hello interval is 10 seconds (broadcast) or 30 seconds
(non-broadcast).
Area configuration
Virtual-link configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The hello interval value is advertised in the hello packets. The shorter the hello interval, the faster topological
changes are detected, but more routing traffic ensues. This value must be the same for all routers and access
servers on a specific network.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1227
OSPFv3 Commands
hello-interval (OSPFv3)
Examples The following example shows how to set the interval between hello packets to 15 seconds on
GigabitEthernet interface 0/3/0/2:
dead-interval (OSPFv3), on page 1203 Sets the interval after which a neighbor is declared dead when no hello
packets are observed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1228
OSPFv3 Commands
instance (OSPFv3)
instance (OSPFv3)
To set the 8-bit instance ID used in Open Shortest Path First Version 3 (OSPFv3) packets sent on an interface,
use the instance command in an appropriate configuration mode. To remove the instance ID, use the no
form of this command.
instance instance-id
no instance instance-id
Syntax Description instance-id Instance identifier sent in OSPFv3 packets. Range is 0 to 255. The same value must be used
by all the communicating OSPFv3 routers on a link.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the instance
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the instance parameter
specified for the process.
If this command is not specified at any level, then the instance is 0.
Area configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The OSPFv3 routing protocol allows multiple unrelated OSPFv3 processes to share a link by using an 8-bit
“instance” value to demultiplex the protocol packets. Each OSPFv3 process sets its configured instance value
in the OSPFv3 packets that it sends, and ignores received packets with instance values from other OSPFv3
processes.
Note The instance-id argument should not be confused with the process-name argument that is specified by the
router ospfv3 command. The former is an 8-bit integer that is sent to other routers as part of the OSPFv3
protocol, and the latter is a 1- to 40-character ASCII string that is significant only within a given router. The
instance ID value is also unrelated to the router ID that is specified by the router-id command, which is a
32-bit integer value that uniquely identifies a router within an OSPFv3 routing domain.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1229
OSPFv3 Commands
instance (OSPFv3)
ospf read,
write
Examples The following example shows how to set the instance value for GigabitEthernet interface 0/3/0/1 to
42:
router-id (OSPFv3), on page 1264 Configures a router ID for the OSPFv3 routing process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1230
OSPFv3 Commands
interface (OSPFv3)
interface (OSPFv3)
To define the interfaces on which Open Shortest Path First Version 3 (OSPFv3) runs, use the interface
command in an appropriate configuration mode. To disable OSPFv3 routing for an interface, use the no form
of this command.
Syntax Description type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the interface command to associate a specific interface with an OSPFv3 area. The interface remains
associated with the area even when the IPv6 address of the interface changes.
Similar to IPv4 address behavior for the interface command, all configured IPv6 addresses are advertised
on an interface after the interface is associated to the OSPF routing process. The only difference is, IPv6
addresses can have multiple primary addresses.
This command places the router in interface configuration mode (prompt: config-router-ar-if), from which
you can configure interface-specific settings. Commands configured under this mode (such as the cost
command) are automatically bound to that interface.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1231
OSPFv3 Commands
interface (OSPFv3)
Examples The following example shows how to define two interfaces that belong to area 1. The cost value for
packets on GigabitEthernet interface 0/3/0/1 is set at 40; the cost value for GigabitEthernet interface
0/3/0/2 is 65:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1232
OSPFv3 Commands
log adjacency changes (OSPFv3)
Syntax Description detail (Optional) Provides all (DOWN, INIT, 2WAY, EXSTART, EXCHANGE, LOADING, FULL)
adjacency state changes.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
By default, you are notified of OSPFv3 neighbor changes without explicitly configuring the log adjacency
changes command. The syslog messages that are sent provide a high-level view of changes to the state of
the OSPFv3 peer relationship.
ospf read,
write
Examples The following example shows how to disable neighbor state change messages:
The following example shows how to re-enable syslog messages for any OSPFv3 neighbor state
changes:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1233
OSPFv3 Commands
log adjacency changes (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1234
OSPFv3 Commands
maximum interfaces (OSPFv3)
Syntax Description number-interfaces Maximum number of interfaces that can be configured for this OSPFv3 process.Range
is 1 to 4294967295.
Release 4.1.1 The range for number of interfaces was changed to 1 to 4294967295 from 1 to 1024. The
default number of interfaces was changed to 1024 from 255.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read,
write
Examples This example shows how to allow a maximum of 1500 interfaces in an OSPFv3 process:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1235
OSPFv3 Commands
maximum paths (OSPFv3)
Syntax Description maximum-routes-number Maximum number of parallel routes that OSPFv3 can install in a routing table.
Range is 1 to 32.
Note The maximum number of paths that can be configured is 32.
VRF configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the maximum number of parallel routes is reduced, all existing paths are pruned and paths reinstalled
at the new maximum number. During this route-reduction period, you may experience some packet loss for
a few seconds. This may impact route traffic.
ospf read,
write
Examples The following example shows how to allow a maximum of two paths to a destination:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1236
OSPFv3 Commands
maximum redistributed-prefixes (OSPFv3)
Syntax Description limit Maximum number of IP Version 6 (IPv6) prefixes that are allowed to be redistributed into
OSPFv3, or, if the warning-only keyword is present, sets the number of prefixes allowed
to be redistributed into OSPFv3 before the system logs a warning message. Range is 1 to
4294967295.
Note If the warning-only keyword is also configured, this value does not limit
redistribution; it is simply the number of redistributed prefixes that, when reached,
causes a warning message to be logged.
threshold (Optional) Percentage of the value set for the maximum number of redistributed prefixes
that, when reached, causes a warning message to be logged.
warning-only (Optional) Causes a warning to be logged when the number of routes defined by the limit
argument have been redistributed. Additional redistribution is not prevented.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If someone mistakenly injects a large number of IPv6 routes into OSPFv3, perhaps by redistributing Border
Gateway Protocol (BGP) into OSPFv3, the network can be severely flooded. Limiting the number of
redistributed routes prevents this potential problem.
When the maximum redistributed-prefixes command is configured, if the number of redistributed routes
reaches the maximum value configured, no more routes are redistributed (unless the warning-only keyword
is configured).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1237
OSPFv3 Commands
maximum redistributed-prefixes (OSPFv3)
The redistribution limit applies only to external IPv6 prefixes. Default routes and summarized routes are not
limited.
The limit is tracked separately for each not-so-stubby-area (NSSA) because redistribution to NSSAs is done
independently for each NSSA and independently of all other regular areas.
Select a maximum value based on your knowledge of how many prefixes are redistributed on the router to
the OSPFv3 process.
ospf read,
write
Examples This example shows how to set a maximum of 2000 prefixes that can be redistributed into OSPFv3
process 1. If the number of prefixes redistributed reaches 75 percent of 2000 (1500 prefixes), a
warning message is logged. Another warning is logged if the limit is reached and no more routes are
redistributed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1238
OSPFv3 Commands
mtu-ignore (OSPFv3)
mtu-ignore (OSPFv3)
To prevent the Open Shortest Path First Version 3 (OSPFv3) router process from checking whether neighbors
are using the same maximum transmission unit (MTU) on a common interface when exchanging database
descriptor (DBD) packets, use the mtu-ignore command in an appropriate configuration mode. To return
to the default state, use the no form of this command.
mtu-ignore [disable]
no mtu-ignore
Syntax Description disable (Optional) Disables the attribute in instances in which it is specified at a higher level in the
configuration.
Note The disable keyword is not available in router ospfv3 configuration mode.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the MTU ignore
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the MTU ignore parameter
specified for the process.
If this command is not specified at any level, then OSPFv3 checks the MTU received from neighbors when
exchanging DBD packets.
Area configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the mtu-ignore command to check whether OSPFv3 neighbors are using the same MTU on a common
interface. This check is performed when neighbors exchange DBD packets. If the receiving MTU in the DBD
packet is higher than the MTU configured on the incoming interface, OSPF adjacency is not established.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1239
OSPFv3 Commands
mtu-ignore (OSPFv3)
Examples The following example shows how to disable MTU mismatch detection on received DBD packets
on GigabitEthernet interface 0/1/0/3:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1240
OSPFv3 Commands
neighbor (OSPFv3)
neighbor (OSPFv3)
To configure Open Shortest Path First Version 3 (OSPFv3) routers interconnecting to nonbroadcast networks,
use the neighbor command in interface configuration mode. To remove a configuration, use the no form
of this command.
neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter all
out]
no neighbor ipv6-address [priority number] [poll-interval seconds] [cost number] [database-filter
all out]
Syntax Description ipv6-address Link- local IP Version 6 (IPv6) address of the neighbor. This argument must be
in the form documented in RFC 2373, in which the address is specified in
hexadecimal using 16-bit values between colons.
priority number (Optional) Specifies an 8-bit number indicating the router priority value of the
nonbroadcast neighbor associated with the IP address specified. The priority
keyword does not apply to point-to-multipoint interfaces.
poll-interval seconds (Optional) Specifies an unsigned integer value (in seconds) reflecting the poll
interval. RFC 1247 recommends that this value be much larger than the hello
interval. The poll-interval keyword does not apply to point-to-multipoint
interfaces.
cost number (Optional) Assigns a cost to the neighbor, in the form of an integer from 1 to 65535.
Neighbors with no specific cost configured assume the cost of the interface, based
on the cost command. On point-to-multipoint interfaces, cost number is the
only keyword and argument combination that works. The cost keyword does not
apply to nonbroadcast multiaccess (NBMA) networks.
database-filter all out (Optional) Filters outgoing link-state advertisements (LSAs) to an OSPFv3
neighbor.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1241
OSPFv3 Commands
neighbor (OSPFv3)
One neighbor entry must be included in the software configuration for each known nonbroadcast network
neighbor. The neighbor address must be the IPv6 link-local address of the interface.
If a neighboring router has become inactive (hello packets have not been seen for the router dead interval
period), it may still be necessary to send hello packets to the dead neighbor. These hello packets are sent at a
reduced rate called the poll interval.
When the router starts up, it sends only hello packets to those routers with nonzero priority; that is, routers
that are eligible to become designated routers (DRs) and backup designated routers (BDRs). After the DR
and BDR are selected, the DR and BDR then start sending hello packets to all neighbors to form adjacencies.
ospf read,
write
Examples The following example shows how to declare a router at address fe80::3203:a0ff:fe9d:f3fe on a
nonbroadcast network:
priority (OSPFv3), on page 1253 Sets the router priority, which helps determine the designated router for this
network.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1242
OSPFv3 Commands
network (OSPFv3)
network (OSPFv3)
To configure the Open Shortest Path First Version 3 (OSPFv3) network type to a type other than the default
for a given medium, use the network command in an appropriate configuration mode. To return to the default
value, use the no form of this command.
[ non-broadcast ] (Optional) Sets the point-to-multipoint network to be nonbroadcast. If you use the
non-broadcast keyword, the neighbor command is required.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the network
parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the network parameter
specified for the process.
If this command is not specified at any level, then the OSPFv3 network type is the default of the given medium.
Area configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the network command to configure broadcast networks as NBMA networks when, for example, routers
in your network do not support multicast addressing.
Most times, it is assumed that when you configure NBMA networks as either broadcast or nonbroadcast, there
are virtual circuits from every router to every router or fully meshed network. However, there are other
configurations where this assumption is not true; for example, a partially meshed network. In these cases, you
can configure the OSPFv3 network type as a point-to-multipoint network. Routing between two routers that
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1243
OSPFv3 Commands
network (OSPFv3)
are not directly connected goes through the router that has virtual circuits to both routers. You need not
configure neighbors when using this command.
If the network command is issued on an interface that does not allow it, this command is ignored.
OSPFv3 has two features related to point-to-multipoint networks. One feature applies to broadcast networks
and the other feature applies to nonbroadcast networks:
• On point-to-multipoint, broadcast networks, you can use the neighbor command, and you must specify
a cost to that neighbor.
• On point-to-multipoint, nonbroadcast networks, you must use the neighbor command to identify
neighbors. Assigning a cost to a neighbor is optional.
ospf read,
write
Examples The following example shows how to configure an Ethernet interface as point-to-point:
neighbor (OSPFv3), on page 1241 Configures OSPFv3 routers interconnecting to nonbroadcast networks.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1244
OSPFv3 Commands
nssa (OSPFv3)
nssa (OSPFv3)
To configure an area as a not-so-stubby area (NSSA), use the nssa command in area configuration mode.
To remove the NSSA distinction from the area, use the no form of this command.
Syntax Description no-redistribution (Optional) Imports routes into the normal areas, but not into the NSSA area,
by the redistribute command when the router is an NSSA area border
router (ABR).
default-information-originate (Optional) Generates a Type 7 default into the NSSA area. This keyword
takes effect only on an NSSA ABR or NSSA autonomous system boundary
router (ASBR).
metric metric-value (Optional) Specifies a metric used for generating the default route. If you do
not specify a default route metric value using the nssa and defaultmetric
commands, the default metric value is 10. The value used is specific to the
protocol.
metric-type type-value (Optional) Specifies an external link type associated with the default route
advertised into the Open Shortest Path First Version 3 (OSPFv3) routing
domain. It can be one of the following values:
1—Type 1 external route
2—Type 2 external route
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
A default route need not be defined in an NSSA ABR when the nssa command is configured. However, if
this command is configured on an NSSA ASBR, then a default route must be defined.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1245
OSPFv3 Commands
nssa (OSPFv3)
ospf read,
write
Examples The following example shows how to configure area 1 as an NSSA area:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1246
OSPFv3 Commands
nsr (OSPFv3)
nsr (OSPFv3)
To configure nonstop routing (NSR) for the Open Shortest Path First Version 3 (OSPFv3) protocol, use the
nsr command in OSPFv3 router configuration mode. To remove this command from the configuration file,
use the no form of this command.
nsr[disable]
no nsr[disable]
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPFv3 NSR will be disabled at process startup, by default. When enabled, this state is remembered in the
active process, and, is regardless of the presence and pairing state of a standby RP, as well as the state of the
standby process.
NSR can be enabled for multiple OSPFv3 processes. The maximum number of processes on which NSR can
be enabled is four.
This example shows how to configure NSR for OSPFv3 process 211:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 211
RP/0/RSP0/CPU0:router(config-ospfv3)#nsr
This example shows how to configure NSR for OSPFv3 process 211:
RP/0/RSP0/CPU0:router#configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1247
OSPFv3 Commands
nsr (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1248
OSPFv3 Commands
ospfv3 name-lookup
ospfv3 name-lookup
To configure Open Shortest Path First Version 3 (OSPFv3) to look up Domain Name System (DNS) names,
use the ospfv3 name-lookup command in global configuration mode. To disable this function, use the no
form of this command.
ospfv3 name-lookup
no ospfv3 name-lookup
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the ospfv3 name-lookup command to simplify the task of searching for a router. Routers are displayed
by name rather than by router ID or neighbor ID.
ospf read,
write
Examples The following example shows how to configure OSPFv3 to look up DNS names for use in all OSPFv3
show command displays:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1249
OSPFv3 Commands
packet-size (OSPFv3)
packet-size (OSPFv3)
To configure the size of Open Shortest Path First Version 3 (OSPFv3) packets up to the size specified by the
maximum transmission unit (MTU), use the packet-size command in an appropriate configuration mode.
To disable this function and reestablish the default packet size, use the no form of this command.
packet-size bytes
no packet-size
Command Default If not specified, the default packet size is 1500 bytes.
Interface configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the packet-size command to customize the size of OSPFv3 packets. The OSPFv3 protocol compares
the packet size and the MTU size and uses the lower packet size value.
ospf read,
write
Examples The following example shows how to configure the packet size:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospf osp3
RP/0/RSP0/CPU0:router(config-ospfv3)# packet-size 3500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1250
OSPFv3 Commands
passive (OSPFv3)
passive (OSPFv3)
To suppress the sending of Open Shortest Path First Version 3 (OSPFv3) packets on an interface, use the
passive command in an appropriate configuration mode. To remove the passive configuration, use the no
form of this command.
passive [disable]
no passive
Command Default If this command is not specified in interface configuration mode, then the interface adopts the passive parameter
specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the passive parameter
specified for the process.
If this command is not specified at any level, then the passive parameter is disabled and OSPFv3 updates are
sent on the interface.
Area configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPF routing information is neither sent nor received through the specified router interface. The specified
interface address appears as a stub network in the OSPF domain.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1251
OSPFv3 Commands
passive (OSPFv3)
Examples The following example shows that OSPFv3 updates run over GigabitEthernet interface 0/3/0/0,
0/2/0/0, and 0/2/0/2. All other interfaces suppress sending OSPFv3 updates because they are in
passive mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1252
OSPFv3 Commands
priority (OSPFv3)
priority (OSPFv3)
To set the router priority for an interface, which helps determine the designated router for an Open Shortest
Path First Version 3 (OSPFv3) link, use the priority command in an appropriate configuration mode. To
return to the default value, use the no form of this command.
priority value
no priority
Syntax Description value 8-bit unsigned integer indicating the router priority value. Range is 0 to 255.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the priority parameter
specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the priority parameter
specified by the process.
If this command is not specified at any level, then the default priority is 1.
Area configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When two routers attached to a network both attempt to become the designated router, the one with the higher
router priority takes precedence. If there is a tie, the router with the higher router ID takes precedence. A
router with a router priority set to zero is ineligible to become the designated router or backup designated
router. Router priority is configured only for interfaces to broadcast and nonbroadcast multiaccess (NBMA)
networks.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1253
OSPFv3 Commands
priority (OSPFv3)
Examples The following example shows how to set the router priority value to 4 on GigabitEthernet interface
0/1/0/1:
neighbor (OSPFv3), on page 1241 Configures OSPFv3 routers interconnecting to nonbroadcast networks.
network (OSPFv3), on page 1243 Configures the OSPFv3 network type to a type other than the default for
a given medium.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1254
OSPFv3 Commands
protocol shutdown (OSPFv3)
protocol shutdown
no protocol shutdown
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the protocol shutdown command to disable the OSPFv3 protocol for a specific routing instance without
removing any existing OSPF configuration parameters.
The OSPFv3 protocol continues to run on the router and you can use the current OSPFv3 configuration, but
OSPFv3 does not form any adjacencies on any interface.
This command is similar to performing the no router ospf command.
ospf read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospfv3 100
RP/0/RSP0/CPU0:router(config-ospfv3)# protocol shutdown
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1255
OSPFv3 Commands
range (OSPFv3)
range (OSPFv3)
To consolidate and summarize routes at an area boundary for Open Shortest Path First Version 3 (OSPFv3),
use the range command in area configuration mode. To restore the default values, use the no form of this
command.
Syntax Description ipv6-prefix Summary prefix designated for a range of IP Version 6 (IPv6) prefixes.
This argument must be in the form documented in RFC 2373, in which the address is
specified in hexadecimal using 16-bit values between colons.
/ prefix-length Length of the IPv6 prefix. A decimal value that indicates how many of the high-order
contiguous bits of the address compose the prefix (the network portion of the address). A
slash must precede the decimal value.
advertise (Optional) Sets the address range status to advertise and generates a Type 3 summary
link-state advertisement (LSA).
not-advertise (Optional) Sets the address range status to DoNotAdvertise. The Type 3 summary LSA is
suppressed and the component networks remain hidden from other networks.
cost number (Optional) Specifies a cost for the range. Range is 1 to 16777214.
Command Default Routes are not consolidated and summarized for an area.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the range command only with Area Border Routers (ABRs). It is used to consolidate or summarize
routes for an area. The result is that a single summary route is advertised to other areas by the ABR. Routing
information is condensed at area boundaries. External to the area, a single route is advertised for each address
range. This process is called route summarization .
You can use the range command to configure multiple ranges. Thus, OSPFv3 can summarize addresses for
many different sets of address ranges.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1256
OSPFv3 Commands
range (OSPFv3)
ospf read,
write
Examples The following example shows how to specify one summary route to be advertised by the ABR to
other areas for all IPv6 prefixes within the range defined by summary prefix 4004:f000::/32:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1257
OSPFv3 Commands
redistribute (OSPFv3)
redistribute (OSPFv3)
To redistribute routes from one routing domain into Open Shortest Path First Version 3 (OSPFv3), use the
redistribute command in an appropriate configuration mode. To remove the redistribute command from
the configuration file and restore the system to its default condition in which the software does not redistribute
routes, use the no form of this command.
Static
redistribute static [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
no redistribute static [metric metric-value] [metric-type {1 | 2}] [policy policy-name] [tag tag-value]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1258
OSPFv3 Commands
redistribute (OSPFv3)
process-id For the bgp keyword, an autonomous system number has the following ranges:
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is
1 to 4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0
to 65535.65535.
For the isis keyword, an IS-IS instance name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be entered,
but it is stored internally as a string.
For the ospf keyword, an OSPF instance name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be entered,
but it is stored internally as a string.
metric metric-value (Optional) Specifies the metric used for the redistributed route. Range is 1 to
16777214. Use a value consistent with the destination protocol.
metric-type { 1 | 2 } (Optional) Specifies the external link type associated with the route advertised into
the OSPF routing domain. It can be one of two values:
• 1—Type 1 external route
• 2—Type 2 external route
If no metric-type is specified, the default is Type 2 external routes.
tag t ag-value (Optional) Specifies the 32-bit dotted-decimal value attached to each external route.
This value is not used by the OSPF protocol itself, but is carried in the External
LSAs. Range is 0 to 4294967295.
policy policy-name (Optional) Specifies the identifier of a configured policy. A policy is used to filter
the importation of routes from this source routing protocol to OSPF.
connected Distributes routes that are established automatically by virtue of having enabled
IP on an interface.
level-1- 2 (Optional) Redistributes both Level 1 and Level 2 routes into other IP routing
protocols.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1259
OSPFv3 Commands
redistribute (OSPFv3)
match { internal | (Optional) Specifies the criteria by which OSPF routes are redistributed into other
external [ 1 | 2 ] | routing domains. It can be one or more of the following:
nssa-external [ 1 | 2
• internal —Routes that are internal to a specific autonomous system (intra-
]}
and inter-area OSPF routes).
• external [ 1 | 2 ]—Routes that are external to the autonomous system, but
are imported into OSPF as Type 1 or Type 2 external routes.
• nssa-external [ 1 | 2 ]—Routes that are external to the autonomous system,
but are imported into OSPF as Type 1 or Type 2 not-so-stubby area (NSSA)
external routes.
For the external and nssa-external options, if a type is not specified, then both
Type 1 and Type 2 are assumed.
If no match is specified, the default is no filtering.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note When redistributing routes (into OSPF) using both command keywords for setting or matching of attributes
and a route policy, the routes are run through the route policy first, followed by the keyword matching and
setting.
Disabling or changing the arguments of any keyword does not affect the state of other keywords.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1260
OSPFv3 Commands
redistribute (OSPFv3)
In general, route redistribution from Level 1 to Level 2 is automatic. You might want to use this command
to better control which Level 1 routes can be redistributed into Level 2.
The redistibution of Level 2 routes into Level 1 is called route leaking. Route leaking is disabled by default.
That is, Level 2 routes are not automatically included in Level 1 link-state protocols. If you want to leak Level
2 routes into Level 1, you must enable that behavior by using this command.
Redistribution from Level 1 into Level 1 and from Level 2 into Level 2 is not allowed.
A router receiving a link-state packet with an internal metric considers the cost of the route from itself to the
redistributing router plus the advertised cost to reach the destination. An external metric considers only the
advertised metric to reach the destination.
Redistributed routing information should always be filtered by the distribute-list prefix-list out command.
Use of this command ensures that only those routes intended by the administrator are passed along to the
receiving routing protocol.
OSPFv3 Considerations
Whenever you use the redistribute or the default-information command to redistribute routes into an
OSPFv3 routing domain, the router automatically becomes an ASBR. However, an ASBR does not, by default,
generate a default route into the OSPFv3 routing domain.
When routes are redistributed between OSPFv3 processes, no OSPFv3 metrics are preserved.
When routes are redistributed into OSPF and no metric is specified with the metric keyword, OSPF uses 20
as the default metric for routes from all protocols except BGP routes, which get a metric of 1. Furthermore,
when the router redistributes from one OSPFv3 process to another OSPFv3 process on the same router, and
if no default metric is specified, the metrics in one process are carried to the redistributing process.
BGP Considerations
The only connected routes affected by this command are the routes not specified by the network (BGP)
command.
ospf read,
write
Examples The following example shows how to cause static routes to be redistributed into an OSPFv3 domain:
distribute-list prefix-list out, on page 1217 Filters the routes redistributed into OSPFv3 from other
routing protocols.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1261
OSPFv3 Commands
retransmit-interval (OSPFv3)
retransmit-interval (OSPFv3)
To specify the time between link-state advertisement (LSA) retransmissions for adjacencies belonging to the
Open Shortest Path First Version 3 (OSPFv3) interface, use the retransmit-interval command in an
appropriate configuration mode. To return to the default value, use the no form of this command.
retransmit-interval seconds
no retransmit-interval
Syntax Description seconds Time (in seconds) between retransmissions. It must be greater than the expected round-trip delay
between any two routers on the attached network. Range is 1 to 65535 seconds.
Command Default If this command is not specified in interface configuration mode, then the interface adopts the retransmit
interval parameter specified by the area.
If this command is not specified in area configuration mode, then the interface adopts the retransmit interval
parameter specified by the process.
If this command is not specified at any level, then the default retransmit interval is 5 seconds.
Area configuration
Virtual-link configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When a router sends an LSA to its neighbor, it keeps the LSA until it receives the acknowledgment message.
If the router receives no acknowledgment, it resends the LSA.
The setting of this parameter should be conservative, or needless retransmission results. The value should be
larger for serial lines and virtual links.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1262
OSPFv3 Commands
retransmit-interval (OSPFv3)
Examples The following example shows how to set the retransmit interval value to 8 seconds while in interface
configuration mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1263
OSPFv3 Commands
router-id (OSPFv3)
router-id (OSPFv3)
To configure a router ID for the Open Shortest Path First Version 3 (OSPFv3) routing process, use the
router-id command in an appropriate configuration mode. To cause the software to use the default method
of determining the router ID, use the no form of this command after clearing or restarting the OSPF process.
router-id router-id
no router-id router-id
Syntax Description router-id 32-bit router ID value specified in four-part, dotted-decimal notation.
Command Default If this command is not configured, the router ID is the highest IP address for an interface on the router, with
any loopback interface taking precedence.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
We recommend that you use the router-id command to explicitly specify a unique 32-bit numeric value for
the router ID. This configuration ensures that OSPFv3 can function regardless of the interface address
configuration. Clear the OSPF process using the clear ospf process command or restart the OSPF process
for the no router-id command to take effect.
In router OSPFv3 configuration mode, OSPF attempts to obtain a router ID in the following ways (in order
of preference):
1. By default, when the OSPF process initializes, it checks if there is a router-id in the checkpointing database.
2. The 32-bit numeric value specified by the OSPF router-id command in router configuration mode. (This
value can be any 32-bit value. It is not restricted to the IPv4 addresses assigned to interfaces on this router,
and need not be a routable IPv4 address.)
3. A global router ID provided by the system (possibly, the first loopback address found at the boot time.
If the OSPFv3 process cannot obtain a router ID from any of these sources, the router issues the following
error message:
%OSPFv3-4-NORTRID : OSPFv3 process 1 cannot run - configure a router ID for this process
At this point, OSPFv3 is effectively passive on all its interfaces. To run OSPFv3, make a router ID available
by one of the methods described.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1264
OSPFv3 Commands
router-id (OSPFv3)
In VRF configuration mode, it is mandatory to configure a router ID manually. Otherwise, the OSPFv3 process
will not become operational in the VRF.
ospf read,
write
Examples The following example shows how to assign the IP address of 10.0.0.10 to the OSPFv3 process 109:
clear ospfv3 process, on page 1193 Resets an OSPFv3 router process without stopping and restarting it.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1265
OSPFv3 Commands
router ospfv3
router ospfv3
To configure an Open Shortest Path First Version 3 (OSPFv3) routing process, use the router ospfv3
command in global configuration mode. To terminate an OSPFv3 routing process, use the no form of this
command.
Syntax Description process-name Name that uniquely identifies an OSPFv3 routing process. The process name is any
alphanumeric string no longer than 40 characters.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You can specify multiple OSPFv3 routing processes in each router. Up to 10 processes can be configured.
The recommendation is not to exceed 4 OSPFv3 processes.
ospf read,
write
Examples The following example shows how to instantiate an OSPFv3 routing process with a process name
of 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1266
OSPFv3 Commands
sham-link (OSPFv3)
sham-link (OSPFv3)
To configure an Open Shortest Path First version 3 (OSPFv3) sham link between two provider edge routers
on a non-default VRF, use the sham-link command in OSPFv3 router area sub-configuration mode. To
terminate an OSPFv3 sham link, use the no form of this command.
Syntax Description source-address IP address of the local (source) sham-link endpoint specified in four-part,
dotted-decimal notation.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the sham-link command to configure a point-to-point connection between two provider edge (PE)
routers creating an interconnect between two VPN sites (VPN backbone). Sham links are configured on PE
provider edge (PE) routers in a Multiprotocol Label Switching (MPLS) VPN backbone.
ospf read,
write
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router ospfv3 ospfv3
RP/0/RSP0/CPU0:router(config_ospfv3)# vrf 1
RP/0/RSP0/CPU0:router(config_ospfv3_vrf)# area 1
RP/0/RSP0/CPU0:router(config_ospfv3_vrf_ar)# sham-link 100::1 200::1
RP/0/RSP0/CPU0:router(config_ospf_vrf_ar_sl)# cost 23
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1267
OSPFv3 Commands
sham-link (OSPFv3)
cost (OSPFv3), on page 1199 Explicitly specifies the cost of the interface (network) for OSPF path calculation.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1268
OSPFv3 Commands
show ospfv3
show ospfv3
To display general information about Open Shortest Path First Version 3 (OSPFv3) routing processes, use
the show ospfv3 command in EXEC mode.
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only information for
the specified routing process is displayed.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Release 4.2.0 Non-stop Routing (NSR) information was added in command output.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Examples The following is a sample output from the show ospfv3 command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1269
OSPFv3 Commands
show ospfv3
The following is a sample output from the show ospfv3 command when OSPFv3 graceful shutdown
has been initiated but not yet completed:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1270
OSPFv3 Commands
show ospfv3
The following is a sample output from the show ospfv3 command when OSPFv3 graceful shutdown
is completed:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1271
OSPFv3 Commands
show ospfv3
Field Description
Minimum hold time between two consecutive SPFs Minimum hold time between consecutive SPFs.
Maximum wait time between two consecutive SPFs Maximum wait time between consecutive SPFs.
Maximum hold time for LSA throttle After initial throttle delay, the LSA generation is backed
off by hold interval.
Maximum wait time for LSA throttle Maximum throttle delay for LSA generation.
LSA group pacing timer Configured LSA group pacing timer (in seconds).
Number of areas in this router is Number of areas configured for the router.
This is sample output from the show ospfv3 vrf command that displays domain -id configuration:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1272
OSPFv3 Commands
show ospfv3
This is sample output from the show ospfv3 vrf command that displays vrf-lite configuration:
This is sample output from the show ospfv3 command to verify that (Non-stop routing (NSR) is
enabled:
RP/0/RSP0/CPU0:router#show ospfv3
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1273
OSPFv3 Commands
show ospfv3
The following is a sample output from the show ospfv3 command with sham-links keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1274
OSPFv3 Commands
show ospfv3 border-routers
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only information for
the specified routing process is displayed.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Examples The following is sample output from the show ospfv3 border-routers command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1275
OSPFv3 Commands
show ospfv3 border-routers
Field Description
GigabitEthernet 0/3/0/0 Packets destined for fe80::3034:30ff:fe33:3742 are sent over GigabitEthernet
interface 3/0/0/0.
ABR/ASBR Router type of the destination; it is either an area border router (ABR) or
autonomous system boundary router (ASBR) or both.
SPF 3 Internal number of the shortest path first (SPF) calculation that installs this route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1276
OSPFv3 Commands
show ospfv3 database
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1277
OSPFv3 Commands
show ospfv3 database
show ospfv3 [process-name [area-id]] [vrf {all vrf-name} ]database [router] [link-state-id]
show ospfv3 [process-name area-id] [vrf {all vrf-name} ]database [router] [adv-router [router-id]]
show ospfv3 [process-name [area-id]] [vrf {all vrf-name} ]database [router] [link-state-id] [internal]
[self-originate]
show ospfv3 [process-name [area-id]][vrf {all vrf-name} ] database [self-originate]
show ospfv3 [process-name [area-id]] [vrf {all vrf-name} ]database [unknown [{area | as | link}]]
[link-state-id] [internal] [adv-router [router-id]] [self-originate]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process
name is defined by the router ospfv3 command. If this argument is included,
only information for the specified routing process is displayed.
adv-router [ router-id ] (Optional) Displays all link-state advertisements (LSAs) of the specified router.
asbr-summary (Optional) Displays information only about the Autonomous System Boundary
Router (ASBR) summary LSAs.
database-summary (Optional) Displays how many of each type of LSA are in the database for each
area and the total.
grace (Optional) Displays information about the state for the graceful restart link.
self-originate (Optional) Displays only self-originated LSAs (from the local router).
link-state-id (Optional) LSA ID that uniquely identifies the LSA. For network LSAs and link
LSAs, this ID is the interface ID of the link of the router originating the LSA.
inter-area prefix (Optional) Displays information only about the interarea prefix LSAs.
inter-area router (Optional) Displays information only about the interarea router LSAs.
nssa-external (Optional) Displays information only about the not-so-stubby area (NSSA) external
LSAs.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1278
OSPFv3 Commands
show ospfv3 database
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The various forms of this command deliver information about different OSPFv3 link-state advertisements.
ospf read
Examples The following is sample output from the show ospfv3 database command with no arguments or
keywords:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1279
OSPFv3 Commands
show ospfv3 database
Field Description
Bits B indicates that the router is an area border router. E indicates that the router is an autonomous
system boundary router. V indicates that the router is a virtual link endpoint. W indicates that
the router is a wildcard multicast receiver.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1280
OSPFv3 Commands
show ospfv3 database
The following is sample output from the show ospfv3 database command with the external
keyword:
LS age: 189
LS Type: AS External Link
Link State ID: 0
Advertising Router: 10.0.0.206
LS Seq Number: 80000002
Checksum: 0xa303
Length: 36
Prefix Address: 2222::
Prefix Length: 56, Options: None
Metric Type: 2 (Larger than any link state path)
Metric: 20
External Route Tag: 0
Field Description
External Route Tag External route tag, a 32-bit field attached to each external route. This tag is not used
by the OSPFv3 protocol itself.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1281
OSPFv3 Commands
show ospfv3 database
The following is sample output from the show ospfv3 database command with the inter-area
prefix keyword:
LS age: 715
LS Type: Inter Area Prefix Links
Link State ID: 0
Advertising Router: 10.0.0.206
LS Seq Number: 80000002
Checksum: 0x3cb5
Length: 36
Metric: 1
Prefix Address: 3002::
Prefix Length: 56, Options: None
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Options LA indicates that the prefix is a local address. MC indicates the prefix is multicast
capable. NU indicates that the prefix is not unicast capable. P indicates that the
prefix should be propagated at a not-so-stubby area (NSSA) area border.
The following is sample output from the show ospfv3 database command with the inter-area
router keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1282
OSPFv3 Commands
show ospfv3 database
LS age: 1522
Options: (V6-Bit E-Bit R-bit DC-Bit)
LS Type: Inter Area Router Links
Link State ID: 167772366
Advertising Router: 10.0.0.207
LS Seq Number: 80000002
Checksum: 0xcaae
Length: 32
Metric: 1
Destination Router ID: 10.0.0.206
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA.)
The following is sample output from the show ospfv3 database command with the link keyword:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1283
OSPFv3 Commands
show ospfv3 database
LS age: 620
Options: (V6-Bit E-Bit R-bit DC-Bit)
LS Type: Link-LSA (Interface: Ethernet0/0/0/0)
Link State ID: 1 (Interface ID)
Advertising Router: 10.0.0.207
LS Seq Number: 80000003
Checksum: 0x7235
Length: 56
Router Priority: 1
Link Local Address: fe80::204:c0ff:fe22:73fe
Number of Prefixes: 1
Prefix Address: 7002::
Prefix Length: 56, Options: None
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Prefix Address and Length List of prefixes associated with the link.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1284
OSPFv3 Commands
show ospfv3 database
Field Description
Options LA indicates that the prefix is a local address. MC indicates that the prefix is
multicast capable. NU indicates that the prefix is not unicast capable. P indicates
that the prefix should be propagated at an NSSA area border.
The following is sample output from the show ospfv3 database command with the network
keyword:
LS age: 1915
Options: (V6-Bit E-Bit R-bit DC-Bit)
LS Type: Network Links
Link State ID: 1 (Interface ID of Designated Router)
Advertising Router: 10.0.0.207
LS Seq Number: 80000004
Checksum: 0x4330
Length: 36
Attached Router: 10.0.0.207
Attached Router: 0.0.0.1
Attached Router: 10.0.0.206
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1285
OSPFv3 Commands
show ospfv3 database
Field Description
The following is sample output from the show ospfv3 database command with the prefix keyword:
Field Description
Referenced LSA Type Router LSA or network LSA of the prefixes referenced.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1286
OSPFv3 Commands
show ospfv3 database
Field Description
Options LA indicates that the prefix is a local address. MC indicates that the prefix
is multicast capable. NU indicates that the prefix is not unicast capable. P
indicates the prefix should be propagated at an NSSA area border.
The following is sample output from the show ospfv3 database command with the router keyword:
LS age: 814
Options: (V6-Bit E-Bit R-bit)
LS Type: Router Links
Link State ID: 0
Advertising Router: 0.0.0.1
LS Seq Number: 8000003c
Checksum: 0x51ca
Length: 56
Number of Links: 2
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1287
OSPFv3 Commands
show ospfv3 database
Field Description
Checksum Link-state checksum (Fletcher checksum of the complete contents of the LSA).
Link connected to The type of network to which this interface is connected. Values are:
• Another Router (point-to-point).
• A Transit Network.
• A Virtual Link.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1288
OSPFv3 Commands
show ospfv3 flood-list
show ospfv3 [process-name] [area-id] [vrf {all vrf-name} ]flood-list [type interface-path-id]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name
is defined by the router ospfv3 command. If this argument is included, only information
for the specified routing process is displayed.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospfv3 flood-list command to display OSPFv3 packet pacing.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1289
OSPFv3 Commands
show ospfv3 flood-list
Examples The following sample output from the show ospfv3 flood-list command shows three entries for the
OSPFv3 1 process running over GigabitEthernet interface 0/3/0/0:
Field Description
Link state retransmission due in Length of time before next link-state transmission.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1290
OSPFv3 Commands
show ospfv3 interface
show ospfv3 [process-name] [area-id] interface [vrf {all vrf-name} ][type interface-path-id]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name
is defined by the router ospfv3 command. If this argument is included, only information
for the specified routing process is displayed.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospfv3 interface command when the adjacency between two neighboring routers is not forming.
Adjacency means that the routers synchronize their databases when they discover each other.
You can look at the output to check the physical link and line protocol status and to confirm that the network
type and timer intervals match those of the neighboring routers.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1291
OSPFv3 Commands
show ospfv3 interface
ospf read
Examples The following is sample output from the show ospfv3 interface command when GigabitEthernet
interface 0/2 /0/0 is specified:
Field Description
GigabitEthernet Status of the physical link and operational status of the protocol.
Link Local Address Interface link local address and interface ID.
Area OSPFv3 area ID, process ID, instance ID, and router ID.
Backup Designated router Backup designated router ID and respective interface IPv6 address.
Hello Number of seconds until next hello packet is sent over this interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1292
OSPFv3 Commands
show ospfv3 interface
Field Description
Index 0/2/1 Link, area and autonomous system flood indexes, and number of flood queue
entries.
Next 0(0)/0(0)/0(0) Next link, area and autonomous system flood information, data pointer, and
index.
Last flood scan time Time of last flood scan (in milliseconds).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1293
OSPFv3 Commands
show ospfv3 message-queue
Syntax Description vrf Specifies an OSPF VPN routing and forwarding (VRF) instance.
Release The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
4.1.0 information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
OSPFv3 Process 0
Hello Thread Packet Input Queue:
Current queue length: 0
Peak queue length: 2
Queue limit: 5000
Packets received: 104091
Packets processed: 104091
Packets dropped: 0
Processing quantum: 10
Full quantum used: 0
Pulses sent: 104089
Pulses received: 104089
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1294
OSPFv3 Commands
show ospfv3 message-queue
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1295
OSPFv3 Commands
show ospfv3 neighbor
show ospfv3 [process-name] [area-id] [vrf {all vrf-name} ]neighbor [type interface-path-id]
[neighbor-id] [detail]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name
is defined by the router ospfv3 command. If this argument is included, only information
for the specified routing process is displayed.
area-id (Optional) Area ID. If you do not specify an area, all areas are displayed.
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
detail (Optional) Displays all neighbors given in detail (lists all neighbors).
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospfv3 neighbor command when the adjacency between two neighboring routers is not
forming. Adjacency means that the routers synchronize their databases when they discover each other.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1296
OSPFv3 Commands
show ospfv3 neighbor
ospf read
Examples The following is sample output from the show ospfv3 neighbor command showing two lines of
summary information for each neighbor:
Field Description
Pri Router priority for designated router election. A router with a priority of 0 is never elected
as the designated router or backup designated router.
Dead Time Time (in hh:mm:ss) to elapse before OSPFv3 declares the neighbor dead.
Neighbor is Time (in hh:mm:ss) that the OSPFv3 neighbor has been up.
up
The following is sample output showing summary information about the neighbor that matches the
neighbor ID:
Neighbor 10.0.0.207
In the area 0 via interface Ethernet0/0/0/0
Neighbor: interface-id 2, link-local address fe80::204:c0ff:fe22:73fe
Neighbor priority is 1, State is FULL, 6 state changes
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1297
OSPFv3 Commands
show ospfv3 neighbor
Neighbor 10.0.0.207
In the area 1 via interface GigabitEthernet 0/3/0/0
Neighbor: interface-id 3, link-local address fe80::3034:30ff:fe33:3742
Neighbor priority is 1, State is FULL, 6 state changes
Options is 0x13
Dead timer due in 00:00:38
Neighbor is up for 01:09:21
Index 0/1/1, retransmission queue length 0, number of retransmission 1
First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Field Description
In the area Area and interface through which the OSPFv3 neighbor is known.
Options Hello packet options field contents (E-bit only; possible values are 0 and 2; 2 indicates
that area is not a stub; 0 indicates that area is a stub).
Dead timer Time (in hh:mm:ss) to elapse before OSPFv3 declares the neighbor dead.
Neighbor is up Time (in hh:mm:ss) that OSPFv3 neighbor has been up.
Index Index and the remaining lines of this command give detailed information about flooding
information received from the neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1298
OSPFv3 Commands
show ospfv3 neighbor
The following sample output shows the neighbors that match the neighbor ID on the interface when
the interface along with the neighbor ID is specified:
Neighbor 10.0.0.207
In the area 0 via interface GigabitEthernet 0/3/0/1
Neighbor: interface-id 2, link-local address fe80::204:c0ff:fe22:73fe
Neighbor priority is 1, State is FULL, 6 state changes
DR is 10.0.0.207 BDR is 10.0.0.206
Options is 0x13
Dead timer due in 00:00:39
Neighbor is up for 01:11:21
Index 0/1/2, retransmission queue length 0, number of retransmission 1
First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Table 132: show ospfv3 neighbor GigabitEthernet 0/3/0/1 10.0.0.207 Field Descriptions
Field Description
In the area Area and interface through which the OSPFv3 neighbor is known.
Options Hello packet options field contents (E-bit only; possible values are 0 and 2; 2 indicates
that area is not a stub; 0 indicates that area is a stub).
Dead timer Time (in hh:mm:ss) to elapse before OSPFv3 declares the neighbor dead.
Neighbor is up Time (in hh:mm:ss) that OSPFv3 neighbor has been up.
Index Index and the remaining lines of this command give detailed information about flooding
information received from the neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1299
OSPFv3 Commands
show ospfv3 neighbor
The following sample output shows all neighbors on the interface when the interface is specified:
Field Description
Pri Router priority for designated router election. A router with a priority of 0 is never elected
as the designated router or backup designated router.
Dead Time Time (in hh:mm:ss) to elapse before OSPF declares the neighbor dead.
Neighbor is Amount of time (in hh:mm:ss) that the OSPF neighbor has been up.
up
The following is sample output showing detailed neighbor information for GigabitEthernet interface
0/3/0/1:
Neighbor 10.0.0.207
In the area 0 via interface GigabitEthernet 0/3/0/1
Neighbor: interface-id 2, link-local address fe80::204:c0ff:fe22:73fe
Neighbor priority is 1, State is FULL, 6 state changes
DR is 10.0.0.207 BDR is 10.0.0.206
Options is 0x13
Dead timer due in 00:00:39
Neighbor is up for 01:13:40
Index 0/1/2, retransmission queue length 0, number of retransmission 1
First 0(0)/0(0)/0(0) Next 0(0)/0(0)/0(0)
Last retransmission scan length is 1, maximum is 1
Last retransmission scan time is 0 msec, maximum is 0 msec
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1300
OSPFv3 Commands
show ospfv3 neighbor
Table 134: show ospfv3 neighbor GigabitEthernet 0/3/0/1 detail Field Descriptions
Field Description
In the area Area and interface through which the OSPFv3 neighbor is known.
Options Hello packet options field contents (E-bit only; possible values are 0 and 2; 2 indicates
that area is not a stub; 0 indicates that area is a stub).
Dead timer Time (in hh:mm:ss) to elapse before OSPFv3 declares the neighbor dead.
Neighbor is up Time (in hh:mm:ss) that the OSPFv3 neighbor has been up.
Index Index and the remaining lines of this command give detailed information about flooding
information received from the neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1301
OSPFv3 Commands
show ospfv3 request-list
show ospfv3 [process-name] [area-id] [vrf {all vrf-name} ]request-list [type interface-path-id]
[neighbor-id]
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name
is defined by the router ospfv3 command. If this argument is included, only information
for the specified routing process is displayed.
area-id (Optional) Area ID. If you do not specify an area, all areas are displayed.
type (Optional) Interface type. For more information, use the question mark (?) online help
function.
For more information about the syntax for the router, use the question mark (?) online
help function.
neighbor-id (Optional) Router ID of the OSPFv3 neighbor. This argument must be in 32-bit
dotted-decimal notation, similar to an IPv4 address.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1302
OSPFv3 Commands
show ospfv3 request-list
You might use this command when the databases of two neighboring routers are out of synchronization or if
the adjacency is not forming between them. Adjacency means that the routers synchronize their databases
when they discover each other.
You can look at the list to determine if one router is trying to request a particular database update. Entries that
appear to be suspended in the list usually indicate that updates are not being delivered. One possible reason
for this behavior is a maximum transmission unit (MTU) mismatch between the routers.
You might also look at this list to make sure it is not corrupted. The list should refer to database entries that
actually exist.
ospf read
Examples The following sample output shows request lists for neighbor 10.0.0.207 on the OSPFv3 1 process:
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1303
OSPFv3 Commands
show ospfv3 request-list
show ospfv3 retransmission-list, on page Displays the first ten link-state entries in the retransmission list
1305 that the local router sends to the specified neighbor over the
specified interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1304
OSPFv3 Commands
show ospfv3 retransmission-list
Syntax Description process-name (Optional) Name that uniquely identifies an Open Shortest Path First Version 3 (OSPFv3)
routing process. The process name is defined by the router ospfv3 command. If this
argument is included, only information for the specified routing process is displayed.
area-id (Optional) Area ID. If you do not specify an area, all areas are displayed.
type (Optional) Interface type. For more information, use the question mark (?) online help
function.
For more information about the syntax for the router, use the question mark (?) online
help function.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You might use this command when the databases of two neighboring routers are out of synchronization or if
the adjacency is not forming between them. Adjacency means that the routers synchronize their databases
when they discover each other.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1305
OSPFv3 Commands
show ospfv3 retransmission-list
You can look at the list to determine if one router is trying to request a particular database update. Entries that
appear to be suspended in the list usually indicate that updates are not being delivered. One possible reason
for this behavior is a maximum transmission unit (MTU) mismatch between the routers.
You might also look at this list to make sure it is not corrupted. The list should refer to database entries that
actually exist.
ospf read
Examples The following sample output shows the retransmission list for neighbor 10.0.124.4 on GigabitEthernet
interface 0/3/0/0:
Table 136: show ospfv3 retransmission-list 10.0.124.4 GigabitEthernet 0/3/0/0 Field Descriptions
Field Description
show ospfv3 request-list, on page 1302 Displays the first ten link-state requests pending that the local router
is making to the specified neighbor and interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1306
OSPFv3 Commands
show ospfv3 routes
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name
is defined by the router ospf command. If this argument is included, only information
for the specified routing process is displayed.
ipv6-prefix (Optional) IP Version 6 (IPv6) prefix, which limits output to a specific route.
This argument must be in the form documented in RFC 2373, in which the address is
specified in hexadecimal using 16-bit values between colons.
/ prefix-length (Optional) Length of the IPv6 prefix. A decimal value that indicates how many of the
high-order contiguous bits of the address compose the prefix (the network portion of the
address). A slash must precede the decimal value.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 4.1.0 The vrf vrf_name keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1307
OSPFv3 Commands
show ospfv3 routes
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospfv3 routes command to display the OSPFv3 private routing table (which contains only
routes calculated by OSPFv3). If there is something wrong with a route in the Routing Information Base
(RIB), check the OSPFv3 copy of the route to determine if it matches the RIB contents. If it does not match,
there is a synchronization problem between OSPFv3 and the RIB. If the routes match and the route is incorrect,
OSPFv3 has made an error in its routing calculation.
ospf read
Examples The following sample output shows the route table for OSPFv3 process 1:
Field Description
cost 21/0 Sum of the link costs required to reach prefix 3000:11:22::/64. 0. In this example,
20 is the external cost.
GigabitEthernet 0/3/0/0 Packets destined for prefix 3000:11:22::/64 are sent over the GigabitEthernet
0/3/0/0 interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1308
OSPFv3 Commands
show ospfv3 routes
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1309
OSPFv3 Commands
show ospfv3 statistics rib-thread
Syntax Description process-name (Optional) Name that uniquely identifies an OSPF routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only information for
the specified routing process is displayed.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1310
OSPFv3 Commands
show ospfv3 statistics rib-thread
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1311
OSPFv3 Commands
show ospfv3 summary-prefix
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only information for
the specified routing process is displayed.
Release 4.1.0 The vrf { vrf_name} keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show ospfv3 summary-prefix command if you configured summarization of external routes with
the summary-prefix command and you want to display configured summary addresses.
ospf read
Examples The following sample output shows the summary prefix address for the OSPFv3 1 process:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1312
OSPFv3 Commands
show ospfv3 summary-prefix
Field Description
4004:f000::/32 Summary prefix designated for a range of IPv6 prefixes. The length of the IPv6 prefix.
Tag Tag value that can be used as a “match” value for controlling redistribution through route
maps.
summary-prefix (OSPFv3), on page 1328 Creates aggregate addresses for routes being redistributed from
another routing protocol into OSPFv3.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1313
OSPFv3 Commands
show ospfv3 virtual-links
Syntax Description process-name (Optional) Name that uniquely identifies an OSPFv3 routing process. The process name is
defined by the router ospfv3 command. If this argument is included, only information for
the specified routing process is displayed.
Release 4.1.0 The vrf { vrf_name} keyword and argument were added to show OSPFv3 VRF configuration
information. The output of the command was enhanced to include the name of the VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The information displayed in the show ospfv3 virtual-links command is useful in debugging OSPFv3 routing
operations.
ospf read
Examples The following sample output shows the virtual links for the OSPFv3 1 process:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1314
OSPFv3 Commands
show ospfv3 virtual-links
Field Description
Virtual Link to router is up Specifies the OSPFv3 neighbor, and if the link to that neighbor is up or down.
Transit area Transit area through which the virtual link is formed.
Cost Cost of reaching the OSPF neighbor through the virtual link.
Hello due in When the next hello message is expected from the neighbor (in hh:mm:ss).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1315
OSPFv3 Commands
show protocols (OSPFv3)
protocol (Optional) Specifies a routing protocol. For the IPv4 address family, the options are:
• bgp
• eigrp
• isis
• ospf
• rip
For the IPv6 address family, the options are:
• bgp
• eigrp
• isis
• ospfv3
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ospf read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1316
OSPFv3 Commands
show protocols (OSPFv3)
Examples The following example is sample output from the show protocols command:
Field Description
Distance Administrative distance for the protocol. This distance determines the priority the Routing
Information Base (RIB) gives to the routes, as opposed to other protocols, for example, IS-IS.
Area OSPFv3 areas defined in this process, followed by their associated interfaces.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1317
OSPFv3 Commands
snmp context (OSPFv3)
Syntax Description context_name Specifies name of the SNMP context for OSPFv3 instance.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes the proper task
IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA
administrator for assistance.
The snmp-server commands need to be configured to perform SNMP request for the OSPF instance. Refer
SNMP Server Commands module in System Management Command Reference for Cisco ASR 9000 Series
Routers for information on using the snmp-server commands.
Note To map an SNMP context with a protocol instance, topology or VRF entity, use the snmp-server context
mapping command. However, the feature option of this command does not work with OSPFv3 protocol.
This example shows how to configure an SNMP context foo for OSPFv3 instance 100:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 100
RP/0/RSP0/CPU0:router(config-ospf)#snmp context foo
This example shows how to configure snmp-server commands to be used with the snmp context
command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1318
OSPFv3 Commands
snmp context (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1319
OSPFv3 Commands
snmp trap (OSPFv3)
snmp trap
no snmp trap
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable SNMP trap for OSPFv3 instance 100 under VRF vrf-1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 100
RP/0/RSP0/CPU0:router(config-ospf)#vrf vrf-1
RP/0/RSP0/CPU0:router(config-ospf-vrf)#snmp trap
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1320
OSPFv3 Commands
snmp trap rate-limit (OSPFv3)
Syntax Description window-size Specifies the trap rate limit sliding window size. The range is 2 to 60 windows.
max-num-traps Specifies the maximum number of traps sent in window time. The range is 0 to 300 traps.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to set the trap rate limit sliding window size to 50 and the maximum number
of traps sent to 250 for OSPFv3 instance 100 under vrf vrf1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 100
RP/0/RSP0/CPU0:router(config-ospfv3)#vrf vrf1
RP/0/RSP0/CPU0:router(config-ospfv3-vrf)#snmp trap rate-limit 50 250
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1321
OSPFv3 Commands
spf prefix-priority (OSPFv3)
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# prefix-set ospf3-critical-prefixes
RP/0/RP0/CPU0:router(config-pfx)# 66.0.0.0/16
RP/0/RP0/CPU0:router(config-pfx)# end-set
RP/0/RP0/CPU0:router(config)# route-policy ospf3-spf-priority
RP/0/RP0/CPU0:router(config-rpl)# if destination in ospf-critical-prefixes then set
spf-priority critical
endif
RP/0/RP0/CPU0:router(config-rpl)# end-policy
RP/0/RP0/CPU0:router(config-rpl)# commit
RP/0/RP0/CPU0:router(config-rpl)# exit
RP/0/RP0/CPU0:router(config)# router ospfv3 1
RP/0/RP0/CPU0:router(config-ospf)# router-id 66.0.0.1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1322
OSPFv3 Commands
spf prefix-priority (OSPFv3)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1323
OSPFv3 Commands
stub (OSPFv3)
stub (OSPFv3)
To define an area as a stub area for Open Shortest Path First Version 3 (OSPFv3), use the stub command
in area configuration mode. To disable this function, use the no form of this command.
stub [no-summary]
no stub
Syntax Description no-summary (Optional) Prevents an area border router (ABR) from sending summary link advertisements
into the stub area. Areas with this option are known as totally stubby areas.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You must configure the stub command on all routers in the stub area. Use the default-cost area command
on the ABR of a stub area to specify the cost of the default route advertised into the stub area by the ABR.
Two stub area router configuration commands exist: the stub and default-cost commands. In all routers
attached to the stub area, the area should be configured as a stub area using the stub command. Use the
default-cost command only on an ABR attached to the stub area. The default-cost command provides
the metric for the summary default route generated by the ABR into the stub area.
To further reduce the number of link-state advertisements (LSAs) sent into a stub area, you can configure the
no-summary keyword on the ABR to prevent it from sending summary LSAs (LSA Type 3) into the stub
area.
A stub area does not accept information about routes external to the autonomous system.
ospf read,
write
Examples The following example shows how to create stub area 5 and specifies a cost of 20 for the default
summary route sent into this stub area:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1324
OSPFv3 Commands
stub (OSPFv3)
RP/0/RSP0/CPU0:router(config-ospfv3-ar)# default-cost 20
default-cost (OSPFv3), on page 1205 Specifies a cost for the default summary route sent into a stub area.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1325
OSPFv3 Commands
stub-router
stub-router
To modify self originated router LSAs when stub router is active, use the stub-router command in an
appropriate configuration mode. To disable this function, use the no form of this command.
Syntax Description router-lsa Specifies that always originate router link-state advertisements (LSAs) with the
stub-router.
r-bit Router-LSAs are originated with R-bit clear (v6 bit set), which means the node does
not act as a transit router. Directly connected networks (native to OSPF) are still
reachable within the OSPF area.
v6-bit Router-LSAs are originated with V6 bit clear (and also r-bit clear). That means the
node is not willing to receive any ipv6 traffic. Other ospfv3 routers won't install any
route to a node with v6-bit clear.
max-metric Router-LSAs are originated with maximum metric. Unlike the r-bit and v6-bit mode,
the router may still act as a transit node, if there is no alternate path.
on-proc-migration Stub-router mode is activated for the desired period of time, upon ospfv3 process
migration.
on-proc-restart Stub-router mode is activated for the desired period of time, upon ospfv3 process restart.
on-switchover Stub-router mode is activated for the desired period of time, upon RP failover.
on-startup Stub-router mode is activated (for configured time, or until BGP converges) upon router
startup (boot).
wait-for-bgp Stub-router mode is terminated upon BGP convergence in ipv6 unicast address family.
This option could only be used in the global routing table, not in a non-default VRF.
This option is only supported with the on-startup trigger when the router boots.
summary-lsa If enabled, summary LSAs are advertised with modified metric when stub-router is
active. This configuration is applicable to max-metric mode.
In r-bit mode, ABR/ASBR functionality is implicitly disabled and routers will not use
this node as an ABR/ASBR, since it declares no transit capability (r-bit clear).
If enabled and metric is not explicitly configured, the default metric for summary LSAs
when stub-router active is 16711680 (0xFF0000).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1326
OSPFv3 Commands
stub-router
external-lsa If enabled, external LSAs are advertised with modified metric when stub-router is
active. This configuration is applicable to max-metric mode.
In r-bit mode, ABR/ASBR functionality is implicitly disabled and routers will not use
this node as an ABR/ASBR, since it declares no transit capability (r-bit clear).
If enabled and metric is not explicitly configured, the default metric for external LSAs
when stub-router active is 16711680 (0xFF0000).
include-stub If enabled, intra-area-prefix LSAs that are referencing router LSA are advertised with
maximum metric (0xffff) when stub-router is active.
Intra-area-prefix LSAs that are referencing network LSA do not change metric
Can be used in r-bit and max-metric modes.
/128 prefixes that are normally advertised with LA-bit set and 0 metric are also
advertised with maximum metric and LA-bit clear when stub-router is active.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Only one method (r-bit, v6-bit, max-metric) could be activated at a time. Configuring the methods
simultaneously, or different method per trigger, is not supported.
This example shows how to configure router LSAs are originated with R-bit clear under OSPFv3
VRF, vrf_1:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 1
RP/0/RSP0/CPU0:router(config-ospfv3)#vrf vrf_1
RP/0/RSP0/CPU0:router(config-ospfv3-vrf)#stub-router router-lsa r-bit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1327
OSPFv3 Commands
summary-prefix (OSPFv3)
summary-prefix (OSPFv3)
To create aggregate addresses for routes being redistributed from another routing protocol into Open Shortest
Path First Version 3 (OSPFv3) protocol, use the summary-prefix command in an appropriate configuration
mode. To stop summarizing redistributed routes, use the no form of the command.
Syntax Description ipv6-prefix Summary prefix designated for a range of IP Version 6 (IPv6) prefixes.
This argument must be in the form documented in RFC 2373, where the address is specified
in hexadecimal using 16-bit values between colons.
/ prefix-length Length of the IPv6 prefix. A decimal value that indicates how many of the high-order
contiguous bits of the address compose the prefix (the network portion of the address). A
slash must precede the decimal value.
not-advertise (Optional) Suppresses summary routes that match the address and mask pair from being
advertised.
tag tag (Optional) Specifies a tag value that can be used as a “match” value for controlling
redistribution.
Command Default When this command is not used in router configuration mode, aggregate addresses are not created for routes
being redistributed from another routing protocol into the OSFPv3 protocol.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the summary-prefix command to cause an OSPFv3 Autonomous System Boundary Router (ASBR) to
advertise one external route as an aggregate for all redistributed routes that are covered by the address. This
command summarizes only routes from other routing protocols that are being redistributed into OSPFv3.
You can use this command multiple times to summarize multiple groups of addresses. The metric used to
advertise the summary is the lowest metric of all the more specific routes. This command helps reduce the
size of the routing table.
If you want to summarize routes between OSPFv3 areas, use the range command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1328
OSPFv3 Commands
summary-prefix (OSPFv3)
ospf read,
write
Examples In the following example, if summary prefix 4004:f000:132 is configured and routes 4004:f000:1::/64,
4004:f000:2::/64, and 4004:f000:3::/64 are redistributed into OSPFv3; only route 4004:f000::/32 is
advertised in an external link-state advertisement:
range (OSPFv3), on page 1256 Consolidates and summarizes routes at an area boundary.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1329
OSPFv3 Commands
timers lsa arrival
Syntax Description milliseconds Minimum delay (in milliseconds) that must pass between acceptance of the same LSA arriving
from neighbors. Range is 0 to 60000 milliseconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the timers lsa arrival command to control the minimum interval for accepting the same LSA. The same
LSA is an LSA instance that contains the same LSA ID number, LSA type, and advertising router ID. If an
instance of the same LSA arrives sooner than the interval that is set, the LSA is dropped.
We recommended that the milliseconds value of the timers lsa arrival command be less than or equal to
the hold-interval value of the timers throttle lsa all command for the neighbor.
ospf read,
write
Examples The following example shows how to set the minimum interval for accepting the same LSA at 2000
milliseconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1330
OSPFv3 Commands
timers lsa arrival
timers throttle lsa all (OSPFv3), on page 1338 Sets rate-limiting values for LSAs being generated.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1331
OSPFv3 Commands
timers pacing flood
Syntax Description milliseconds Time (in milliseconds) at which LSAs in the flooding queue are paced in between updates.
Range is 5 milliseconds to 100 milliseconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Configuring OSPFv3 flood pacing timers allows you to control interpacket spacing between consecutive
link-state update packets in the OSPF transmission queue. Use the timers pacing flood command to control
the rate at which LSA updates occur, thereby preventing high CPU or buffer utilization that can result when
an area is flooded with a very large number of LSAs.
The default settings for OSPFv3 packet pacing timers are suitable for the majority of OSPFv3 deployments.
Do not change the packet pacing timers unless all other options to meet OSPFv3 packet flooding requirements
have been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue
tuning, and buffer tuning before changing the default flood timers. Furthermore, no guidelines exist for
changing timer values; each OSPFv3 deployment is unique and should be considered on a case-by-case basis.
The network operator assumes risks associated with changing the default flood timer values.
ospf read,
write
Examples The following example shows how to configure LSA flood packet-pacing updates to occur in
55-millisecond intervals for OSPFv3 routing process 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1332
OSPFv3 Commands
timers pacing flood
show ospfv3, on page 1269 Displays general information about OSPFv3 routing processes.
timers pacing lsa-group, on page 1334 Changes the interval at which OSPFv3 link-state advertisements
(LSAs) are collected into a group and refreshed, checksummed,
or aged
timers pacing retransmission , on page 1336 Configures LSA retransmission packet pacing.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1333
OSPFv3 Commands
timers pacing lsa-group
Syntax Description seconds Interval (in seconds) at which LSAs are grouped and refreshed, checksummed, or aged. Range is
10 to 1800 seconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the timers pacing lsa-group command to control the rate at which LSA updates occur so that high CPU
or buffer utilization that can occur when an area is flooded with a very large number of LSAs can be reduced.
The default settings for OSPFv3 packet pacing timers are suitable for the majority of deployments. Do not
change the packet pacing timers unless all other options to meet OSPFv3 packet flooding requirements have
been exhausted. Specifically, network operators should prefer summarization, stub area usage, queue tuning,
and buffer tuning before changing the default flooding timers. Furthermore, no guidelines exist for changing
timer values; each OSPFv3 deployment is unique and should be considered on a case-by-case basis. The
network operator assumes the risks associated with changing the default timer values.
Cisco IOS XR software groups the periodic refresh of LSAs to improve the LSA packing density for the
refreshes in large topologies. The group timer controls the interval used for group refreshment of LSAs;
however, this timer does not change the frequency that individual LSAs are refreshed (the default refresh rate
is every 30 minutes).
The duration of the LSA group pacing is inversely proportional to the number of LSAs the router is handling.
For example, if you have about 10,000 LSAs, decreasing the pacing interval would benefit you. If you have
a very small database (40 to 100 LSAs), increasing the pacing interval to 10 to 20 minutes might benefit you
slightly.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1334
OSPFv3 Commands
timers pacing lsa-group
ospf read,
write
Examples The following example shows how to configure OSPFv3 group packet-pacing updates between LSA
groups to occur in 60-second intervals for OSPFv3 routing process 1:
show ospfv3, on page 1269 Displays general information about OSPFv3 routing processes.
timers pacing flood, on page 1332 Configures LSA flood packet pacing.
timers pacing retransmission , on page 1336 Configures LSA retransmission packet pacing.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1335
OSPFv3 Commands
timers pacing retransmission
Syntax Description milliseconds Time (in milliseconds) at which LSAs in the retransmission queue are paced. Range is 5
milliseconds to 100 milliseconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the timers pacing retransmission command to control interpacket spacing between consecutive link-state
update packets in the OSPFv3 retransmission queue. This command controls the rate at which LSA updates
occur. When an area is flooded with a very large number of LSAs, the LSA updates can result in high CPU
or buffer utilization. Using this command reduces CPU or buffer utilization.
The default settings for OSPFv3 packet retransmission pacing timers are suitable for the majority of
deployments. Do not change the packet retransmission pacing timers unless all other options to meet OSPFv3
packet flooding requirements have been exhausted. Specifically, network operators should prefer summarization,
stub area usage, queue tuning, and buffer tuning before changing the default flooding timers. Furthermore,
no guidelines exist for changing timer values; each OSPFv3 deployment is unique and should be considered
on a case-by-case basis. The network operator assumes risks associated with changing the default packet
retransmission pacing timer values.
ospf read,
write
Examples The following example shows how to configure LSA flood pacing updates to occur in 55-millisecond
intervals for OSPFv3 routing process 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1336
OSPFv3 Commands
timers pacing retransmission
show ospfv3, on page 1269 Displays general information about OSPFv3 routing processes.
timers pacing flood, on page 1332 Configures LSA flood packet pacing.
timers pacing lsa-group, on page 1334 Changes the interval at which OSPFv3 LSAs are collected into a group
and refreshed, checksummed, or aged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1337
OSPFv3 Commands
timers throttle lsa all (OSPFv3)
Syntax Description start-interval Minimum delay (in milliseconds) for the generation of LSAs. The first instance of LSA is
always generated immediately upon a local OSPFv3 topology change. The generation of the
next LSA is not before the start interval. Range is 0 to 600000 milliseconds.
hold-interval Incremental time (in milliseconds). This value is used to calculate the subsequent rate limiting
times for LSA generation. Range is 1 to 600000 milliseconds.
max-interval Maximum wait time (in milliseconds) between generation of the same LSA. Range is 1 to
600000 milliseconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration mode.
Release 4.3.0 The default timers throttle lsa values were changed to: start-interval: 50 milliseconds and
hold-interval: 200 milliseconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The “same LSA” is defined as an LSA instance that contains the same LSA ID number, LSA type, and
advertising router ID. We recommend that you keep the milliseconds value of the timers lsa arrival
command less than or equal to the hold-interval value of the timers throttle lsa all command.
ospf read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1338
OSPFv3 Commands
timers throttle lsa all (OSPFv3)
Examples This example shows how to customize OSPFv3 LSA throttling so that the start interval is 200
milliseconds, the hold interval is 10,000 milliseconds, and the maximum interval is 45,000
milliseconds. The minimum interval between instances of receiving the same LSA is 2000
milliseconds.
show ospfv3, on page 1269 Displays general information about OSPFv3 routing processes.
timers lsa arrival, on page 1330 Sets the minimum interval at which the software accepts the same LSA from
OSPFv3 neighbors.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1339
OSPFv3 Commands
timers throttle spf (OSPFv3)
Syntax Description spf-start Initial SPF schedule delay (in milliseconds). Range is 1 to 600000 milliseconds.
spf-hold Minimum hold time (in milliseconds) between two consecutive SPF calculations. Range is
1 to 600000 milliseconds.
spf-max-wait Maximum wait time (in milliseconds) between two consecutive SPF calculations. Range is
1 to 600000 milliseconds.
Release 4.1.0 This command was supported under OSPFv3 VRF configuration mode.
Release 4.3.0 The default timers throttle spf values were changed to: spf-start: 50 milliseconds, spf-hold:
200 milliseconds, and spf-max-wait: 5000 milliseconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The first wait interval between SPF calculations is the amount of time (in milliseconds) specified by the
spf-start argument. Each consecutive wait interval is twice the current hold level (in milliseconds) until the
wait time reaches the maximum time (in milliseconds) as specified by the spf-max-wait argument. Subsequent
wait times remain at the maximum until the values are reset or a link-state advertisement (LSA) is received
between SPF calculations.
Tip Setting a low spf-start time and spf-hold time causes routing to switch to the alternate path more quickly
if a failure occurs. However, it consumes more CPU processing time.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1340
OSPFv3 Commands
timers throttle spf (OSPFv3)
ospf read,
write
Examples The following example shows how to change the start, hold, and maximum wait interval values to
5, 1000, and 90,000 milliseconds, respectively:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1341
OSPFv3 Commands
trace (OSPFv3)
trace (OSPFv3)
To specify the Open Shortest Path First Version 3 (OSPFv3) buffer size, use the trace command in router
ospfv3 configuration mode. To return to the default value, use the no form of this command.
Syntax Description size Deletes existing buffer and creates one with N entries.
buffer_name Specifies a buffer from one of the 15 listed buffers. Refer Table 141: Buffer Types, on page
1342 table for details on the buffers.
size Specifies allowed size for the selected buffer. Options are: 0, 256, 1024, 2048, 4096, 8192,
16384, 32768, and 65536.
Select 0 to disable traces.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Trace buffers are used to store various traffic and processing events during the runtime. Large buffers can
store more events. If the buffer becomes full, old entries are overwritten by the latest entries. In a large network,
user may want to increase the trace buffer size to accommodate more events.
Name Description
adj adjacency
adj_cycle dbd/flood events/pkts
config config events
errors errors
events mda/rtrid/bfd/vrf
ha startup/HA/NSF
hello hello events/pkts
idb interface
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1342
OSPFv3 Commands
trace (OSPFv3)
Name Description
pkt I/O packets
rib rib batching
spf spf/topology
spf_cycle spf/topology detail
te mpls-te
test testing info
mq message queue info
ospf read,
write
Examples This example shows how to set 1024 error trace entries:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 osp3
RP/0/RSP0/CPU0:router(config-ospfv3)#trace size errors ?
0 disable trace
256 trace entries
512 trace entries
1024 trace entries
2048 trace entries
4096 trace entries
8192 trace entries
16384 trace entries
32768 trace entries
65536 trace entries
RP/0/RSP0/CPU0:router(config-ospfv3)#trace size errors 1024
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1343
OSPFv3 Commands
transmit-delay (OSPFv3)
transmit-delay (OSPFv3)
To set the estimated time required to send a link-state update packet on the interface, use the transmit-delay
command in an appropriate configuration mode. To return to the default value, use the no form of this
command.
transmit-delay seconds
no transmit-delay seconds
Syntax Description seconds Time (in seconds) required to send a link-state update. Range is 1 to 65535 seconds.
Area configuration
Interface configuration
Virtual-link configuration
Release 4.1.0 This command was supported under OSPFv3 VRF configuration submode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Link-state advertisements (LSAs) in the update packet must have their ages incremented by the amount
specified in the seconds argument before transmission. The value assigned should take into account the
transmission and propagation delays for the interface.
If the delay is not added before transmission over a link, the time in which the LSA propagates over the link
is not considered. This setting has more significance on very low-speed links.
ospf read,
write
Examples The following example shows how to configure a transmit delay of 3 seconds for GigabitEthernet
interface 0/3/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1344
OSPFv3 Commands
transmit-delay (OSPFv3)
show ospfv3, on page 1269 Displays general information about OSPF routing processes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1345
OSPFv3 Commands
virtual-link (OSPFv3)
virtual-link (OSPFv3)
To define an Open Shortest Path First Version 3 (OSPFv3) virtual link, use the virtual-link command in
area configuration mode. To remove a virtual link, use the no form of this command.
virtual-link router-id
no virtual-link
Syntax Description router-id Router ID associated with the virtual link neighbor. The router ID appears in the show ospfv3
display. This value must be entered in 32-bit dotted-decimal notation, similar to an IP Version
4 (IPv4) address. There is no default.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In OSPFv3, when there exists a path through another non-backbone area over which the virtual link can
function, all areas must be connected to a backbone area. If the connection to the backbone is lost, it can be
repaired by establishing a virtual link.
Virtual links, which are defined in the submode of the area they transit, are in effect virtual point-to-point
interfaces belonging to area 0 (the backbone). The virtual links inherit parameter values from the backbone
area, rather than the transit area in which they are defined.
Each virtual link neighbor must include the router ID of the virtual link neighbor for the link to be properly
established. Use the show ospfv3 command to display the router ID of an OSPFv3 process.
Use the virtual-link command to place the router in virtual-link configuration mode (config-router-ar-vl),
from which you can configure virtual-link-specific settings. Commands configured under this mode (such as
the transmit-delay command) are automatically bound to that virtual link.
ospf read,
write
Examples The following example shows how to establish a virtual link with default values for all optional
parameters:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1346
OSPFv3 Commands
virtual-link (OSPFv3)
RP/0/RSP0/CPU0:router(config-ospfv3)# area 1
RP/0/RSP0/CPU0:router(config-ospfv3-ar)# virtual-link 10.3.4.5
show ospfv3, on page 1269 Displays general information about OSPF routing processes.
transmit-delay (OSPFv3), on page 1344 Sets the estimated time required to send a link-state update packet
on the interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1347
OSPFv3 Commands
vrf (OSPFv3)
vrf (OSPFv3)
To configure an Open Shortest Path First Version 3 (OSPFv3) VPN routing and forwarding (VRF) instance
and enter OSPFv3 VRF configuration submode, use the vrf command in router configuration mode. To
terminate an OSPFv3 VRF, use the no form of this command.
vrf vrf-name
no vrf vrf-name
Syntax Description vrf-name Specifies a name for the OSPFV3 vrf. If a name is not specified, the default vrf is assumed.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vrf command to explicitly configure a VRF. This command creates a separate instance of OSPFv3
within the process. Commands configured under the VRF configuration mode (such as the interface
[OSPFv3] and authentication [OSPFv3] commands) are automatically bound to that VRF.
To modify or remove the VRF, the vrf-name argument format must be the same as the format used when
creating the VRF.
This example shows how to configure VRF vrf_1 and enter OSPFv3 VRF configuration submode:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospfv3 osp3
RP/0/RSP0/CPU0:router(config-ospfv3)#vrf vrf_1
RP/0/RSP0/CPU0:router(config-ospfv3-vrf)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1348
RIB Commands
This module describes the commands used to display and clear information in the Routing Information Base
(RIB).
For detailed information about RIB concepts, configuration tasks, and examples, see the Implementing RIB
on Cisco ASR 9000 Series Router module in Routing Configuration Guide for Cisco ASR 9000 Series
Routers.
• address-family next-hop dampening disable, on page 1351
• clear route, on page 1352
• maximum prefix (RIB), on page 1354
• lcc, on page 1356
• rcc, on page 1357
• recursion-depth-max, on page 1359
• router rib, on page 1360
• rump always-replicate, on page 1361
• show lcc statistics, on page 1362
• show rcc, on page 1364
• show rcc statistics, on page 1366
• show rcc vrf, on page 1368
• show rib, on page 1369
• show rib afi-all, on page 1371
• show rib attributes, on page 1373
• show rib client-id, on page 1374
• show rib clients, on page 1376
• show rib extcomms, on page 1378
• show rib firsthop, on page 1380
• show rib history, on page 1382
• show rib next-hop, on page 1384
• show rib opaques, on page 1386
• show rib protocols, on page 1388
• show rib recursion-depth-max, on page 1390
• show rib statistics, on page 1392
• show rib tables, on page 1395
• show rib trace, on page 1397
• show rib vpn-attributes, on page 1399
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1349
RIB Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1350
RIB Commands
address-family next-hop dampening disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rib read,
write
Examples The following example shows how to disable RIB next-hop dampening for IPv6 address families:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router rib
RP/0/RSP0/CPU0:router(config-rib)# address-family ipv6 next-hop dampening disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1351
RIB Commands
clear route
clear route
To clear routes from the IP routing table, use the clear route command in EXEC configuration mode.
clear route [vrf {vrf-name | all}] {ipv4 | ipv6 | afi-all} {unicast | multicast | safi-all} [topology
topo-name] [ip-address mask]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
topology topo-name (Optional) Specifies topology table information and name of the topology table.
ip-address node-id (Optional) Clears hardware resource counters from the designated node. The node-id
argument is entered in the rack/slot/module notation.
Command Default If a vrf vrf-name is not specified, routes are cleared from the default IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1352
RIB Commands
clear route
Use the clear route command to clear routes from an IP routing table to a specific network, a matching
subnet address, or all routes.
rib read,
write
Examples The following example shows how to remove all routes matching the subnet address 192.168.2.0
and mask 255.255.255.0 from the IPv4 unicast routing table:
The following example shows how to remove all routes from the IPv4 unicast routing table:
RP/0/RSP0/CPU0:router# clear route ipv4 unicast
show route, on page 1403 Displays the current state of the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1353
RIB Commands
maximum prefix (RIB)
Syntax Description maximum Maximum number of prefixes allowed in the VRF instance. Range is 32 to 2000000.
mid-threshold (Optional) Integer specifying at what percentage of the maximum argument value the
software starts to generate a Simple Network Management Protocol (SNMP) trap. Range is
1 to 100.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the maximum prefix command to configure a maximum number of prefixes that a VRF instance is
allowed to receive.
rib read,
write
Examples The following example shows how to set the maximum number of prefixes allowed to 1000:
A maximum number of routes is applicable to dynamic routing protocols as well as static or connected
routes. When maximum prefix is configured, an syslog message is generated in the following
conditions:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1354
RIB Commands
maximum prefix (RIB)
1. if the number of routes is above the threshold when“maximum prefix” configuration has been
committed
2. if the number routes reaches the configured “maximum prefix” values for the VRF
show rib tables, on page 1395 Displays all tables known to the RIB.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1355
RIB Commands
lcc
lcc
To enable Label Consistency Checker (lcc) background scan for IPv6 or IPv4 labels, use the lcc enable
command in global configuration mode. To disable lcc background scan, use the no for of this command.
period milliseconds Specifies the period between scans in milliseconds. Range is 100 to 600000
milliseconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv6 read,
write
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#lcc ipv6 unicast enable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1356
RIB Commands
rcc
rcc
To enable Route Consistency Checker (rcc) background scan for IPv6 or IPv4 routes, use the rcc enable
command in global configuration mode. To disable rcc background scan, use the no form of this command.
period milliseconds Specifies the period between scans in milliseconds. Range is 100 to 600000
milliseconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the period option to control how often the scan be triggered. Each time the scan is triggered, the background
scan process resumes verification from where it was left out and sends one buffer’s worth of routes to the
forwarding information base (FIB).
ipv6 read,
write
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#rcc ipv6 unicast enable
This example shows how to enable rcc with a scan period of 500 milliseconds for IPv6 unicast:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1357
RIB Commands
rcc
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#rcc ipv6 unicast period 500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1358
RIB Commands
recursion-depth-max
recursion-depth-max
To set the maximum depth for route recursion checks, use the recursion-depth-max command in router
configuration mode. To set the recursion checks to the default value, use the no form of this command.
recursion-depth-max maximum
no recursion-depth-max maximum
Syntax Description maximum Maximum depth for recursion checks. Range is 5 to 16.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the recursion-depth-max command to configure a specific maximum number of recursion checks in
the range of 5 to 16.
rib read,
write
Examples The following example shows how to set the maximum depth for route recursion checks to 12:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# router rib
RP/0/RSP0/CPU0:router(config-rib)# recursion-depth-max 12
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1359
RIB Commands
router rib
router rib
To enter Routing Information Base (RIB) configuration mode, use the router rib command in global
configuration mode. To remove all RIB configurations and terminate the RIB routing process, use the no
form of this command.
router rib
no router rib
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
bgp read,
write
ospf read,
write
hsrp read,
write
isis read,
write
Examples The following example shows how to enter RIB configuration mode:
RP/0/RSP0/CPU0:router(config)# router rib
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1360
RIB Commands
rump always-replicate
rump always-replicate
To enable replication from uRIB to muRIB as usual even after features such as MTR are configured, use the
rump always-replicate command in router configuration mode. To diable replication from uRIB to muRIB,
use the no form of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Configuring the rump always-replicate command allows routers in a network to be upgraded to multitopology
routing gradually without a flag day where all routers need to be configured at the same time without major
service disruption. When rump always-replicate is configured, replicated routes are added into the muRIB
with the lowest admin distance. So if protocols are populating the muRIB, they continue to do so. For the
same route, protocol routes win over replicated routes because of higher admin distance.
If an unwanted more specific route comes from the uRIB, optionally provide an access list through which the
replicated routes are run. If the route passes the access list, the route is replicated by RUMP.
rib read,
write
Examples The following example shows how to enale replication from uRIB to muRIB:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1361
RIB Commands
show lcc statistics
scan-id scan-id-value Specifies the scan ID value. The range is between <0-100000>.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv6 read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1362
RIB Commands
show lcc statistics
End Of Logs
End Of Logs
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1363
RIB Commands
show rcc
show rcc
To display route consistency checker (RCC) information, use the show rcc command in EXEC mode.
vrf vrf-name (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv4 read
Examples The following is sample output from the show rcc command:
Paused By:
route churn:False on-demand scan:False error scan:False
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1364
RIB Commands
show rcc
Scan Logs
=========
Legend:
? - Currently Inactive Node, ! - Non-standard SVD Role
* - Node did not reply
End of Logs
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1365
RIB Commands
show rcc statistics
scan-id scan-id-value Specifies the scan ID value. The range is between <0-100000>.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv6 read
This example shows background scan statistics for AFI-SAFI IPv6 unicast:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1366
RIB Commands
show rcc statistics
End Of Logs
This example shows background scan statistics for AFI-SAFI Ipv4 unicast:
End Of Logs
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1367
RIB Commands
show rcc vrf
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv6 read
This example shows how to run on-demand rcc scan for an IPv6 prefix:
This example shows how to run on-demand rcc scan for an Ipv4 prefix:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1368
RIB Commands
show rib
show rib
To display Routing Information Base (RIB) data, use the show rib command in EXEC mode.
show rib {ipv4 | ipv6} {unicast | multicast}[{firsthop | [{ type interface-path-id}] | next-hop | [{ type
interface-path-id}] | opaques | {attribute | ip-nexthop | ipfrr | safi-tunnel | summary | tunnel-nexthop}
| protocols | [{standby}] | statistics | [{name}] | [{standby}] | topology | {topo-name | all}}]
type Interface type. For more information, use the question mark (?) online help function.
For more information about the syntax for the router, use the question mark (?) online
help function.
safi-tunnel (Optional) Specifies subaddress family (SAFI) tunnel opaque data installed in the RIB.
tunnel-nexthop (Optional) Specifies tunnel next-hop opaque data installed in the RIB.
all (Optional) Specifies that all topology table information should be displayed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1369
RIB Commands
show rib
Release 5.1 The output of this command is modified to include next-hop identifier (NHID).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv4 read
ipv4 multicast
topology
BLUE
show rib afi-all, on page 1371 Displays both IPv4 and IPv6 RIB information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1370
RIB Commands
show rib afi-all
show rib afi-all [attributes] [client-id] [clients] [extcomms] [firsthop] [history] [multicast]
[next-hop] [opaques] [protocols] [recursion-depth-max] [safi-all] [statistics] [tables] [trace]
[unicast] [vpn-attributes]
Syntax Description attributes (Optional) Displays all BGP attributes installed in RIB.
client-id (Optional) Displays RIB client ID for longer history of redistributed routes sent to
the client.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1371
RIB Commands
show rib afi-all
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv4 read
Examples The following example illustrates the show rib afi-all attributes command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1372
RIB Commands
show rib attributes
Syntax Description summary (Optional) Displays a summary of BGP attribute data installed in the RIB.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rib read
Examples The following is sample output from the show rib attributes command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1373
RIB Commands
show rib client-id
redistribution history Displays longer history of redistributed routes sent to RIB clients.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib client-id command to display a history of the route additions, deletions, and updates sent
from RIB to the client across VRFs.
rib read
Examples The following is sample output from the show rib client-id command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1374
RIB Commands
show rib client-id
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1375
RIB Commands
show rib clients
show rib [{afi-all | ipv4 | ipv6}] clients [{protocols | redistribution [history]}] [standby]
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib clients command to display the list of clients who have registered with RIB, what protocol
routes they are redistributing, and a history of the routes sent to the client.
The maximum number of redistribution entries is 5000 for Bulk Content Downloader (BCDL) and 500 for
other protocols.
rib read
Examples The following is sample output from the show rib clients command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1376
RIB Commands
show rib clients
isis node0_5_CPU0
ipv4 uni vrf default insync route
static insync
ospf node0_5_CPU0
ipv4 uni vrf default insync route
static insync
local insync
bgp node0_5_CPU0
ipv4 uni vrf abc insync route
static insync
bcdl_agent node0_5_CPU0
ipv4 uni vrf default insync rib_fib
ipv4 uni vrf bar insync rib_fib
ipv4 uni vrf abc insync rib_fib
ipv4 uni vrf test insync rib_fib
Field Description
Redist Whether the client is redistributing any protocols or not and whether it has read all routes from
RIB or not.
• insync—read
• outsync—not read.
Proto Whether the protocol has sent all its routes to RIB and signaled update complete or not.
• insync—read
• outsync—not read.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1377
RIB Commands
show rib extcomms
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rib read
Examples The following is sample output from the show rib extcomms command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1378
RIB Commands
show rib extcomms
Field Description
Extended Community Type of extended communities. Different protocols can add different extended
communities.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1379
RIB Commands
show rib firsthop
show rib [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | safi-all}] firsthop
[client-name] [{type interface-path-id | ip-address /prefix-length | ip-address mask | resolved | unresolved
| damped}] [summary] [standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
/ prefix-length (Optional) Length of the IP address prefix. A decimal value that indicates how many
of the high-order contiguous bits of the address compose the prefix (the network
portion of the address). A slash (/) must precede the decimal value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1380
RIB Commands
show rib firsthop
Command Default If a vrf vrf-name is not specified, the registered first-hop notifications addresses are displayed for the default
IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib firsthop command to display the list of first hops registered by various clients with RIB
and the address and interface through which they are resolved.
rib read
Examples The following is sample output from the show rib firsthop command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1381
RIB Commands
show rib history
client-id client-id (Optional) Specifies the ID of the client. Range for client-id argument is 0 to
4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib history command to display the list of routes that RIB has sent to various clients.
rib read
Examples The following is sample output from the show rib history command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1382
RIB Commands
show rib history
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1383
RIB Commands
show rib next-hop
show rib [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | safi-all}] next-hop
[client-name] [{type interface-path-id | ip-address /prefix-length | ip-address mask | resolved | unresolved
| damped}] [summary] [standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
ip-address (Optional) Network IP address about which routing information should be displayed.
/ prefix-length (Optional) Length of the IP address prefix. A decimal value that indicates how many
of the high-order contiguous bits of the address compose the prefix (the network
portion of the address). A slash (/) must precede the decimal value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1384
RIB Commands
show rib next-hop
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib next-hop command to display the list of next-hops registered by various clients with the
RIB and the address and interface through which they are resolved.
rib read
Examples The following is sample output from the show rib next-hop command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1385
RIB Commands
show rib opaques
show rib [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | safi-all}] opaques
{attribute | ip-nexthop | ipfrr | safi-tunnel | summary | tunnel-nexthop} [rib-client-name] [standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
ipfrr Displays IP fast reroute (IPFRR) opaque data installed in the RIB.
safi-tunnel Displays subaddress family (SAFI) tunnel opaque data installed in the RIB.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1386
RIB Commands
show rib opaques
If information is not used by the RIB server process, it is viewed as opaque data. Use the show rib opaques
command to display opaque data installed in the RIB.
rib read
Examples The following is sample output from the show rib opaques command:
Field Description
Opaque key Unique key for the opaque data as populated by the protocol client.
show ospf routes, on page 1144 Displays Open Shortest Path First (OSPF) topology
table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1387
RIB Commands
show rib protocols
show rib [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | safi-all}] protocols
[standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If a vrf vrf-name is not specified, the registered first-hop notification addresses are displayed for the default
IPv4 unicast VRF.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rib read
Examples The following is sample output from the show rib protocols command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1388
RIB Commands
show rib protocols
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1389
RIB Commands
show rib recursion-depth-max
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib recursion-depth-max command to display the maximum recursion depth for RIB. Recursion
depth is the number of next-hops that can be specified.
rib read
Examples The following is sample output from the show rib recursion-depth-max command:
IPv4:
-----
Maximum recursion depth in RIB:
Configured: 12
In Use: 128
IPv6:
-----
Maximum recursion depth in RIB:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1390
RIB Commands
show rib recursion-depth-max
Configured: 12
In Use: 128
Field Description
In Use Value of maximum recursion depth RIB is using. This value can be different from the configured
value because RIB has to be restarted after the configuration is changed for the new configuration
to be effective.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1391
RIB Commands
show rib statistics
show rib [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | safi-all}] statistics
[client-name] [standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If vrf vrf-name is not specified, the registered first-hop notification addresses are displayed for the default
IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib statistics command to display RIB statistics. The statistics include requests sent from the
clients to the RIB and the information redistributed to the client.
RIB maintains counters for all requests sent from a client including:
• Route operations
• Table registrations
• Next-hop registrations
• Redistribution registrations
• Attribute registrations
• Synchronization completion
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1392
RIB Commands
show rib statistics
rib read
Examples The following is sample output from the show rib statistics command:
RIB Statistics:
Received 142 batch messages
137 route operations, 0 attribute operations
0 opaque operations
11 complete operations, 0 convergent operations
Results of the batch message received:
142 successes
0 forward references, 0 invalid client id, 0 unknown errors
0 memory allocation errors, 0 client lookup errors, table lookup errors 0
0 proto lookup errors, 0 client proto lookup errors
ipv4_connected/node0_RP0_CPU0 last performed route operation
with status BATCH_SUCESS at Jun 26 21:43:33.601
Field Description
Received n light weight messages Number of lightweight API messages sent from RIB clients.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1393
RIB Commands
show rib statistics
Field Description
Received n nexthop batch messages Number of batch API messages sent from RIB clients received by
the RIB.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1394
RIB Commands
show rib tables
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rib tables command to display all tables known to the RIB, including table attributes. Attributes
include VPN routing and forwarding (VRF) instance, address family, and maximum prefix information.
rib read
Examples The following is sample output from the show rib tables command when entered without an address:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1395
RIB Commands
show rib tables
Field Description
F Forward referenced. If Y is indicated, a table has been created by RIB because a client has
registered for the table, but RIB has not heard from the router space infrastructure (RSI) about
the table. RSI manages the tables.
D If Y is indicated, the table has been deleted in the RSI but RIB has not cleared the information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1396
RIB Commands
show rib trace
show rib [{afi-all | ipv4 | ipv6}] trace [{clear | counts | event-manager | startup | sync | timing}]
[{unique | wrapping}] [last entries] [hexdump] [reverse] [tailif] [stats] [verbose] [{file name
original location node-id | location {allnode-id}}]
last entries (Optional) Displays a specified number of the last entries. Range is 1 to
4294967295.
file name original location (Optional) Displays trace entries for a specific file for the designated
node-id node. The node-id argument is entered in the rack/slot/module notation.
location { all | node-id } (Optional) Displays ltrace entries for the designated node. The node-id
argument is entered in the rack/slot/module notation. The all keyword
displays ltrace entries for all nodes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1397
RIB Commands
show rib trace
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rib read
Examples The following is sample output from the show rib trace command
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1398
RIB Commands
show rib vpn-attributes
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rib read
Examples The following is sample output from the show rib vpn-attributes command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1399
RIB Commands
show rib vpn-attributes
EIGRP AD:444:51200 1
EIGRP AD:444:153600 2
EIGRP RHB:255:0:16384 2
EIGRP RHB:255:1:16384 5
EIGRP RHB:255:1:256000 1
EIGRP LM:0x0:1:1500 3
EIGRP LM:0x0:1:1514 2
EIGRP LM:0x0:1:4470 3
EIGRP AR:0:192.168.0.13 6
EIGRP PM:11:0 6
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1400
RIB Commands
show rib vrf
show rib vrf {vrf-name | all} [ipv4] [ipv6] [afi-all] [firsthop] [next-hop] [opaques] [protocols]
[statistics name]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
statistics name (Optional) Specifies RIB statistics for the given name.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
ipv4 read
Examples The following example shows output from the show rib vrf all statistics command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1401
RIB Commands
show rib vrf
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1402
RIB Commands
show route
show route
To display the current routes in the Routing Information Base (RIB), use the show route command in EXEC
mode.
show route [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | safi-all}] [{protocol
[instance] | ip-address [mask] | ip-address/prefix-length}] [standby] [detail]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
protocol (Optional) Name of a routing protocol. If you specify a routing protocol, use one
of the following keywords:
• bgp
• eigrp
• isis
• ospf
• rip
• static
• local
• connected
instance (Optional) Number or name used to identify an instance of the specified protocol.
ip-address (Optional) Network IP address about which routing information should be displayed.
/prefix-length (Optional) Length of the IP address prefix. A decimal value that indicates how many
of the high-order contiguous bits of the address compose the prefix (the network
portion of the address). A slash (/) must precede the decimal value.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1403
RIB Commands
show route
Command Default If a vrf vrf-name is not specified, routes are displayed for the default IPv4 unicast VRF.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported. The input
parameters and output were modified to display 4-byte autonomous system numbers and
extended communities in either asplain or asdot notations.
Release 5.1 The output of this command is modified to include next-hop identifier (NHID).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the afi-all keyword is used, the ip-address and mask arguments are not available.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route command when entered without an address:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1404
RIB Commands
show route
Field Description
S* Code indicating how the route was derived. See the code legend preceding the
output. In this case, the route was derived from a static (candidate default).
[1/0] First number in the brackets is the administrative distance of the information source;
the second number is the metric for the route.
MgmtEthernet Specifies the interface through which the specified network can be reached.
0/5/CPU0/0
C Code indicating how the route was derived. See the code legend preceding the
output. In this case, the route was connected.
L Code indicating how the route was derived. See the code legend preceding the
output. In this case, the route was local.
O Code indicating how the route was derived. See the code legend preceding the
output. In this case, the route was on-demand routing (ODR).
E2 Code indicating how the route was derived. See the code legend preceding the
output. In this case, the route was OSPF external type 2.
8.2.8.0/24 Address and prefix length of the remote network connected to the static route.
via 3.3.3.1 Specifies the address of the next router to the remote network.
When you specify that you want information about a particular network, more detailed statistics are
displayed. The following is sample output from the show route command when entered with an
IP address:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1405
RIB Commands
show route
Intermediate System-to-Intermediate System (IS-IS) includes an IP address typed length value (TLV)
in its link-state packet (LSP) that helps identify the node injecting the route into the network. The
IS-IS node uses one of its own interface addresses in this TLV. A loopback address is preferred
among interfaces configured under IS-IS. When other networking devices calculate IP routes, they
can store the IP address as the originator address with each route in the routing table.
The following example shows the output from the show route command for a specific IP address
on a router configured with IS-IS. Each path that is shown under the Routing Descriptor Blocks
report displays two IP addresses. The first address (10.0.0.9) is the next-hop address; the second is
the originator IP address from the advertising IS-IS router.
Field Description
Routing Descriptor Blocks: Displays the next-hop IP address followed by the information source.
from ... via ... First address is the next-hop IP address, and the other is the information source.
This report is followed by the interface for this route.
No advertising protos. Indicates that no other protocols are advertising the route to their redistribution
consumers. If the route is being advertised, protocols are listed in the following
manner:
Redist Advertisers:
isis p
ospf 43
The following example illustrates the show route command with the topology topo-name keyword
and argument specified:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1406
RIB Commands
show route
This example is a sample show route detail command output that displays path ID and backup-path
ID information:
show route summary, on page 1428 Displays the current contents of the routing table in summary format.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1407
RIB Commands
show route
Command Description
show rib opaques, on page 1386 Displays opaque data installed in the Routing Information Base (RIB).
show ospf routes, on page 1144 Displays Open Shortest Path First (OSPF) topology table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1408
RIB Commands
show route backup
show route [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | {topology topo-name}
| safi-all}] backup [{ip-address [mask] ip-address /prefix-length] }][standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
ip-address (Optional) Network IP address about which backup routing information should be
displayed.
/prefix-length (Optional) Length of the IP address prefix. A decimal value that indicates how many
of the high-order contiguous bits of the address compose the prefix (the network
portion of the address). A slash (/) must precede the decimal value.
Command Default If a vrf vrf-name is not specified, the backup routes from the RIB are displayed for the default IPv4 unicast
VRF.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1409
RIB Commands
show route backup
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route backup command to display information about routes that have been installed into the
RIB as backup routes. This command also displays information about the currently selected active route for
which there is a backup.
When the afi-all keyword is used, the ip-address and mask arguments are not available.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route backup command:
Field Description
S Code indicating how the route was derived. See the legend of the codes preceding
the output.
2d20h Time (in hh:mm:ss) since the route was installed in the RIB.
Backup Identifies the entry as a backup version of the route, typically installed by a different
routing protocol.
O Code indicating how the route was derived. See the code legend preceding the output.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1410
RIB Commands
show route backup
Field Description
E2 Code for the type of route. This code is relevant only for OSPF and IS-IS routes.
The codes for an OSPF route can be:
none—intra-area route
IA—interarea route
E1—external type 1
E2—external type 2
N1—NSSA external type 1
N2—NSSA external type 2
The codes for an IS-IS route can be:
L1—level 1
L2—level 2
ia—interarea
su—summary route
show route, on page 1403 Displays the current routes in the RIB.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1411
RIB Commands
show route best-local
show route [vrf {vrf-name | all}] [{ipv4 | ipv6}] [{unicast | multicast | {topology topo-name} | safi-all}]
best-local ip-address [ standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If a vrf vrf-name is not specified, the best local address is displayed for the default IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route best-local command to display information about the best local routes in the routing
table.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route best-local command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1412
RIB Commands
show route best-local
Field Description
Routing Descriptor Blocks: Displays the next-hop IP address followed by the information source.
10.12.12.1 Directly connected ... via First address is the next-hop IP address, followed by a report that it
... is directly connected. This report is followed by the interface for this
route.
show route local, on page 1416 Displays local addresses installed in the RIB as a receive entry.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1413
RIB Commands
show route connected
show route [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | {topology topo-name}
| safi-all}] connected [ standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If a vrf vrf-name is not specified, the current connected routes of the routing table are displayed for the
default IPv4 unicast VRF.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route connected command to display information about connected routes in the routing table.
rib read
Examples The following is sample output from the show route connected command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1414
RIB Commands
show route connected
Field Description
13:43:40 Time (in hh:mm:ss) since the route was installed in the RIB.
show route summary, on page 1428 Displays the current contents of the RIB.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1415
RIB Commands
show route local
show route [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | {topology topo-name}
| safi-all}] local [{type interface -path-id}] [ standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? )
online help function.
Command Default If a vrf vrf-name is not specified, the local routes receiving updates from the RIB are displayed for the
default IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route local command to display information about local routes in the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1416
RIB Commands
show route local
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route local command:
Field Description
00:14:36 Time (in hh:mm:ss) since the route was installed in the RIB.
show route connected, on page 1414 Displays information about all clients that have registered with the RIB
as protocols.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1417
RIB Commands
show route longer-prefixes
show route [vrf {vrf-name | all}] [{ipv4 | ipv6}] [{unicast | multicast | {topology topo-name} | safi-all}]
longer-prefixes {ip-address mask ip-address/prefix-length} [ standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
/ prefix-length Length of the IP address prefix. A decimal value that indicates how many of the
high-order contiguous bits of the address compose the prefix (the network portion
of the address). A slash (/) must precede the decimal value.
Command Default If a vrf vrf-name is not specified, the current routes in the RIB sharing a specified number of bits with a
network are displayed for the default IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1418
RIB Commands
show route longer-prefixes
Use the show route longer-prefixes command to troubleshoot forwarding problems whose cause may be a
long prefix.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route longer-prefixes command:
Field Description
4d15h Time (in hh:mm:ss or ndnh) since the route was installed in the RIB.
show route summary, on page 1428 Displays the current contents of the routing table in summary format.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1419
RIB Commands
show route next-hop
show route [vrf {vrf-name | all}] [{ipv4 | ipv6}] [{unicast | multicast | {topology topo-name} | safi-all}]
next-hop [ip-address][{[standby]}]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If a vrf vrf-name is not specified, the next-hop gateway or host is displayed for the default IPv4 unicast
VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route next-hop command to find all routes going through a next-hop address or interface.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route next-hop command filtering routes on the
next-hop address:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1420
RIB Commands
show route next-hop
The following is sample output from the show route next-hop command filtering routes on the
next-hop interface:
Field Description
15:01:46 Time (in hh:mm:ss or ndnh) since the route was installed in the RIB.
show route, on page 1403 Displays the current contents of the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1421
RIB Commands
show route quarantined
show route [vrf {vrf-name | all}] [{ipv4 | ipv6}] [{unicast | multicast | {} | safi-all}] quarantined
[{ip-address/prefix-length]ip-address mask}] [standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
/ prefix-length (Optional) Length of the IP address prefix. A decimal value that indicates how many
of the high-order contiguous bits of the address compose the prefix (the network
portion of the address). A slash (/) must precede the decimal value.
Command Default If a vrf vrf-name is not specified, the next-hop gateway or host is displayed for the default IPv4 unicast
VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RIB quarantining detects mutually recursive routes and quarantines the last route that actually completes the
mutual recursion. The quarantined route is periodically evaluated to see if the mutual recursion has gone away.
If the recursion still exists, the route remains quarantined. If the recursion has gone away, the route is released
from quarantine.
Use the show route quarantined command to display mutually recursive (looping) routes.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1422
RIB Commands
show route quarantined
rib read
Examples The following is sample output from the show route quarantined command:
Field Description
00:00:01 Time (in hh:mm:ss or ndnh) since the route was installed in the RIB.
show route, on page 1403 Displays the current contents of the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1423
RIB Commands
show route resolving-next-hop
show route [vrf {vrf-name | all}] [{ipv4 | ipv6}] [{unicast | multicast | {topology topo-name} | safi-all}]
resolving-next-hop ip-address [ standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If a vrf vrf-name is not specified, the next-hop gateway or host is displayed for the default IPv4 unicast
VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route resolving-next-hop command to perform a recursive route lookup on the supplied
destination address and return information on the next immediate router (next hop) to the destination.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1424
RIB Commands
show route resolving-next-hop
Examples The following is sample output from the show route resolving-next-hop command:
Field Description
Known via Name of the routing protocol that installed the matching route.
show route, on page 1403 Displays the current contents of the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1425
RIB Commands
show route static
show route [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | {topology topo-name}
| safi-all}] static [ standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
Command Default If a vrf vrf-name is not specified, the current static routes of the RIB are displayed for the default IPv4
unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route static command to display information about static routes in the routing table.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
rib read
Examples The following is sample output from the show route static command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1426
RIB Commands
show route static
Field Description
00:54:05 Time (in hh:mm:ss) since the route was installed in the RIB.
show route, on page 1403 Displays the current contents of the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1427
RIB Commands
show route summary
show route [vrf {vrf-name | all}] [{afi-all | ipv4 | ipv6}] [{unicast | multicast | {topology topo-name}
| safi-all}] summary [detail] [standby]
Syntax Description vrf { vrf-name | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or
all VRF instances.
detail (Optional) Displays a detailed summary of the contents of the RIB, including the
number of paths and some protocol-specific route attributes.
Command Default If a vrf vrf-name is not specified, the contents of the RIB are displayed for the default IPv4 unicast VRF.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show route summary command to display information about routes in the routing information base.
When a route summary is needed frequently—for instance, in a polling situation—use the show route
summary command without the detail keyword. The detail keyword is used less frequently for verification
purposes, because it is much more expensive (in bandwidth), requiring a scan of the entire routing database.
The topology keyword must be accompanied by the ipv4 multicast keywords, except when the afi-all
keyword or the safi-all keyword is specified.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1428
RIB Commands
show route summary
rib read
Examples The following is sample output from the show route summary command:
This table explains fields in the output of the show route summary command.
Field Description
Routes Number of selected routes that are present in the routing table for each route source.
Backup Number of routes that are not selected (are backup to a selected route).
Deleted Number of routes that have been marked for deletion in the RIB, but have not yet been purged.
Memory Number of bytes allocated to maintain all routes for the particular route source.
The following is sample output from the show route summary command with the detail keyword:
Route Source Active Route Active Path Backup Route Backup Path
static 1 1 0 0
connected 2 2 1 1
local 3 3 0 0
isis 1 1 1 1
Level 1: 0 0 1 1
Level 2: 1 1 0 0
ospf 1673 6 12 0 0
Intra-Area: 3 6 0 0
Inter-Area: 3 6 0 0
External-1: 0 0 0 0
External-2: 0 0 0 0
bgp 100 10 20 4 8
External: 5 10 4 8
Internal: 5 10 0 0
local: 0 0 0 0
Total 7 7 2 2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1429
RIB Commands
show route summary
This table explains fields in the output of the show route summary detail command.
Field Description
Route Source Source of the route. Routing protocol name and type.
show route, on page 1403 Displays the current contents of the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1430
RIP Commands
This module describes the commands used to configure and monitor the Routing Information Protocol (RIP).
For detailed information about RIP concepts, configuration tasks, and examples, see the Implementing RIP
on Cisco ASR 9000 Series Router module in the Routing Configuration Guide for Cisco ASR 9000 Series
Routers.
• authentication keychain mode (RIP), on page 1433
• auto-summary (RIP), on page 1435
• broadcast-for-v2, on page 1436
• clear rip, on page 1437
• clear rip database, on page 1438
• clear rip interface, on page 1440
• clear rip out-of-memory, on page 1442
• clear rip statistics, on page 1444
• default-information originate (RIP), on page 1445
• default-metric (RIP), on page 1446
• distance (RIP), on page 1448
• interface (RIP), on page 1450
• maximum-paths (RIP), on page 1452
• metric-zero-accept, on page 1453
• neighbor (RIP), on page 1454
• nsf (RIP), on page 1456
• output-delay, on page 1457
• passive-interface (RIP), on page 1458
• poison-reverse, on page 1460
• receive version, on page 1462
• redistribute (RIP), on page 1463
• router rip, on page 1466
• route-policy (RIP), on page 1468
• send version, on page 1470
• show protocols (RIP), on page 1471
• show rip, on page 1473
• show rip database, on page 1475
• show rip interface, on page 1477
• show rip statistics, on page 1484
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1431
RIP Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1432
RIP Commands
authentication keychain mode (RIP)
Syntax Description keychain-name Specifies the name of the keychain configured using the keychain command.
Note All keychains need to be configured in Cisco IOS XR keychain database using
the keychain configuration commands described in Implementing Keychain
Management module of System Security Configuration Guide for Cisco ASR
9000 Series Routers
md5 Specifies that the authentication keychain mode is keyed message digest (md5).
VRF-interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
All keychains need to be configured in Cisco IOS XR keychain database using the keychain configuration
commands described in Implementing Keychain Management module of System Security Configuration Guide
for Cisco ASR 9000 Series Routers
This example shows how to configure an authentication keychain in md5 mode on a RIP VRF
interface:
RP/0/RSP0/CPU0:router#configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1433
RIP Commands
authentication keychain mode (RIP)
RP/0/RSP0/CPU0:router(config)#router rip
RP/0/RSP0/CPU0:router(config-rip)#vrf vrf_rip_auth
RP/0/RSP0/CPU0:router(config-rip-vrf)#interface POS 0/6/0/0
RP/0/RSP0/CPU0:router(config-rip-vrf-if)#authentication keychain key1 mode md5
This example shows how to configure an authentication keychain in clear text mode on a RIP interface:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router rip
RP/0/RSP0/CPU0:router(config-rip)#interface POS 0/6/0/1
RP/0/RSP0/CPU0:router(config-rip-if)#authentication keychain key2 mode text
vrf (RIP), on page 1493 Defines a VPN routing and forwarding (VRF) instance
and enters VRF configuration mode.
Refer System Security Command Reference for Cisco
ASR 9000 Series Routers for complete command
reference information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1434
RIP Commands
auto-summary (RIP)
auto-summary (RIP)
To enable the automatic summarization of subnet routes into network-level routes, use the auto-summary
command in the appropriate configuration mode. To disable this function and send subprefix routing information
across classful network boundaries, use the no form of this command.
auto-summary
no auto-summary
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the auto-summary command to turn on route summarization. Route summarization reduces the amount
of routing information in the routing tables.
Disable automatic summarization if you must perform routing between disconnected subnets. When automatic
summarization is off, subnets are advertised. Automatic summarization is disabled by default.
rip read,
write
vrf (RIP), on page 1493 Defines a VRF instance and enters VRF configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1435
RIP Commands
broadcast-for-v2
broadcast-for-v2
To send Routing Information Protocol (RIP) Version 2 output packets to a broadcast address, use the
broadcast-for-v2 command in the appropriate configuration mode. To disable this feature, use the no form
of this command.
broadcast-for-v2
no broadcast-for-v2
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the broadcast-for-v2 command to broadcast RIP Version 2 broadcast updates to hosts that do not listen
to multicasts. Version 2 updates (requests and responses) will be sent to the IP broadcast address
255.255.255.255 instead of the IP multicast address 244.0.0.9.
rip read,
write
Examples The following example shows how to send RIP v2 output messages to a broadcast address for all
RIP interfaces:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1436
RIP Commands
clear rip
clear rip
To clear VRF and interface-related information for Routing Information Protocol (RIP) such as database
entries and statistics, use the clear rip command in EXEC configuration mode.
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RIP VRFs and interfaces that are forcibly deactivated by the software because of a severe memory state are
not activated again until the out-of-memory state is cleared by using the clear rip , clear rip interface , or
clear rip out-of-memory command.
rip read
Examples The following example shows how to clear all database, interface, and VRF entries in RIP:
RP/0/RSP0/CPU0:routerr# clear rip vrf all
clear rip interface, on page 1440 Clears interface-related information for RIP such as database entries
and statistics.
clear rip out-of-memory, on page 1442 Clears the out-of-memory state for RIP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1437
RIP Commands
clear rip database
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read,
write
Examples The following example shows how to clear only database entries from the topology table for the
GigabitEthernet 0/1/0/0 interface:
RP/0/RSP0/CPU0:router# clear rip database interface GigabitEthernet 0/1/0/0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1438
RIP Commands
clear rip database
show rip statistics, on page 1484 Displays database and interface entry information for the RIP process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1439
RIP Commands
clear rip interface
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RIP VRFs and interfaces that are forcibly deactivated by the software because of a severe memory state are
not activated again until after out-of-memory state is cleared by using the clear rip , clear rip interface or
c lear rip out-of-memory command.
rip read,
write
Examples The following example shows how to clear all interface-related data such as routes and statistics
from the GigabitEthernet 0/1/0/0 interface:
RP/0/RSP0/CPU0:router# clear rip interface GigabitEthernet 0/1/0/0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1440
RIP Commands
clear rip interface
clear rip, on page 1437 Clears VRF and interface-related information for RIP such as database
entries and statistics.
clear rip out-of-memory, on page 1442 Clears the out-of-memory state for RIP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1441
RIP Commands
clear rip out-of-memory
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the clear rip out-of-memory command, to clear the out-of-memory state completely and allow the RIP
process to force the VRF or interface to shut down.
When the router begins to run out of memory, the RIP process can transition through different memory states
defined as Normal, Minor, Severe, and Critical:
• In Normal state, RIP VRFs and interfaces function normally.
• In Minor state, RIP VRFs and interfaces that are currently active are allowed to remain active. VRFs and
interfaces that are not currently active are not allowed to become active until the RIP process transitions
to Normal state.
• In Severe state, a few VRFs and interfaces are forcibly brought down periodically until the RIP process
transitions to another state.
• In Critical state, the RIP process is forcibly shut down.
VRFs and interfaces that are forcibly shut down in Severe state are not automatically activated when the RIP
process transitions to Minor or Normal state. When a VRF or interface is forcibly brought down while in
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1442
RIP Commands
clear rip out-of-memory
Severe state, the clear rip , clear rip interface or clear rip out-of-memory command clears the Forced
Down state and reactivates the VRF or interface.
The show rip and show rip interface commands allow you to view the current out-of-memory state.
rip read,
write
Examples The following example shows how to clear the out-of-memory state for a RIP process:
RP/0/RSP0/CPU0:router# clear rip out-of-memory
Related Commands clear rip, on page 1437 Clears VRF and interface-related information for RIP such as database
entries and statistics.
clear rip interface, on page 1440 Clears interface-related information for RIP such as database entries and
statistics.
show rip interface, on page 1477 Displays interface entry information from the RIP topology table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1443
RIP Commands
clear rip statistics
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
interface (Optional) Specifies the interface from which to clear topology entries.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read,
write
Examples The following example shows how to clear all RIP statistics:
RP/0/RSP0/CPU0:router# clear rip statistics
show rip statistics, on page 1484 Displays database and interface entry information for the RIP process.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1444
RIP Commands
default-information originate (RIP)
Syntax Description route-policy name Route policy name that indicates criteria for the default route.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read,
write
Examples The following example shows how to originate a default route in RIP updates based on the result of
running the route policy on the routing table:
route-policy (RIP), on page 1468 Applies a routing policy to updates advertised to or received from a RIP
neighbor.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1445
RIP Commands
default-metric (RIP)
default-metric (RIP)
To set default metric values for routes redistributed from other protocols into Routing Information Protocol
(RIP), use the default-metric command in the appropriate configuration mode. To return to the default state,
use the no form of this command.
default-metric number-value
no default-metric
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the default-metric command with the redistribute command to cause RIP to use the same metric
value for all redistributed routes. A default metric helps solve the problem of redistributing routes with
incompatible metrics by providing a reasonable substitute and enables redistribution to proceed. If you want
to set different metrics for other redistributed protocols, use the route-policy option in the redistribute
command.
The RIP metric used for redistributed routes is determined by the route policy. If a route policy is not configured
or the route policy does not set the RIP metric, the metric is determined based on the redistributed protocol.
For VPNv4 routes redistributed by BGP, the RIP metric set at the remote PE router is used, if valid.
In all other cases (BGP, IS-IS, OSPF, EIGRP, connected, static), the metric set by the default-metric
command is used. If a valid metric cannot be determined, then redistribution does not happen.
rip read,
write
Examples The following example shows how a router in autonomous system 109 uses both the RIP and the
Open Shortest Path First (OSPF) routing protocols. The example advertises OSPF-derived routes
using RIP and assigns the OSPF-derived routes a RIP metric of 10:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1446
RIP Commands
default-metric (RIP)
redistribute (RIP), on page 1463 Redistributes routes from one routing domain into RIP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1447
RIP Commands
distance (RIP)
distance (RIP)
To define the administrative distance assigned to routes discovered by the Routing Information Protocol (RIP),
use the distance admin-distance command in the appropriate configuration mode. To remove the distance
definition from the configuration file and restore the system to its default condition, use the no form of this
command.
Syntax Description admin-distance Administrative distance to be assigned to RIP routes. Range is 0 to 255.
prefix (Optional) Network IP address about which routing information should be displayed.
prefix-length (Optional) The prefix-length argument specifies the length of the IP prefix. A decimal value
that indicates how many of the high-order contiguous bits of the address compose the prefix
(the network portion of the address). A slash must precede the decimal value. Range is 0 to
32 for IPv4 addresses.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the distance command to change the preference of RIP routes over other protocol routes. When
administrative distance and redistribution features are used to together, routing behavior may be affected for
routes accepted from and advertised to RIP neighbors.
Numerically, an administrative distance is an integer from 0 to 255. In general, the higher the value, the lower
the trust rating. An administrative distance of 255 means that the routing information source cannot be trusted
at all and should be ignored.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1448
RIP Commands
distance (RIP)
The order in which you enter distance commands can affect the assigned administrative distances in unexpected
ways.
This table lists default administrative distances.
Connected interface 0
External BGP 20
Internal EIGRP 90
OSPF 110
IS-IS 115
Unknown 255
rip read,
write
Examples The following example shows how to set the administrative distance for a particular prefix:
redistribute (RIP), on page 1463 Redistributes routes from one routing domain into RIP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1449
RIP Commands
interface (RIP)
interface (RIP)
To define the interfaces on which the Routing Information Protocol (RIP) runs and enter interface configuration
mode, use the interface command in router configuration mode. To disable RIP routing for interfaces, use
the no form of this command.
Syntax Description type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Command Default When you do not specify this command in configuration mode, RIP routing for interfaces is not enabled.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the interface command to associate a specific interface with a RIP process. The interface remains
associated with the process even when the IPv4 address of the interface changes.
This command places the router in interface configuration mode, from which you can configure
interface-specific settings. Commands configured under this mode (such as the broadcast-for-v2, on page 1436
command) are automatically bound to that interface.
rip read,
write
Examples The following example shows how to enter interface configuration mode for a RIP process, and send
RIP Version 2 messages to the broadcast address on the GigabitEthernet interface 0/1/0/0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1450
RIP Commands
interface (RIP)
broadcast-for-v2, on page 1436 Sends RIP Version 2 output packets to a broadcast address.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1451
RIP Commands
maximum-paths (RIP)
maximum-paths (RIP)
To configure the maximum number of equal cost parallel routes that the Routing Information Protocol (RIP)
will install into the routing table, use the maximum-paths command in the appropriate configuration mode.
To remove the maximum-paths command from the configuration file and restore the system to its default
condition with respect to RIP, use the no form of this command.
maximum-paths maximum
no maximum-paths
Syntax Description maximum Maximum number of parallel routes that RIP can install in a routing table. Range is 1 to 32..
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read,
write
Examples The following example shows how to allow a maximum of 16 equal cost paths to a destination:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1452
RIP Commands
metric-zero-accept
metric-zero-accept
To allow RIP to accept routing entries from RIP updates with a metric set to zero (0), use the
metric-zero-accept command in interface configuration mode. To remove the metric-zero-accept command
from the configuration file and restore the system to its default condition with respect to RIP, use the no
form of this command.
metric-zero-accept
no metric-zero-accept
Command Default RIP routes received with a metric of zero (0) are ignored.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
After the metric-zero-accept command is configured on routing entries from RIP updates, RIP accepts these
routes and then sets the metric to one (1).
rip read,
write
Examples The following example shows how to set the RIP interface to accept metric zero on routing entries:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1453
RIP Commands
neighbor (RIP)
neighbor (RIP)
To define a neighboring router with which to exchange Routing Information Protocol (RIP) information, use
the neighbor command in the appropriate configuration mode. To remove an entry, use the no form of
this command.
neighbor ip-address
no neighbor ip-address
Syntax Description ip-address IP address of a peer router with which routing information is exchanged.
VRF configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the neighbor command to permit the point-to-point (nonbroadcast) exchange of routing information.
When the neighbor command is used in combination with the passive-interface command in router
configuration mode, routing information can be exchanged between a subset of routers and access servers on
a LAN.
Multiple neighbor commands can be used to specify additional neighbors or peers.
rip read,
write
Examples The following example shows how to permit the sending of RIP updates to specific neighbors. One
copy of the update is generated per neighbor:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1454
RIP Commands
neighbor (RIP)
passive-interface (RIP), on page 1458 Suppresses the sending of RIP updates on an interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1455
RIP Commands
nsf (RIP)
nsf (RIP)
To configure nonstop forwarding (NSF) on Routing Information Protocol (RIP) routes after a RIP process
shutdown or restart, use the nsf command in the appropriate configuration mode. To remove this command
from the configuration file and restore the system to its default condition, use the no form of this command.
nsf
no nsf
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When you use the nsf command, NSF lifetime is automatically set to two times the update time (with a
minimum value of 60 seconds). The RIP process must reconverge within this time. If the convergence exceeds
the NSF lifetime, routes are purged from the Routing Information Base (RIB) and NSF may fail.
rip read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1456
RIP Commands
output-delay
output-delay
To change the interpacket delay for Routing Information Protocol (RIP) updates sent, use the output-delay
command in the appropriate configuration mode. To remove the delay, use the no form of this command.
output-delay delay
no output-delay delay
Syntax Description delay Delay (in milliseconds) between consecutive packets in a multiple-packet RIP update. The range is
from 8 to 50.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the output-delay command if you are sending at high speed to a low-speed router that might not be
able to receive at the high speed. Configuring this command helps prevent the routing table from losing
information.
rip read,
write
Examples The following example shows how to set the interpacket delay to 10 milliseconds:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1457
RIP Commands
passive-interface (RIP)
passive-interface (RIP)
To suppress the sending of Routing Information Protocol (RIP) updates on an interface, use the
passive-interface command in interface configuration mode. To unsuppress updates, use the no form of
this command.
passive-interface
no passive-interface
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
While RIP stops sending routing updates to the multicast (or broadcast) address on a passive interface, RIP
continues to receive and process routing updates from its neighbors on that interface.
rip read,
write
Examples The following example shows that GigabitEthernet interface 0/1/0/0 stops multicasting (or
broadcasting) RIP updates while continuing to receive RIP updates normally. GigabitEthernet interface
0/1/0/3 sends and receives updates normally. Also RIP updates are unicast to neighbor 172.168.1.2
over the appropriate interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1458
RIP Commands
passive-interface (RIP)
neighbor (RIP), on page 1454 Defines a neighboring router with which to exchange RIP protocol information.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1459
RIP Commands
poison-reverse
poison-reverse
To enable poison reverse processing of Routing Information Protocol (RIP) router updates, use the
poison-reverse command in interface configuration mode. To disable poison reverse processing of RIP
updates, use the no form of this command.
poison-reverse
no poison-reverse
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Route poisoning prevents routing loops by communicating to other routers that a route is no longer reachable,
effectively removing these routes from other router's routing tables. The system default, split horizon ,
provides that routes learned through RIP are not advertised from the interface over which they were learned.
The poison-reverse command enables poison reverse processing of RIP router updates. A router that receives
route poisoning information sends the poisoning information back to the sending router, a process called
poison reverse. This process ensures that all routers on the same interface have received the poisoned route
information.
If both poison- reverse and split horizon are configured, then simple split horizon behavior (suppression of
routes from the interface over which they were learned) is replaced by poison reverse behavior. If split horizon
is disabled, the poison reverse configuration is ignored.
rip read,
write
Examples The following example shows how to enable poison reverse processing for an interface running RIP:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1460
RIP Commands
poison-reverse
split-horizon disable (RIP), on page 1488 Disables the split horizon mechanism.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1461
RIP Commands
receive version
receive version
To configure the Routing Information Protocol (RIP) interface to accept version-specific packets, use the
receive version command in interface configuration mode. To revert to the default setting, use the no form
of this command.
receive version {1 | 2 | 1 2}
no receive version {1 | 2 | 1 2}
2 Version 2 packets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the receive version command to override the default behavior of RIP. This command applies only to
the interface being configured.
rip read,
write
Examples The following example shows how to configure an interface to accept both RIP Version 1 and 2
packets:
send version, on page 1470 Configures the RIP interface to send version specific packets.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1462
RIP Commands
redistribute (RIP)
redistribute (RIP)
To redistribute routes from another routing domain into Routing Information Protocol (RIP), use the
redistribute command in the appropriate configuration mode. To remove the redistribute command from
the configuration file and restore the system to its default condition in which the software does not redistribute
routes, use the no form of this command.
IP Static Routes
redistribute static [route-policy name]
no redistribute static
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1463
RIP Commands
redistribute (RIP)
• For the eigrp keyword, an EIGRP instance name from which routes are to
be redistributed. The value takes the form of a string. A decimal number can
be entered, but it is stored internally as a string.
• For the isis keyword, an IS-IS instance name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be
entered, but it is stored internally as a string.
• For the ospf keyword, an OSPF instance name from which routes are to be
redistributed. The value takes the form of a string. A decimal number can be
entered, but it is stored internally as a string.
route-policy name (Optional) Specifies the identifier of a configured policy. A policy is used to filter
the importation of routes from this source routing protocol to RIP.
level-1 (Optional) Redistributes Level 1 IS-IS routes into other routing protocols
independently.
level-1-2 (Optional) Distributes both Level 1 and Level 2 IS-IS routes into other routing
protocols.
level-2 (Optional) Distributes Level 2 IS-IS routes into other routing protocols
independently.
[ match { external [ (Optional) Specifies the criteria by which OSPF routes are redistributed into other
1 | 2 ] | internal | routing domains. It can be one or more of the following:
nssa-external [ 1 | 2
• internal —Routes that are internal to a specific autonomous system (intra-
]]} [ route-policy
and inter-area OSPF routes).
name ]
• external [ 1 | 2 ]—Routes that are external to the autonomous system, but
are imported into OSPF as Type 1 or Type 2 external routes.
• nssa-external [ 1 | 2 ]—Routes that are external to the autonomous system,
but are imported into OSPF as Type 1 or Type 2 not-so-stubby area (NSSA)
external routes.
For the external and nssa-external options, if a type is not specified, then both Type
1 and Type 2 are assumed.
If no match is specified, the default is no filtering.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1464
RIP Commands
redistribute (RIP)
VRF configuration
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Note When you are redistributing routes (into RIP) using both command keywords for setting or matching of
attributes and a route policy, the routes are run through the route policy first, followed by the keyword matching
and setting.
Redistributed routing information may be filtered by the route-policy name keyword and argument. This
filtering ensures that only those routes intended by the administrator are redistributed by RIP.
The RIP metric used for redistributed routes is determined by the route policy. If a route policy is not configured
or the route policy does not set the RIP metric, the metric is determined based on the redistributed protocol.
For VPNv4 routes redistributed by BGP, the RIP metric set at the remote PE router is used, if valid.
In all other cases (BGP, IS-IS, OSPF, EIGRP, connected, static), the metric set by the default-metric
command is used. If a valid metric cannot be determined, then redistribution does not happen.
For information about routing policies, see the Routing Policy Commands on Cisco ASR 9000 Series Router
module of the Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference.
rip read,
write
Examples The following example shows how to cause BGP routes to be redistributed into a RIP process:
default-metric (RIP), on page 1446 Sets default metric values for routes redistributed from other protocols
into RIP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1465
RIP Commands
router rip
router rip
To configure a routing process and enter router configuration mode for a Routing Information Protocol (RIP)
process, use the router rip command in global configuration mode. To turn off the RIP routing process,
use the no form of this command.
router rip
no router rip
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read,
write
Examples The following example shows how to configure a router process for RIP:
The following example shows how to enter router configuration mode for RIP and identify commands
that can be issued from that mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1466
RIP Commands
router rip
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1467
RIP Commands
route-policy (RIP)
route-policy (RIP)
To apply a routing policy to updates advertised to or received from a Routing Information Protocol (RIP)
neighbor, use the route-policy command in the appropriate configuration mode. To disable applying routing
policy to updates, use the no form of this command.
VRF configuration
Interface configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-policy command to specify a routing policy for an inbound or outbound route. The policy can
be used to filter routes or modify route attributes.
Note If a route policy is configured both on the interface and on the VRF, the interface route policy is applied.
rip read,
write
Examples The following example shows how to filter routing updates received on an interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1468
RIP Commands
route-policy (RIP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1469
RIP Commands
send version
send version
To configure the Routing Information Protocol (RIP) interface to send version specific packets, use the send
version command in interface configuration mode. To revert to the default setting, use the no form of this
command.
send version {1 | 2 | 1 2}
no send version {1 | 2 | 1 2}
2 Version 2 packets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the send version command to override the default behavior of RIP. This command applies only to the
interface being configured.
rip read,
write
Examples The following example shows how to configure an interface to send only RIP Version 2 packets:
receive version, on page 1462 Configures the RIP interface to accept version-specific packets.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1470
RIP Commands
show protocols (RIP)
show protocols [{ipv4 | afi-all}] [{allprotocol}] [{default-context | [vrf {vrf-name | all}]}] [private]
default-context (Optional) Displays default context information. This keyword is available when the
eigrp or rip protocol is specified.
vrf vrf-name (Optional) Displays VPN routing and forwarding (VRF) information for the specified
process. This keyword is available when the eigrp or rip protocol is specified.
private (Optional) Displays private EIGRP data. This keyword is available when the eigrp
protocol is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show protocols command to get information about the protocols running on the router and to quickly
determine which protocols are active. The command summarizes the important characteristics of the running
protocol, and command output varies depending on the specific protocol selected.
For RIP, the command output lists the instance number, default AS context, router ID, default networks,
distance, maximum paths, and so on.
RIP read
Examples The following is sample output from the show protocols rip command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1471
RIP Commands
show protocols (RIP)
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1472
RIP Commands
show rip
show rip
To display configuration and status of Routing Information Protocol (RIP), use the show rip command in
EXEC mode.
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read
Examples The following example shows sample output from the show rip command:
RIP config:
Active?: Yes
Added to socket?: Yes
Out-of-memory state: Normal
Version: 2
Default metric: Not set
Maximum paths: 4
Auto summarize?: No
Broadcast for V2?: No
Packet source validation?: Yes
NSF: Disabled
Timers: Update: 30 seconds (25 seconds until next update)
Invalid: 180 seconds
Holddown: 180 seconds
Flush: 240 seconds
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1473
RIP Commands
show rip
Field Description
Added to socket? Multicast group setting on RIP configured interfaces. If yes, updates are received
on these interfaces.
Out-of-memory state Out-of-memory state for RIP can be one of the following: Normal, Minor, Severe,
or Critical.
Packet source validation? Validation setting for the source IP address of incoming routing updates to RIP.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1474
RIP Commands
show rip database
show rip [vrf {vrf-name | all}] database [{prefix prefix-length | prefix mask}]
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
prefix (Optional) Network IP address about which routing information should be displayed.
prefix-length (Optional) The prefix-length argument specifies the length of the IP prefix. A decimal
value that indicates how many of the high-order contiguous bits of the address compose
the prefix (the network portion of the address). A slash between must precede the decimal
value. Range is 0 to 32 for IPv4 addresses.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Summary address entries appear in the database only if relevant child routes are summarized. When the last
child route for a summary address becomes invalid, the summary address is also removed from the routing
table.
rip read
Examples The following is sample output from the show rip database command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1475
RIP Commands
show rip database
Field Description
50.50.1.0/24 (inactive) The destination route 50.50.1.0/24 is not active in the routing
table.
[1] via 10.0.0.20, next hop 10.0.0.20, Uptime:
1s, GigabitEthernet0/6/0/0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1476
RIP Commands
show rip interface
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
interface (Optional) Specifies the interface from which to clear topology entries.
type Interface type. For more information, use the question mark ( ? ) online help function.
For more information about the syntax for the router, use the question mark ( ? ) online
help function.
Release The command output was modified to include authentication keychain configuration
4.0.0 information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read
Examples This example is sample output from the show rip interface command:
GigabitEthernet0_6_0_0
Rip enabled?: Yes
Out-of-memory state: Normal
Broadcast for V2: No
Accept Metric 0?: No
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1477
RIP Commands
show rip interface
Send versions: 2
Receive versions: 2
Interface state: Up
IP address: 10.0.0.12/24
Metric Cost: 0
Split horizon: Enabled
Poison Reverse: Disabled
Joined multicast group?: Yes
GigabitEthernet0_6_0_2
Out-of-memory state: Normal
Rip enabled?: Yes
Broadcast for V2: No
Accept Metric 0?: No
Send versions: 2
Receive versions: 2
Interface state: Up
IP address: 12.0.0.12/24
Metric Cost: 0
Split horizon: Enabled
Poison Reverse: Disabled
Joined multicast group?: Yes
Field Description
Rip enabled? Specifies whether the RIP routing protocol is enabled on the interface.
Broadcast for V2 Specifies whether RIP Version 2 output packets are sent to a broadcast
address on the interface.
Accept Metric 0? Specifies whether this interface accepts routing entries from RIP updates
with a metric set to zero (0).
Send versions: Specifies which version RIP uses to send out packets on this interface.
Receive versions: Specifies which version packets RIP accepts on this interface.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1478
RIP Commands
show rip interface
Field Description
Joined multicast group?: Specifies whether the interface has joined the RIP multicast group
224.0.0.9.
RIP peers attached to this interface List of RIP neighbors on this interface.
12.0.0.13
version: 2 Specifies which version packets are received from this neighbor.
packets discarded: 0 Specifies the number of packets discarded from this neighbor.
routes discarded: 402 Specifies the number of routes discarded from this neighbor.
When the keychain configured on the RIP interface does not exists or does not have any active keys:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1479
RIP Commands
show rip interface
Receive versions: 2
Interface state: Unknown State
IP address: 0.0.0.0/0
Metric Cost: 0
Split horizon: Enabled
Poison Reverse: Disabled
Socket set options:
Joined multicast group?: No
LPTS filter set?: No
When an active key exists in the keychain configured on the RIP interface, but not configured with MD5
cryptographic algorithm:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1480
RIP Commands
show rip interface
When the keychain configured on the RIP interface does not exist or does not have any active keys:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1481
RIP Commands
show rip interface
When an active key exists in the keychain configured on the RIP interface, but not configured with MD5
cryptographic algorithm:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1482
RIP Commands
show rip interface
Packets dropped due to wrong keychain config Number of packets dropped due to wrong keychain
configuration.
Packets received without authentication data Number packets received without authentication data .
Packets received with invalid authentication Number of packets received with invalid authentication.
No active key found in keychain database No active keys are available in IOS XR keychain
database.
Key(s) not configured with MD5 cryptographic Keys are not configured with MD5 cryptographic
algorithm algorithm.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1483
RIP Commands
show rip statistics
Syntax Description vrf { vrf | all } (Optional) Specifies a particular VPN routing and forwarding (VRF) instance or all VRF
instances.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
rip read
Examples The following example is sample output from the show rip statistics command:
RIP statistics:
Total messages sent: 5597
Message send failures: 0
Regular updates sent: 5566
Queries responsed to: 0
RIB updates: 6
Total packets received: 5743
Discarded packets: 0
Discarded routes: 0
Number of routes allocated: 18
Number of paths allocated: 14
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1484
RIP Commands
show rip statistics
Field Description
Message send failures Number of times that the packet send operation failed.
Queries responsed to Number of times RIP updates are sent in response to a RIP query.
RIB updates Number of route addition and deletion messages sent to RIB.
Discarded routes Number of routes (in received RIP update packets) that are discarded.
Number of routes allocated Number of routes allocated for the RIP internal topology database.
Number of paths allocated Number of paths allocated for the RIP internal topology database.
Note The number of routes found in the allocated field might ot be the same number of routes present in
the RIP database.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1485
RIP Commands
site-of-origin (RIP)
site-of-origin (RIP)
To configure the Site of Origin (SoO) filtering on a Routing Information Protocol (RIP) interface, use the
site-of-origin command in interface configuration mode. To disable SoO filtering on an interface, use the
no form of this command.
number Network number. Range is from 0 to 4294967295 when a 2-byte AS number is used. Range
is from 0 to 65535 when a 4-byte AS number is used.
ip-address The IP address argument specifies the IP address in four-part, dotted-decimal notation.
A colon is used to separate the IP address and network number.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
A RIP process must be capable of retrieving the SoO attribute on routes redistributed from the Border Gateway
Protocol (BGP) when required to support complex topologies that include MPLS VPN links between sites
with backdoor links.
Use the site-of-origin command to set an SoO BGP extended community attribute that is used to identify
routes that have originated from a site so that the readvertisement of that prefix back to the source site can be
prevented. The SoO extended community uniquely identifies the site from which a provider edge (PE) router
has learned a route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1486
RIP Commands
site-of-origin (RIP)
rip read,
write
Examples The following example shows how to configure SoO filtering on a RIP interface:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1487
RIP Commands
split-horizon disable (RIP)
split-horizon disable
no split-horizon disable
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You can explicitly specify the split-horizon disable command in your configuration.
If split horizon is disabled, the poison reverse configuration is ignored.
Note In general, we recommend that you do not change the default state of split horizon unless you are certain that
your application requires the change to properly advertise routes.
rip read,
write
Examples The following example shows how to disable split horizon on a Packet-over-SONET/SDH link:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1488
RIP Commands
split-horizon disable (RIP)
poison-reverse, on page 1460 Enables poison reverse processing of RIP router updates.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1489
RIP Commands
timers basic
timers basic
To adjust Routing Information Protocol (RIP) network timers, use the timers basic command in router
configuration mode. To restore the timers default values, use the no form of this command.
Syntax Description update Rate, in seconds, at which updates are sent. This is the fundamental timing parameter of the routing
protocol. Range is 5 to 50000.
invalid Interval, in seconds, after which a route is declared invalid; it should be at least three times the
value of the update argument. A route becomes invalid when there is an absence of updates that
refresh the route. The route then enters into a holddown state. The route is marked inaccessible
and is advertised as unreachable. Range is 15 to 200000.
holddown Interval, in seconds, during which routing information regarding better paths is suppressed. It
should be at least three times the value of the update argument. A route enters into a holddown
state when an update packet is received that indicates that the route is unreachable. The route is
marked inaccessible and is advertised as unreachable. When holddown expires, routes advertised
by other sources are accepted, and the route is no longer inaccessible. Range is 15 to 200000.
flush Amount of time, in seconds, that must pass before the route is removed from the routing table;
the interval specified should be greater than the value of the invalid argument. If it is less than
the invalid timer value, the proper holddown interval cannot elapse, which results in a new route
being accepted before the holddown interval expires. Range is 16 to 250000.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The basic timing parameters for RIP are adjustable. Because RIP is running a distributed, asynchronous routing
algorithm, these timers must be the same for all routers in the network.
Note Use the show rip command to display the current and default timer values.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1490
RIP Commands
timers basic
rip read,
write
Examples The following example shows how to set updates to be broadcast every 5 seconds. If a router is not
heard from in 15 seconds, the route is declared unusable. Further information is suppressed for an
additional 15 seconds. At the end of the flush period, the route is flushed from the routing table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1491
RIP Commands
validate-update-source disable
validate-update-source disable
To stop the Cisco IOS XR software from validating the source IP address of incoming routing updates for
Routing Information Protocol (RIP), use the validate-update-source disable command in router configuration
mode. To reenable this function, use the no form of this command.
validate-update-source disable
no validate-update-source disable
Command Default The source IP address of incoming updates for RIP is always validated.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When the validate-update-source disable command is used, validation is not performed.
By default, the software ensures that the source IP address of incoming routing updates is on the same IP
network as one of the addresses defined for the receiving interface.
For unnumbered IP interfaces (interfaces configured as IP unnumbered), no checking is performed.
rip read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1492
RIP Commands
vrf (RIP)
vrf (RIP)
To define a VPN routing and forwarding (VRF) instance and to enter VRF configuration mode, use the vrf
command in router configuration mode. To remove a VRF instance use the no form of this command.
vrf vrf-name
no vrf vrf-name
Syntax Description vrf-name Specifies a particular VPN routing and forwarding instance.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vrf command to configure a VRF instance. A VRF instance is a collection of VPN routing and
forwarding tables maintained at the provider edge (PE) router.
From VRF configuration mode, you can issue all commands available in router configuration mode such as
the auto-summary command.
rip read,
write
Examples The following example shows how to enter VRF configuration mode and identify RIP commands
that can be issued from that mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1493
RIP Commands
vrf (RIP)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1494
Routing Policy Language Commands
This module describes the Cisco IOS XR software routing policy language (RPL) commands used to create,
modify, monitor, and maintain routing policies.
For detailed information about RPL concepts, configuration tasks, and examples, see the Implementing Routing
Policy on Cisco ASR 9000 Series Router module in the Routing Configuration Guide for Cisco ASR 9000
Series Routers .
• abort (RPL), on page 1499
• add, on page 1501
• apply, on page 1503
• as-path in, on page 1505
• as-path is-local, on page 1507
• as-path length, on page 1508
• as-path neighbor-is, on page 1510
• as-path originates-from, on page 1513
• as-path passes-through, on page 1515
• as-path-set, on page 1517
• as-path unique-length, on page 1519
• community is-empty, on page 1521
• community matches-any, on page 1522
• community matches-every, on page 1524
• community-set, on page 1526
• delete community, on page 1529
• delete extcommunity rt, on page 1531
• destination in, on page 1533
• done, on page 1535
• drop, on page 1537
• edit, on page 1539
• end-global, on page 1542
• end-policy, on page 1543
• end-set, on page 1544
• extcommunity rt is-empty, on page 1546
• extcommunity rt matches-any, on page 1547
• extcommunity rt matches-every, on page 1549
• extcommunity rt matches-within, on page 1551
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1495
Routing Policy Language Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1496
Routing Policy Language Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1497
Routing Policy Language Commands
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1498
Routing Policy Language Commands
abort (RPL)
abort (RPL)
To discard a route policy or set definition and return to global configuration mode, use the abort command
in the appropriate configuration mode.
abort
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
route-policy read,
write
Examples The following example shows how to discard a route policy definition that was started and return to
global configuration mode:
The following example shows how to discard a prefix set definition that was started and return to
global configuration mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1499
Routing Policy Language Commands
abort (RPL)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1500
Routing Policy Language Commands
add
add
To add a value to an Routing Information Protocol (RIP) or Enhanced Interior Gateway Protocol (EIGRP)
existing metric, use the add command in route-policy configuration mode.
loading Effective bandwidth (loading). 255 is 100-percent loaded. Range is from 0 to 255.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If the add value is greater than the maximum allowed value, the metric is added. If the resulting metric exceeds
the maximum for the routing protocol, then the route is dropped (by the client routing protocol).
route-policy read,
write
Examples The following example shows how to offset the RIP metric value:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1501
Routing Policy Language Commands
add
The following example shows how to set the EIGRP metric value:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1502
Routing Policy Language Commands
apply
apply
To execute a parameterized or unparameterized policy from within another policy, use the apply command
in route-policy configuration mode.
argument (Optional) Parameter name. The argument can be a value (for example, '100' ) or a parameter
(for example, '$parameter')
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the apply command to execute a policy (either parameterized or unparameterized) from within another
policy, which allows for the reuse of common blocks of policy.
Wildcards can be used in apply policy names. This supports the nested wildcard apply scenario. A wildcard
is specified by inserting an asterisk (*) in place of one of the portions of the apply policy name; the wildcard
indicates that any value for that portion of the apply policy name matches. The nested wildcard apply policy
allows wildcard (*) based apply nesting. The wildcard operation permits declaration of a generic apply
statement that calls all policies that contain a specific defined set of alphanumeric characters, defined on the
router.
route-policy read,
write
Examples In the following example, the policy CustomerIn applies the route-policy SetLocalPref to conditionally
set the local preference on a route. The parameters 20, 30, 40, and 50 are passed to the parameterized
policy SetLocalPref, where the local preference is set to:
• 20, if the community 217:20 is present in the route
• 30, if the community 217:30 is present in the route
• 40, if the community 217:40 is present in the route
• 50, if the community 217:50 is present in the route
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1503
Routing Policy Language Commands
apply
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1504
Routing Policy Language Commands
as-path in
as-path in
To match the AS path of a route to an AS path set, use the as-path in command in route-policy configuration
mode.
as-path in {as-path-set-nameinline-as-path-setparameter}
inline-as-path-set Inline AS path set. The inline AS path set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path in command as a conditional expression within an if statement to match the AS path of a
route to an AS path set. The AS path is a sequence of autonomous system numbers traversed by a route.
Note For a list of all conditional expressions available within an if statement, see the if command.
The as-path in command evaluates to true if at least one of the regular expressions defined in the associated
AS path set matches the AS path attribute of the route.
In the case where the AS path set is defined but contains no elements in it, the as-path in conditional
expression command returns false.
route-policy read,
write
Examples For example, assume we have an AS path set named my-as-set defined as follows:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1505
Routing Policy Language Commands
as-path in
RP/0/RSP0/CPU0:router(config-as)# end-set
The AS path in condition evaluates to true if one or more of the regular expression matches in the
set my-as-set match the AS path associated with the route. In the case of a defined but empty AS
path set, this operator returns false.
The preceding policy excerpt is equivalent to the following version, which uses an inline-as-path
set variable:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1506
Routing Policy Language Commands
as-path is-local
as-path is-local
To determine if this router or another router within this autonomous system or confederation originated a
Border Gateway Protocol (BGP) route, use the as-path is-local command in route-policy configuration
mode.
as-path is-local
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path is-local command as a conditional expression within an if statement to determine if this
router (or another router within this autonomous system or confederation) originated the route.
Note For a list of all conditional expressions available within an if statement, see the if command.
Routes that are locally originated within the autonomous system or confederation carry an empty AS path.
For the Border Gateway Protocol (BGP) specification, when a route is advertised across the autonomous
system boundary or a confederation boundary, the local autonomous system number or confederation ID is
appended to the autonomous system path. The AS path of a locally originated aggregate is also empty unless
it has been modified by policy.
The is-local operator evaluates to true for autonomous system paths that are empty. An empty AS path is
how an AS path that is local to our autonomous system is represented in BGP.
route-policy read,
write
Examples In the following example, if the AS path is local, then the local preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1507
Routing Policy Language Commands
as-path length
as-path length
To compare the number of ASN in the AS path of a Border Gateway Protocol (BGP) route, use the as-path
length command in route-policy configuration mode.
Syntax Description eq | is | ge | le Equal to; greater than or equal to; less than or equal to.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path length command as a conditional expression within an if statement to perform a conditional
check based on the length of the AS path.
Note For a list of all conditional expressions available within an if statement, see the if command.
This command takes either a specific integer value or a range of integer values specified with the ge and le
operators. Any or all these integers can be parameterized. The operator counts one for each autonomous system
in the path. In the case where the route may be aggregated and contain one or more AS sets, the length operator
adds one for each set present, the occurrence of an AS set typically indicates that this route is an aggregated
route, and the aggregated route had a component route that contained one of the autonomous systems in the
set. Likewise, in the case of confederations, a count of one is added for each confederation in the path or each
confederation set in the path. A null AS path has a length of zero.
route-policy read,
write
Examples In the following example, if the AS path length equals 10, then the local preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1508
Routing Policy Language Commands
as-path length
as-path in, on page 1505 Matches the AS path of a route to an AS path set.
as-path originates-from, on page 1513 Compares an AS path against the AS sequence beginning with the
AS number that originated a route
as-path passes-through, on page 1515 Verifies if the supplied integer or parameter appears anywhere in
the AS path or if the supplied sequence of integers and parameters
appears, in the same order, anywhere in the AS path.
as-path unique-length, on page 1519 Performs specific checks based on the length of the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1509
Routing Policy Language Commands
as-path neighbor-is
as-path neighbor-is
To test autonomous system numbers at the head of the AS path against a sequence of one or more values or
parameters, use the as-path neighbor-is command in route-policy configuration mode.
Syntax Description as-number-list Numbers or parameters, enclosed in single quotation marks, that represent a sequence of
autonomous system numbers.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
exact (Optional) Specifies that with the exact keyword, the as-number-list value must identically
match the AS path for the route; without the exact keyword, any element in the
as-number-list argument matches one or more occurrences of that element in the AS path
for the route.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path neighbor-is command as a conditional expression within an if statement to test the
autonomous system number or numbers at the head of the AS path against a sequence of one or more integral
values or parameters. In other words, to test to learn if the sequence of autonomous system numbers matches
the path beginning with the neighboring autonomous system from which this route was heard.
Note For a list of all conditional expressions available within an if statement, see the if command.
This command has an equivalent regular expression (ios-regex). For example, AS path neighbor-is ‘1’ would
be ‘^1_’.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1510
Routing Policy Language Commands
as-path neighbor-is
route-policy read,
write
These statements evaluate to true when the first autonomous system numbers on the AS path match,
in the same order, the supplied parameters or integer values in the neighbor-is statement. If the
neighboring autonomous system location happens to be an AS-set, the operator evaluates to true if
the corresponding argument to the neighbor-is operator is an element of the AS-set.
Without the exact keyword, repeated autonomous system numbers in the AS path are ignored. For
example,
10 10 10 20 ...
10 20 ....
as-path in, on page 1505 Matches the AS path of a route to an AS path set.
as-path length, on page 1508 Compares the number of ASN in the AS path of a route.
as-path originates-from, on page 1513 Compares an AS path to the AS sequence beginning with the AS
number that originated a route.
as-path passes-through, on page 1515 Verifies if the supplied integer or parameter appears anywhere in
the AS path or if the supplied sequence of integers and parameters
appears, in the same order, anywhere in the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1511
Routing Policy Language Commands
as-path neighbor-is
Command Description
as-path unique-length, on page 1519 Performs specific checks based on the length of the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1512
Routing Policy Language Commands
as-path originates-from
as-path originates-from
To compare an AS path against the AS sequence beginning with the AS number that originated a route, use
the as-path originates-from command in route-policy configuration mode.
Syntax Description as-number-list Numbers or parameters, enclosed in single quotation marks, that represent a sequence of
autonomous system numbers.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
exact (Optional) Specifies that with the exact keyword, the as-number-list value must identically
match the AS path for the route; without the exact keyword, any element in the
as-number-list argument matches one or more occurrences of that element in the AS path
for the route.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path originates-from command as a conditional expression within an if statement to compare
an AS path to the autonomous system sequence.
Note For a list of all conditional expressions available within an if statement, see the if command.
The originates-from operator is similar to the neighbor-is operator, except that it looks at the autonomous
system number at the opposite end of the AS path. In other words, it is comparing to the autonomous system
that originated the route. It can take numbers or parameters, enclosed in single quotation marks, that represent
a sequence of autonomous system numbers. When more than one number is specified in the list, the sequence
of autonomous system numbers listed must appear as a subsequence in the AS path, with the last number
corresponding to the autonomous system that originated the route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1513
Routing Policy Language Commands
as-path originates-from
route-policy read,
write
The first line of the preceding example evaluates to true if autonomous system 11 originated the
route and then advertised it to autonomous system 10, from which the route was eventually propagated
to us. In the case where the route has been aggregated, and the location of the originating autonomous
system contains an AS-set, the originates-from operator evaluates to true if the argument to the
originates-from operator is contained in the AS-set.
Without the exact keyword, repeated autonomous system numbers in the AS path are ignored. For
example,
...10 10 10 11
...10 11
matches the second of these autonomous system paths but not the first.
as-path in, on page 1505 Matches the AS path of a route to an AS path set.
as-path length, on page 1508 Compares the number of ASN in the AS path of a route
as-path passes-through, on page 1515 Verifies if the supplied integer or parameter appears anywhere in the
AS path or if the supplied sequence of integers and parameters appears,
in the same order
as-path unique-length, on page 1519 Performs specific checks based on the length of the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1514
Routing Policy Language Commands
as-path passes-through
as-path passes-through
To verify if the supplied integer or parameter appears anywhere in the AS path or if the supplied sequence of
integers and parameters appears, in the same order, anywhere in the AS path, use the as-path passes-through
command in route-policy configuration mode.
Syntax Description as-number-list Numbers or parameters, enclosed in single quotation marks, that represent a sequence of
autonomous system numbers.
• Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535.
• Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to
4294967295.
• Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to
65535.65535.
exact (Optional) Specifies that with the exact keyword, the as-number-list value must identically
match the AS path for the route; without the exact keyword, any element in the
as-number-list argument matches one or more occurrences of that element in the AS path
for the route.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path passes-through command as a conditional expression within an if statement to verify if the
specified integer or parameter appears anywhere in the AS path or if the sequence of integers and parameters
appears.
Note For a list of all conditional expressions available within an if statement, see the if command.
The passes-through operator takes a sequence of integers or parameters, enclosed in single quotation marks,
as an argument. It can also take a single integer or parameter as an argument. It evaluates to true if the supplied
integer or parameter appears anywhere in the AS path, or if the supplied sequence of integers and parameters
appears, in the same order, anywhere in the AS path. This includes the originates-from or neighbor-is
location in the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1515
Routing Policy Language Commands
as-path passes-through
route-policy read,
write
Without the exact keyword, repeated autonomous system numbers in the AS path are ignored. For
example:
...9 10 10 10 11 ....
...9 10 11...
as-path in, on page 1505 Matches the AS path of a route to an AS path set.
as-path length, on page 1508 Compares the number of ASN in the AS path of a route
as-path originates-from, on page 1513 Compares an AS path to the AS sequence beginning with the AS
number that originated a route.
as-path unique-length, on page 1519 Performs specific checks based on the length of the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1516
Routing Policy Language Commands
as-path-set
as-path-set
To create a named AS path set, use the as-path-set command in global configuration mode. To remove the
named AS path set, use the no form of this command.
as-path-set name
no as-path-set name
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path-set command to create a named AS path set.
An AS path set comprises operations for matching an AS path attribute.
This command enters AS path set configuration mode, in which you can use any of the below option to specify
an operation.
Options Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1517
Routing Policy Language Commands
as-path-set
Options Description
The above options can also be used as an inline set in a parenthesized list of comma-separated expressions.
route-policy read,
write
Examples The following is a sample definition of an AS path set named aset1. This AS path set is composed
of two elements. When used in a matching operation, this AS path set matches any route whose AS
path ends with either the autonomous system number 42 or 127.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1518
Routing Policy Language Commands
as-path unique-length
as-path unique-length
To perform specific checks based on the length of the AS path (match against the number of unique ASNs in
the AS path), use the as-path unique-length command in route-policy configuration mode.
Syntax Description eq | is | ge | le Equal to; greater than or equal to; less than or equal to.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the as-path unique-length command as a conditional expression within an if statement to perform a
match based on the length of the AS path.
Note For a list of all conditional expressions available within an if statement, see the if command.
The unique-length operator is similar to the length operator, except that when an AS path has been padded
with the same autonomous system number multiple times, the operator counts only one when the route is
padded. Therefore, given an AS path of 333 333 111 222 123 444 444 444, the unique-length operator
would return a value of 5, whereas the length operator would return a value of 8.
route-policy read,
write
Examples The following example shows show to perform checks based on the AS path length. If the AS path
matches the specified values, the local preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1519
Routing Policy Language Commands
as-path unique-length
as-path length, on page 1508 Performs conditional checks based on the length of the AS path.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1520
Routing Policy Language Commands
community is-empty
community is-empty
To check if a route has no community attributes associated with it, use the community is-empty command
in route-policy configuration mode.
community is-empty
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the community is-empty command as a conditional expression within an if statement to check if a
route has community attributes associated with it.
Note For a list of all conditional expressions available within an if statement, see the if command.
This command takes no arguments and evaluates to true only if the route has no community attributes associated
with it.
route-policy read,
write
Examples In the following example, if the route has no community attributes associated with it, then the local
preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1521
Routing Policy Language Commands
community matches-any
community matches-any
To match any elements of a community set, use the community matches-any command in route-policy
configuration mode.
inline-community-set Inline community set. The inline community set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the community matches-any command as a conditional expression within an if statement to match
any element of a community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-any operator evaluates as true if at least one community element of
the community attribute for the route matches an element in the community set operand. If no community in
the route matches any of the specifications in the named or inline set, then the condition evaluates to false.
Likewise, when there is no community at all in the route, the condition evaluates to false.
Matching of a community in the route to a specification in a named or an inline set is intuitive. If the community
specification in a set is the familiar colon-separated decimal 16-bit numbers specification, or one of the
well-known communities, the community matches the specification if the specification denotes the same
32-bit number as that in the route. If the community specification uses a wildcard, then the community in the
route matches if it is one of the many communities denoted by the wildcard specification. In inline sets,
community specifications may be parameterized, in which case the relevant matching is done when the value
of the parameter has been supplied.
Communities may also be matched using range and regular expression operators. Range specifications are
entered as follows: [ low-value .. high-value ]. Either or both colon-separated halves of a community value
may contain a range. The following are valid range specifications:
10:[100..1000]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1522
Routing Policy Language Commands
community matches-any
[10..100]:80
[10..100]:[100..2000]
In addition, the private-as keyword may be used to specify the range from 64512 to 65534. Regular
expressions are specified as the ios-regex keyword followed by a valid regular expression string.
Community values from the route are matched one at a time to the match specifications. Therefore, regex
match specifications are expected to represent one individual community value and not a sequence of community
values.
route-policy read,
write
Examples In the following example, a named community set called my-community-set and a route policy called
community-matches-any-example are created. The policy sets the local-preference to 100 for any
route that has one or more of the communities in the my-community-set community set. If the route
does not have any of these communities, the policy checks whether it has any communities whose
first half is in the range from 10 to 25 and whose second half is the value 35, in which case it sets
the local-preference to 200. Otherwise, it checks for a community value in the range of 30:100 to
30:500, in which case it sets the local-preference to 300.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1523
Routing Policy Language Commands
community matches-every
community matches-every
To match every element of a community set, use the community matches-every command in route-policy
configuration mode.
inline-community-set Inline community set. The inline community set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the community matches-every command as a conditional expression within an if statement to match
every element of a community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-every operator evaluates as true if every specification in the named
set or inline set specified matches at least one community value in the route. If any community specification
in the named or inline set is not matched, then the operation evaluates to false.
Matching of a community in the route to a specification in a named or an inline set is intuitive. If the
community-specification in a set is the familiar colon-separated decimal 16-bit numbers specification, or one
of the well-known communities, the community matches the specification if the specification denotes the
same 32-bit number as that in the route. If the community specification uses a wildcard, then the community
in the route matches if it is one of the many communities denoted by the wildcard specification. In inline sets,
community specifications may be parameterized, in which case the relevant matching is done when the value
of the parameter has been supplied.
Communities may also be matched using range and regular expression operators. Range specifications are
entered as follows: [ low-value .. high-value ]. Either or both colon-separated halves of a community value
may contain a range. The following are valid range specifications:
10:[100..1000]
[10..100]:80
[10..100]:[100..2000]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1524
Routing Policy Language Commands
community matches-every
Therefore, a matches-every operation with two community range specifications means that a community
must be present in the route that corresponds to each range. For example, in the following statement:
the statement evaluates as true if one or more communities in the route lie in the range 10:[100.200] and one
or more communities in the route lie in the range 20:[100..200].
In addition, the private-as keyword may be used to specify the range from 64512 to 65534.
Regular expressions are specified as the ios-regex keyword followed by a valid single-quoted regular
expression string. Community values from the route are matched one at a time against the match specifications.
Therefore, regex match specifications are expected to represent one individual community value and not a
sequence of community values.
route-policy read,
write
Examples In the following example, the route policy named community-matches-every-example sets the
local-preference value to 100 for all routes that have all three communities in the my-community-set
community set. Routes that do not have all three communities but have a community that matches
the first regular expression match have the local-preference value set to 200. Finally, any remaining
routes that match the last regular expression have the local-preference values set to 300.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1525
Routing Policy Language Commands
community-set
community-set
To define a community set, use the community-set command in global configuration mode. To remove the
community set, use the no form of this command.
community-set name
no community-set name
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Regular expressions and ranges can be specified to match the communities. An attempt to use a community
set that contains a range or regular expression to set a community value is rejected when an attempt to attach
such a policy is made.
A community set holds community values for matching against the Border Gateway Protocol (BGP) community
attribute. A community is a 32-bit quantity. For notational convenience, each community value must be split
in half and expressed as two unsigned decimal integers in the range from 0 to 65535, separated by a colon.
The inline form of a community set also supports parameterization. Each 16-bit portion of the community
may be parameterized.
The routing policy language (RPL) provides symbolic names for the standard well-known community values:
accept-own is 0xFFFF0001, internet is 0:0, no-export is 65535:65281, no-advertise is 65535:65282,
and local-as is 65535:65283.
RPL also provides a facility for using wildcards in community specifications. A wildcard is specified by
inserting an asterisk (*) in place of one of the 16-bit portions of the community specification, which indicates
that any value for that portion of the community matches.
Every community set must contain at least one community value. An empty community set is invalid and the
policy configuration system rejects it.
Community sets can be entered in these formats:
Format Description
#-remark Remark beginning with '#'
* Wildcard (any community or part thereof)
0-65535 16-bit half-community number
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1526
Routing Policy Language Commands
community-set
Format Description
[ Left bracket to begin range
accept-own Accept-Own (BGP well-known community)
dfa-regex DFA (deterministic finite automata) style regular
expression
internet Internet (BGP well-known community)
ios-regex Traditional IOS style regular expression
local-AS Do not send outside local AS (BGP well-known
community)
no-advertise Do not advertise to any peer (BGP well-known
community)
no-export Do not export to next AS (BGP well-known
community)
private-as Match within BGP private AS range [64512..65534]
Note The dfa-regex and ios-regex syntax for community set is "['][^':&<> ]*:[^':&<> ]*[']". This means that
regex starts with a single-quote (") followed by a string of any character (that does not include single-quote,
colon, ampersand, less-than, greater-than, or space) followed by a colon, and a string of any characters (that
does not include single-quote, colon, ampersand, less-than, greater-than, or space) followed by single-quote.
route-policy read,
write
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#community-set cset_accept_own
RP/0/RSP0/CPU0:router(config-comm)#accept-own
RP/0/RSP0/CPU0:router(config-comm)#end-set
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1527
Routing Policy Language Commands
community-set
In the following example, a community set named cset3 is created. This policy uses wildcards and
matches all communities where the autonomous system part of the community is 123.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1528
Routing Policy Language Commands
delete community
delete community
To delete community attributes associated with a Border Gateway Protocol (BGP) route, use the delete
community command in route-policy configuration mode.
Syntax Description all Removes all communities except the well-known communities.
in Removes any communities associated with the route that are listed in either the named
community set or the inline community set.
inline-community-set Inline community set. The inline community set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
not in Removes all communities that are not listed in either the named community set or the
inline community set, and are not well-known communities.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the delete community command to delete community attributes associated with a BGP route.
Note The delete community command can be used as an action statement within an if statement. For a list of
all action statements available within an if statement, see the if command.
Communities are 32-bit values carried in Border Gateway Protocol (BGP) routes. Each route may have zero
or more communities in an unordered list.
You can remove a well-known community (internet, no-export, no-advertise, or local-as) from a route, but
this removal must be done explicitly. This command should be used with a degree of caution. In general, few
circumstances exist in which you would need to remove a well-known community.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1529
Routing Policy Language Commands
delete community
route-policy read,
write
Examples The following example shows how to delete any communities associated with the routes that are
listed in either the named community set or inline community set, respectively.
The following example shows how to remove all communities including well-known communities.
The following example shows how to remove all communities except for the well-known communities.
The following example shows how to delete the well-known community value internet from a route:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1530
Routing Policy Language Commands
delete extcommunity rt
delete extcommunity rt
To delete route target (RT) extended community attributes associated with a Border Gateway Protocol (route),
use the delete extcommunity rt command in route-policy configuration mode.
in Removes any extended communities associated with the routes that are listed in
either the named extended community set or the inline extended community set.
inline-extcommunity-set Inline extended community set. The inline extended community set must be enclosed
in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
not in Removes all extended communities that are not listed in either the named extended
community set or the inline extended community set, and are not well-known
extended communities.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the delete extcommunity rt command to delete extended community values from a BGP route target
extended community list in a route.
Note The delete extcommunity rt command can be used as an action statement within an if statement. For a list
of all action statements available within an if statement, see the if command.
Extended communities are similar to regular Border Gateway Protocol (BGP) communities but contain more
data and have a richer structure for encoding information in them.
Extended communities can be in the following forms: SoO:AS:tag, SoO:IP:tag, RT:AS:tag, or RT:IP:tag.
Wildcards (*) and regular expressions are allowed for extended community set elements.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1531
Routing Policy Language Commands
delete extcommunity rt
The forms of this command that take a named extended community set or an inline extended community set
value as arguments are equivalent. They delete any extended communities that are listed in either the named
set or the inline set, respectively.
route-policy read,
write
In this example, any extended communities that are listed in my-extcommunity-set are deleted:
In this example, extended communities associated with the route listed in the named inline extended
community sets are deleted:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1532
Routing Policy Language Commands
destination in
destination in
To match a destination entry in a named prefix set or inline prefix set, use the destination in command in
route-policy configuration mode.
destination in {prefix-set-nameinline-prefix-setparameter}
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
parameter
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the destination in command as a conditional expression within an if statement to match a destination
entry in a named prefix set or inline prefix set.
Note For a list of all conditional expressions available within an if statement, see the if command.
This command takes either a named prefix set or an inline prefix set value as an argument. The condition
returns true if the destination entry matches any entry in the prefix set or inline prefix set. An attempt to match
a destination using a prefix set that is defined but contains no elements returns false.
The routing policy language (RPL) provides the ability to test destinations for a match to a list of prefix match
specifications using the in operator. The destination in command is protocol-independent.
In Border Gateway Protocol (BGP), the destination of a route is also known as its network-layer reachability
information (NLRI). It comprises a prefix value and a mask length.
RPL supports both 32-bit IPv4 prefixes, specified in dotted-decimal format, and 128-bit IPv6 prefixes, specified
in colon-separated hexadecimal format.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1533
Routing Policy Language Commands
destination in
Examples In the following example, a prefix set named my-prefix-set is defined and a route policy named
use-destination-in is created. Within the use-destination-in route policy, the destination in command
is used within an if statement to learn if the destination is in the prefix-set named my-prefix-set. If
it is, then local preference is set to 100. If it is not in my-prefix-set but does match the next prefix
specifications, then local preference is set to 200.
In the following example, a prefix set named ipv6-prefix-set is defined and a route policy named
ipv6-destination-in is created. Within the ipv6-destination-in route policy, the destination in
command is used within an if statement to learn if the destination is in the prefix-set named
ipv6-prefix-set. If it is, then the next-hop is set to 2001:abcd:fedc::1. If it is not in ipv6-prefix-set but
does match the next prefix specifications, then the next-hop is set to
1111:2222:3333:4444:5555:6666:7777:8888.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1534
Routing Policy Language Commands
done
done
To stop executing a policy and accept the route, use the done command in route-policy configuration mode.
done
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the done command to stop executing the policy and accept the route.
Note The done command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
When encountering a done statement the route is passed and no further policy statements are executed. All
modifications made to the route prior to the done statement are still valid.
Note The default action of a route policy is to drop or discard any routes that have not been either explicitly passed
or for which no attempt has been made to modify with an action. The routing policy language (RPL) does not
have specific “match clauses,” which means the default drop behavior is controlled by whether a route has
been explicitly passed or an attempt has been to modify the route using an action statement.
route-policy read,
write
Examples In the following example, if the destination match succeeds for 29.0.0.0/8 le 32, the execution
continues past set community 102:12 and onto the next statement. If the destination match succeeds
for 39.0.0.0/8 le 32 execution, then the policy execution stops when in encounters the done statement.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1535
Routing Policy Language Commands
done
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1536
Routing Policy Language Commands
drop
drop
To discard a route, use the drop command in route-policy configuration mode.
drop
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the drop command within a route policy to drop a route.
Note The drop command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
This command causes the route to be dropped. After a route is dropped, no further execution of policy occurs.
Therefore, if after executing the first two statements of a policy the drop statement is encountered, the route
is discarded and execution stops immediately even when the policy contains further statements.
Note The default action of a route policy is to drop or discard any routes that have not been either explicitly passed
or attempted to be modified with an action. The routing policy language (RPL) does not have specific “match
clauses,” which means the default drop behavior is controlled by whether a route has been explicitly passed
or an attempt has been to modify the route using an action statement.
route-policy read,
write
Examples In the following example, any route with a destination address contained within the prefix set pset1
is dropped:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1537
Routing Policy Language Commands
drop
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1538
Routing Policy Language Commands
edit
edit
To edit the contents of a route policy, a prefix set, an AS path set, a community set, or an extended community
set, use the edit command in EXEC configuration mode.
extcommunity-set Edits the contents of an extended community set of the specified type.
name Name of a route policy, a prefix set, an AS path set, a community set, or an extended
community set, RD set, or global parameters.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1539
Routing Policy Language Commands
edit
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the edit command to edit the contents of a route policy, a prefix set, an AS path set, a community set,
an extended community set, a global policy, or a route destination set.
After editing with Nano, save the edit buffer and exit the editor using the Ctrl-X keystroke.
After editing with Emacs, save the editor buffer by using the Ctrl-X and Ctrl-S keystrokes. To save and exit
the editor, use the Ctrl-X and Ctrl-C keystrokes.
After editing with VIM, to write to a current file and exit use the :wq or :x or ZZ keystrokes. To quit and
confirm, use the :q keystrokes. To quit and discard changes, use the :q! keystrokes.
route-policy read,
write
Examples In the following example, the policy_A policy is opened in the editor:
----------------------------------------
== MicroEMACS 3.8b () == rpl_edit.139281 ==
if destination in (2001::/8) then
drop
endif
end-policy
!
If there are parse errors, you are asked whether editing should continue:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1540
Routing Policy Language Commands
edit
Parsing.
105 bytes parsed in 1 sec (103)bytes/sec
If you answer yes , the editor continues on the text buffer from where you left off. If you answer no,
the running configuration is not changed and the editing session is ended.
After the policy is opened, it may be manipulated using normal editor commands, then saved and
committed to the running configuration.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1541
Routing Policy Language Commands
end-global
end-global
To end the definition of global parameters and exit global parameter configuration mode, use the end-global
command in global parameter configuration mode.
end-global
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the end-global command to end the definition of global parameters and exit global parameter configuration
mode.
route-policy read,
write
Examples In the following example, the end-global command ends the definition of global parameters:
RP/0/RSP0/CPU0:router(config)#policy-global
RP/0/RSP0/CPU0:router(config-rp-gl)# glbpathtype ‘ebgp’
RP/0/RSP0/CPU0:router(config-rp-gl)# glbtag ‘100’
RP/0/RSP0/CPU0:router(config-rp-gl)# end-global
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1542
Routing Policy Language Commands
end-policy
end-policy
To end the definition of a route policy and exit route-policy configuration mode, use the end-policy command
in route-policy configuration mode.
end-policy
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the end-policy command to end the definition of a route policy and exit route-policy configuration
mode.
route-policy read,
write
Examples In the following example, the end-policy command ends the definition of a route policy:
RP/0/RSP0/CPU0:router(config)#route-policy med-to-local-pref
RP/0/RSP0/CPU0:router(config-rpl)#if med eq 150 then
RP/0/RSP0/CPU0:router(config-rpl-if)# set local-preference 10
RP/0/RSP0/CPU0:router(config-rpl-if)# elseif med eq 200 then
RP/0/RSP0/CPU0:router(config-elseif)# set local-preference 60
RP/0/RSP0/CPU0:router(config-elseif)# elseif med eq 250 then
RP/0/RSP0/CPU0:router(config-elseif)# set local-preference 0
RP/0/RSP0/CPU0:router(config-elseif)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
route-policy (RPL), on page 1609 Defines a route policy and enters route-policy configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1543
Routing Policy Language Commands
end-set
end-set
To end the definition of an AS path set, a prefix set, a community set, an extended community set, or an RD
set and return to global configuration mode, use the end-set command in route-policy configuration mode.
end-set
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the end-set command to end the definition of an AS path set, a prefix set, a community set, or an extended
community set.
route-policy read,
write
Examples In the following example, the end-set command ends the definition of an AS path set named aset1:
RP/0/RSP0/CPU0:router(config-as)# end-set
RP/0/RSP0/CPU0:router(config)#
The following example shows how to create an RD set called my_rd_set and use the end-set
command to end the definition:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1544
Routing Policy Language Commands
end-set
RP/0/RSP0/CPU0:router(config-rd)# 172.16.0.0/16:*,
RP/0/RSP0/CPU0:router(config-rd)# 172.17.0.0/16:100,
RP/0/RSP0/CPU0:router(config-rd)# 192:*,
RP/0/RSP0/CPU0:router(config-rd)# 192:100
RP/0/RSP0/CPU0:router(config-rd)# end-set
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1545
Routing Policy Language Commands
extcommunity rt is-empty
extcommunity rt is-empty
To check if a Border Gateway Protocol (BGP) route has route target (RT) extended community attributes
associated with it, use the extcommunity rt is-empty command in route-policy configuration mode.
extcommunity rt is-empty
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity rt is-empty command as a conditional expression within an if statement to check
if a BGP route has extended community attributes associated with it.
Note For a list of all conditional expressions available within an if statement, see the if command.
The is-empty operator takes no arguments and evaluates to true if the route has no extended community
attributes associated with it.
route-policy read,
write
Examples In the following example, if the extended community is empty, then the local preference is set to
100:
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1546
Routing Policy Language Commands
extcommunity rt matches-any
extcommunity rt matches-any
To match any element of a Border Gateway Protocol (BGP) route target (RT) extended community set, use
the extcommunity rt matches-any command in route-policy configuration mode.
inline-extcommunity-set Inline RT extended community set. The inline extended community set must be
enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity rt matches-any command as a conditional expression within an if statement to
match elements of an extended community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-any operator evaluates as true if at least one extended community in
the route matches an extended community specification in the named or inline set. If no extended community
in the route matches any of the specifications in the named or inline set, then this simple condition evaluates
to false. Likewise, when there is no extended community at all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. In
inline sets, extended community specifications may be parameterized, in which case the relevant matching is
done when the value of the parameter has been supplied.
route-policy read,
write
Examples In the following example, an extended community set named my-extcommunity-set and a
parameterized route-policy named my-extcommunity-set-example($tag,$ip) are defined. The
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1547
Routing Policy Language Commands
extcommunity rt matches-any
extcommunity rt matches-any command is used in an if statement such that if at least one extended
community in the route matches an extended community specification in the named set, then the
local preference is set to 100. If there is no extended community in the route that matches any of the
specifications in the named set, then the condition evaluates as false and the extended community is
compared to the inline extended sets.
extcommunity rt matches-every, on page 1549 Matches every element of a BGP RT extended community
set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1548
Routing Policy Language Commands
extcommunity rt matches-every
extcommunity rt matches-every
To match every element of a Border Gateway Protocol (BGP) route target (RT) extended community set, use
the extcommunity rt matches-every command in route-policy configuration mode.
inline-extcommunity-set Inline RT extended community set. The inline extended community set must be
enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity rt matches-every command as a conditional expression within an if statement to
match every element of an RT extended community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-every operator evaluates as true if every extended community value
in the extended community attribute for the route matches at least one element of the extended community
set or inline set. If no extended community in the route matches any of the specifications in the named or
inline set, then this simple condition evaluates to false. Likewise, when there is no extended community at
all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. In
inline sets, extended community specifications may be parameterized, in which case the relevant matching is
done when the value of the parameter has been supplied.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1549
Routing Policy Language Commands
extcommunity rt matches-every
Examples In the following example, an extended community set named my-extcommunity-set and a
parameterized route policy named extcommunity-matches-every-example ($as, $tag) are defined.
The condition extcommunity rt matches-every is used in an if statement in this policy. If it evaluates
to true, the local-preference value is set to 100. If it evaluates to false, the extended community is
evaluated using an inline set. If that condition evaluates to true, the local-preference value is set to
200. If it evaluates to false, the local-preference value is set to 300.
extcommunity rt matches-any, on page 1547 Matches any element of a BGP RT extended community set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1550
Routing Policy Language Commands
extcommunity rt matches-within
extcommunity rt matches-within
To match at least one element of an extended community set of a Border Gateway Protocol (BGP) route target
(RT), use the extcommunity rt matches-within command in route-policy configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity rt matches-within command as a conditional expression within an if statement to match
elements of an extended community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-within operator evaluates as true if all the elements in extended
community from the route match any element in the extended community set. For example, let 'c' be the RTs
from the route and 'm' be the RT set from the policy. With the extcommunity rt matches-within configuration,
each value in 'c' must match any (or at least one) value in 'm'.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. In
inline sets, extended community specifications may be parameterized, in which case the relevant matching is
done when the value of the parameter has been supplied.
In the following example, an extended community set named my-extcommunity-set and a parameterized
route-policy named my-extcommunity-set-example($tag,$ip) are defined. The extcommunity rt
matches-within command is used in an if statement such that if all extended community values in
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1551
Routing Policy Language Commands
extcommunity rt matches-within
the route match any element of the extended community specification in the named set, then the local
preference is set to 100.
RP/0/RSP0/CPU0:router(config)#extcommunity-set rt my-extcommunity-set
RP/0/RSP0/CPU0:router(config-ext)#10:615,
RP/0/RSP0/CPU0:router(config-ext)#10:6150,
RP/0/RSP0/CPU0:router(config-ext)#15.15.15.15:15
RP/0/RSP0/CPU0:router(config-ext)#end-set
RP/0/RSP0/CPU0:router(config)#route-policy my-extcommunity-set-example($tag,$ip)
RP/0/RSP0/CPU0:router(config-rpl)#if extcommunity rt matches-within my-extcommunity-set
then
RP/0/RSP0/CPU0:router(config-rpl-if)#set local-preference 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1552
Routing Policy Language Commands
extcommunity-set cost
extcommunity-set cost
To define a cost extended community set, use the extcommunity-set cost command in global configuration
mode. To remove the cost extended community set, use the no form of this command.
Syntax Description name Name of a cost extended community set. The name argument is case sensitive, can contain any
alphanumeric characters, and can be up to 63 characters in length.
Release 3.9.0 Support was added for more cost extended community formats.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity-set cost command to define a cost extended community set.
An extended community set is analogous to a community set except that it contains extended community
values instead of regular community values. Extended community values are 64-bit structured values. An
extended community set also supports named forms and inline forms.
Cost extended communities can be entered in these formats:
• #-remark ---Remark beginning with '#'
• 0-255---Decimal number
• abort ---Discard RPL definition and return to top level config
• end-set ---End of set definition
• exit ---Exit from the submode
• igp:---Cost Community with IGP as point of insertion
• pre-bestpath: ---Cost Community with Pre-Bestpath as point of insertion
• show ---Show partial RPL configuration
Multiple cost community set clauses can be configured in each route policy block or sequence. Each cost
community set clause must have a different ID (0-255). The cost community set clause with the lowest
cost-value is preferred by the best path selection process when all other attributes are equal.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1553
Routing Policy Language Commands
extcommunity-set cost
As with community sets, the inline form supports parameterization within parameterized policies. Either
portion of the extended community value can be parameterized.
Every extended community set must contain at least one extended community value. Empty extended
community sets are invalid and the policy configuration system rejects them.
Wildcards (*) and regular expressions are allowed for extended community set elements.
Examples In the following example, a cost extended community set named extcomm-cost is defined:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1554
Routing Policy Language Commands
extcommunity-set rt
extcommunity-set rt
To define a Border Gateway Protocol (BGP) route target (RT) extended community set, use the
extcommunity-set rt command in global configuration mode. To remove the RT community set, use the
no form of this command.
extcommunity-set rt name
no extcommunity-set rt name
Release 3.9.0 Support was added for more rt extended community formats.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity-set rt command to define an RT extended community set for BGP.
Regular expressions and ranges can be specified to match the extended communities. Regular expressions
and ranges can be specified in an extended community set to support the matching of communities. An attempt
to use an extended community set that contains a range or regular expression to set an extended community
set value is rejected when an attempt to attach such a policy is made.
An extcommunity set RT holds RT extended community values to match against the Border Gateway Protocol
(BGP) RT extended community attribute. RT extended communities can be entered in these formats:
• #-remark ---Remark beginning with '#'
• *--- Wildcard (any community or part thereof)
• 1-4294967295---32-bit decimal number
• 1-65535 ---16-bit decimal number
• A.B.C.D/M:N ---Extended community - IPv4 prefix format
• A.B.C.D:N---Extended community - IPv4 format
• ASN:N ---Extended community - ASPLAIN format
• X.Y:N ---Extended community - ASDOT format
• dfa-regex ---DFA (deterministic finite automata) style regular expression
• ios-regex ---Traditional IOS style regular expression
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1555
Routing Policy Language Commands
extcommunity-set rt
Note The dfa-regex and ios-regex syntax for community set is "['][^':&<> ]*:[^':&<>
]*[']". This means that regex starts with a single-quote (") followed by a string
of any character (that does not include single-quote, colon, ampersand, less-than,
greater-than, or space) followed by a colon, and a string of any characters (that
does not include single-quote, colon, ampersand, less-than, greater-than, or space)
followed by single-quote.
Examples In the following example, an RT extended community set named extcomm-rt is defined:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1556
Routing Policy Language Commands
extcommunity-set soo
extcommunity-set soo
To define a Border Gateway Protocol (BGP) Site-of-Origin (SoO) extended community set, use the
extcommunity-set soo command in global configuration mode. To remove the SoO extended community
set, use the no form of this command.
Release 3.9.0 Support was added for more soo extended community formats.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity-set soo command to define an SoO extended community set.
An extcommunity set soo holds SoO extended community values to match against the Border Gateway Protocol
(BGP) SoO extended community attribute. SoO extended communities can be entered in these formats:
• #-remark ---Remark beginning with '#'
• *--- Wildcard (any community or part thereof)
• 1-4294967295---32-bit decimal number
• 1-65535 ---16-bit decimal number
• A.B.C.D/M:N ---Extended community - IPv4 prefix format
• A.B.C.D:N---Extended community - IPv4 format
• ASN:N ---Extended community - ASPLAIN format
• X.Y:N ---Extended community - ASDOT format
• abort ---Discard RPL definition and return to top level config
• dfa-regex ---DFA style regular expression
• end-set ---End of set definition
• exit ---Exit from the submode
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1557
Routing Policy Language Commands
extcommunity-set soo
N is a site-specific number.
Examples In the following example, a SoO extended community set named extcomm-soo is defined:
RP/0/RSP0/CPU0:router(config-ext)# 100.100.100.1:153
RP/0/RSP0/CPU0:router(config-ext)# end-set
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1558
Routing Policy Language Commands
extcommunity soo is-empty
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity soo is-empty command as a conditional expression within an if statement to check
if a BGP SoO route has extended community attributes associated with it.
Note For a list of all conditional expressions available within an if statement, see the if command.
The is-empty operator takes no arguments and evaluates to true if the route has no SoO extended community
attributes associated with it.
route-policy read,
write
Examples In the following example, if a route has no SoO extended communities associated with it, the local
preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1559
Routing Policy Language Commands
extcommunity soo matches-any
inline-extcommunity-set Inline SoO extended community set. The inline extended community set must be
enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity soo matches-any command as a conditional expression within an if statement to
match elements of an extended community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-any operator evaluates as true if at least one extended community in
the route matches an extended community specification in the named or inline set. If no extended community
in the route matches any of the specifications in the named or inline set, then this simple condition evaluates
to false. Likewise, when there is no extended community at all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. In
inline sets, extended community specifications may be parameterized, in which case the relevant matching is
done when the value of the parameter has been supplied.
route-policy read,
write
Examples In the following example, an SoO extended community set named extcomm-soo and a parameterized
route policy named my-extcommunity-set-example($tag,$ip) are defined.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1560
Routing Policy Language Commands
extcommunity soo matches-any
The condition route policy named extcommunity soo matches-any is used in an if statement in this
policy. If it evaluates to true, the local preference value is set to 100.
If it evaluates to false, the SoO extended community is evaluated using an inline set. If it evaluates
to true, the local preference value is set to 200.
If it evaluates to false, the SoO extended community is evaluated using a different inline set. If it
evaluates to true, the local preference value is set to 300.
If it evaluates to false, the SoO extended community is evaluated using a different inline set. If it
evaluates to true, the local preference value is set to 400.
extcommunity rt matches-any, on page 1547 Matches any element of a BGP RT extended community
set.
extcommunity soo matches-every, on page 1562 Matches every element of a BGP SoO extended community
set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1561
Routing Policy Language Commands
extcommunity soo matches-every
inline-extcommunity-set Inline SoO extended community set. The inline extended community set must be
enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the extcommunity soo matches-every command as a conditional expression within an if statement
to match every element of a SoO extended community set.
Note For a list of all conditional expressions available within an if statement, see the if command.
A simple condition using the matches-every operator evaluates as true if every extended community value
in the extended community attribute for the route matches at least one element of the extended community
set or inline set. If no extended community in the route matches any of the specifications in the named or
inline set, then this simple condition evaluates to false. Likewise, when there is no extended community at
all in the route, the condition evaluates to false.
Matching an extended community in the route to a specification in a named or an inline set is intuitive. In
inline sets, extended community specifications may be parameterized, in which case the relevant matching is
done when the value of the parameter has been supplied.
Examples In the following example, an extended community set named my-extcomm-rt-set and a parameterized
route policy named extcommunity-matches-every-example($as, $tag) are defined. The condition
extcommunity soo matches-every is used in an if statement in this policy and if it evaluates to true,
the local-preference value is set to 100. If it evaluates to false, the extended community is evaluated
using an inline set. If that condition evaluates to true, the local-preference value is set to 200. If it
evaluates to false, the local-preference value is set to 300.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1562
Routing Policy Language Commands
extcommunity soo matches-every
extcommunity soo matches-any, on page 1560 Matches any element of a BGP SoO extended community set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1563
Routing Policy Language Commands
globalVarN is
globalVarN is
To check the value of globalVarN value assigned through the var globalVarN command, use the globalVarN
is command in router-policy configuration mode.
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is from 1 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Command Default If the globalVarN is not assigned using the var globalVarN command, then the default value for globalVarN
is zero.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The scope of this variable is from the start of policy to end of policy attached under any attach-point. The
variable can be assigned in any child policy and can check for value in parent policy or any other hierarchy
of route-policy referred using apply statement.
Example
This example is to identify routes which has communities configured under community-sets
internal_set and service2 and set different local-preference values based on the community values.
community-set internal_set
1:1
end-set
community-set service2
3:3
end-set
route-policy child1
var globalVar1 100
#... user can add more actions or conditions...
end-policy
route-policy child2
var globalVar2 200
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1564
Routing Policy Language Commands
globalVarN is
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1565
Routing Policy Language Commands
if
if
To decide which actions or dispositions should be taken for a given route, use the if command in route-policy
configuration mode.
Syntax Description conditional-expression Expression to decide which actions or dispositions should be taken for the given
route.
Release 4.2.0 Support was added for Apply Condition Policies that allow the usage of a route-policy in an
"if" statement of another route-policy.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The if command uses a conditional expression to decide which actions or dispositions should be taken for
a given route. Table 172: Conditional Expressions, on page 1567 lists the conditional expressions.
An action statement is a sequence of operations that modify a route, most of which are distinguished by the
set keyword. In a route policy, these operations can be grouped. Table 173: Action Statements, on page 1568
lists the action statements.
Apply Condition policies allow usage of a route-policy in an "if" statement of another route-policy.
Route-policy policy_name
If apply policyA and apply policyB then
Set med 100
Else if not apply policyD then
Set med 200
Else
Set med 300
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1566
Routing Policy Language Commands
if
Endif
End-policy
Command Description
as-path in, on page 1505 Matches the AS path of a route to an AS path set. The AS path
is a sequence of autonomous system numbers traversed by a
route.
as-path is-local, on page 1507 Determines if the router (or another router within this
autonomous system or confederation) originated the route.
as-path length, on page 1508 Performs a conditional check based on the length of the AS path.
as-path neighbor-is, on page 1510 Tests the autonomous system number or numbers at the head of
the AS path against a sequence of one or more integral values
or parameters.
as-path originates-from, on page 1513 Tests an AS path against the AS sequence beginning with the
AS number that originated a route.
as-path passes-through, on page 1515 Tests to learn if the specified integer or parameter appears
anywhere in the AS path or if the sequence of integers and
parameters appears.
as-path unique-length, on page 1519 Performs specific checks based on the length of the AS path.
community is-empty, on page 1521 Learns if a route has community attributes associated with it.
destination in, on page 1533 Matches a destination entry in a named prefix set or inline prefix
set.
extcommunity rt is-empty, on page 1546 Learns if a route has RT extended community attributes
associated with it.
extcommunity rt matches-within, on page Matches at least one element of a Border Gateway Protocol
1551 (BGP) route target (RT) extended community set.
extcommunity soo is-empty, on page 1559 Learns if a route has SoO extended community attributes
associated with it.
extcommunity soo matches-any, on page Matches elements of an SoO extended community set.
1560
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1567
Routing Policy Language Commands
if
Command Description
extcommunity soo matches-every, on page Matches every element of an SoO extended community set.
1562
med, on page 1577 Compares the MED to an integer value or a parameterized value.
next-hop in, on page 1578 Compares the next-hop associated with the route to data
contained in either a named or an inline prefix set.
orf prefix in, on page 1580 Matches a prefix in a prefix set or an inline prefix set.
origin is, on page 1582 Tests the value of the origin attribute.
rd in, on page 1600 Compares the RD associated with the route to data contained in
either a named or an inline RD set.
route-has-label, on page 1608 Checks if a route has a Multiprotocol Label Switching (MPLS)
label.
route-type is, on page 1611 Compares route types when redistribution is being performed
into BGP, OSPF, or IS-IS.
source in, on page 1761 Tests the source of the route against the data in either a named
or an inline prefix set.
vpn-distinguisher is, on page 1771 Compares the VPN distinguisher against a specified value.
Command Description
abort (RPL), on page 1499 Discards a route policy definition and returns to global configuration
mode.
delete community, on page 1529 Deletes community values from a community list in a route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1568
Routing Policy Language Commands
if
Command Description
delete extcommunity rt, on page 1531 Deletes extended community values from an extended community list
in a route.
end-policy, on page 1543 Ends the definition of a route policy and exits route-policy configuration
mode.
pass, on page 1588 Signifies that even though the route has not been modified, the user
wants to continue executing in the policy block.
prepend as-path, on page 1596 Prepends the AS path with additional autonomous system numbers.
replace as-path, on page 1603 Replaces a sequence of AS numbers or private AS numbers in the AS
path with the configured local AS.
set eigrp-metric, on page 1624 Sets the Enhanced Interior Gateway Routing Protocol (EIGRP) metric
value.
set extcommunity cost, on page 1626 Replaces or adds the extended communities for a cost on the route.
set extcommunity rt, on page 1628 Replaces or adds the extended communities for an RT on the route.
set isis-metric, on page 1632 Sets the IS-IS metric attribute value.
set label, on page 1633 Sets the BGP label attribute value.
set level, on page 1636 Configures the IS-IS level in which redistributed routes should be sent.
set local-preference, on page 1637 Specifies a preference value for the autonomous system path.
set metric-type (IS-IS), on page 1640 Controls whether IS-IS treats the metric as an internal or external
metric.
set metric-type (OSPF), on page 1641 Controls whether OSPF treats the cost as a Type 1 or Type 2 metric.
set next-hop, on page 1642 Replaces the next-hop associated with a given route.
set ospf-metric, on page 1645 Sets an OSPF protocol metric attribute value.
set qos-group (RPL), on page 1648 Sets the QoS group to classify packets.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1569
Routing Policy Language Commands
if
Command Description
set rib-metric, on page 1649 Sets a RIB metric attribute value for a table policy.
set weight, on page 1660 Sets the weight value for BGP routes.
suppress-route, on page 1763 Indicates that a given component of an aggregate should be suppressed,
that is, not advertised.
route-policy read,
write
Examples In the following example, any route whose AS path is in the set as-path-set-1 is dropped:
The contents of the then clause may be an arbitrary sequence of action statements.
The following example shows an if statement with two action statements:
The if command also permits an else clause to be executed if the expression is false, as follows:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1570
Routing Policy Language Commands
if
The routing policy language (RPL) also provides syntax using the elseif command to string together
a sequence of tests, as shown in the following example:
The statements within an if statement may themselves be if statements, as shown in this example:
The policy configuration shown sets the value of the local preference attribute to 100 on any route
that has a community value of 12:34 or 56:78 associated with it. However, if any of these routes has
a Multi Exit Descriminator (MED) value of 150, then each route with both the community value of
12:34 or 56:78 and a MED of 150 is dropped.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1571
Routing Policy Language Commands
if route-aggregated
if route-aggregated
To match the aggregated routes from the other routes, use the if route-aggregated command in route policy
configuration mode.
if route-aggregated
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples This example shows how to match the aggregated routes from other routes:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# route-policy route-policy atomic_agg
RP/0/RSP0/CPU0:router(config-rpl)# if route-aggregated then
RP/0/RSP0/CPU0:router(config-rpl-if)# set extcommunity rt (1:1)
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1572
Routing Policy Language Commands
is-best-path
is-best-path
To tag the path selected as the best path use theis-best-path command in route policy configuration mode.
is-best-path
Syntax Description is-best-path Checks and tags the path selected as best-path.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
RP/0/RSP0/CPU0:router(config)# route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# if destination i
in is-backup-path is-best-external is-best-path
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1573
Routing Policy Language Commands
is-backup-path
is-backup-path
To tag all the paths equal to the back up path use, is-backup-path command in route policy configuration
mode.
is-backup-path
Syntax Description is-backup-path Checks and tags the path selected as backup path.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
RP/0/RSP0/CPU0:router(config)# route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# if destination i
in is-backup-path is-best-external is-best-path
RP/0/RSP0/CPU0:router(config)# route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# if destination i
in is-backup-path is-best-external is-best-path
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1574
Routing Policy Language Commands
is-multi-path
is-multi-path
To tag all the paths equal to the best path based on multi-path context use, is-multi-path command in route
policy configuration mode.
is-multi-path
Syntax Description is-multi-path Checks and tag all the path equal to the as best-path.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Example
RP/0/RSP0/CPU0:router(config)#route-policy
WORD Route Policy name
RP/0/RSP0/CPU0:router(config)#route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)#if destination i
in is-backup-path is-best-external is-best-path
is-multi-path
RP/0/RSP0/CPU0:router(config-rpl)#if destination is-
is-backup-path is-best-external is-best-path is-multi-path
RP/0/RSP0/CPU0:router(config-rpl)#if destination is-best-path then
RP/0/RSP0/CPU0:router(config-rpl-if)#set l
label label-index label-mode level
community lsm-root
RP/0/RSP0/CPU0:router(config-rpl-if)#set community community
RP/0/RSP0/CPU0:router(config-rpl-if)#endif
RP/0/RSP0/CPU0:router(config-rpl)#end-policy
RP/0/RSP0/CPU0:router(config)#commit
Wed Jul 8 16:08:23.436 IST
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1575
Routing Policy Language Commands
local-preference
local-preference
To compare the local-preference attribute of a BGP route to an integer value or a parameterized value, use
the local-preference command in route-policy configuration mode.
Syntax Description eq | is | ge | le Equal to; exact match; greater than or equal to; less than or equal to.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the local- preference command as a conditional expression within an if statement to compare the
local-preference attribute to an integer value or a parameterized value.
Note For a list of all conditional expressions available within an if statement, see the if command.
The MED is a 32-bit unsigned integer. The eq operation compares the local-preference to either a static value
or a parameterized value passed to a parameterized policy for equality with that value. A greater than or equal
to comparison can also be done with the ge operator, and a less than or equal to comparison can be performed
using the le operator.
Examples The following example shows that if the local-preference is 10, local-preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1576
Routing Policy Language Commands
med
med
To compare the Multi Exit Discriminator (MED) to an integer value or a parameterized value or compare the
MED attribute of a BGP route to an integer value, use the med command in route-policy configuration mode.
Syntax Description eq | is | ge | le Equal to; exact match; greater than or equal to; less than or equal to.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the med command as a conditional expression within an if statement to compare the MED to an integer
value or a parameterized value.
Note For a list of all conditional expressions available within an if statement, see the if command.
The MED is a 32-bit unsigned integer. The eq operation compares the MED to either a static value or a
parameterized value passed to a parameterized policy for equality with that value. A greater than or equal to
comparison can also be done with the ge operator, and a less than or equal to comparison can be performed
using the le operator.
route-policy read,
write
Examples The following example shows that if the med commands match, the local preference is set to 100:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1577
Routing Policy Language Commands
next-hop in
next-hop in
To compare the next-hop associated with the route to data contained in either an inline or a named prefix set,
use the next-hop in command in route-policy configuration mode.
next-hop in {prefix-set-nameinline-prefix-setparameter}
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the next-hop in command as a conditional expression within an if statement to compare the next-hop
associated with the route to data contained in either an inline or a named prefix set. The result is true if any
value in the prefix set matches the next-hop of the route. A comparison that refers to a named prefix set that
has no elements in it returns false.
Note For a list of all conditional expressions available within an if statement, see the if command.
The next-hop is an IPv4 address entered as a dotted-decimal or an IPv6 address entered as a colon-separated
hexadecimal.
route-policy read,
write
Examples The following example shows that if the next-hop in commands match, the local preference is set
to 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1578
Routing Policy Language Commands
next-hop in
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1579
Routing Policy Language Commands
orf prefix in
orf prefix in
To configure an outbound route filter (ORF), use the orf prefix in command in route-policy configuration
mode.
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the orf prefix in command to match a prefix in a prefix set or an inline prefix set.
This command takes either a named prefix set or an inline prefix set value as an argument. It returns true if
the destination NLRI matches any entry in the prefix set. An attempt to match destination using a prefix set
that is defined but contains no elements returns false.
This command is used in the context of the orf route-policy attach point in BGP. The destination of a route
is also known in Border Gateway Protocol (BGP) as its network-layer reachability information (NLRI). It
comprises a prefix value and a mask length. The routing policy language (RPL) provides one operation on
prefixes, testing them for matching against a list of prefix-match specifications using the in operator.
Examples In the following example, the prefix set orfpreset1 and the route policy named orfpolicy are defined.
Next, the orfpolicy is applied to the neighbor orf attach point.
If the prefix of the route matches any of the prefixes specified in orfpreset1 (211.105.1.0/24,
211.105.5.0/24, 211.105.11.0/24), then the prefix is dropped. If the prefix matches in(211.105.3.0/24,
211.105.7.0/24, 211.105.13.0/24), then the prefix is accepted. In addition to this inbound filtering,
BGP sends these prefix entries to the upstream neighbor indicating a permit or deny so that the
neighbor can make the same filter updates.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1580
Routing Policy Language Commands
orf prefix in
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1581
Routing Policy Language Commands
origin is
origin is
To match a specific origin type, use the origin is command in route-policy configuration mode.
incomplete Specifies that Border Gateway Protocol (BGP) first learned the route by means other than BGP
or Interior Gateway Protocol (IGP); for example, the route is learned through configuration.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the origin is command as a conditional expression within an if statement to test the value of the origin
attribute.
Note For a list of all conditional expressions available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, the origin is tested within an if statement to learn if it is either igp or
egp :
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1582
Routing Policy Language Commands
origin is
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1583
Routing Policy Language Commands
ospf-area
ospf-area
To match a specific ospf area, use the ospf-area command in route-policy configuration mode.
in Specify a list of area-id or area-set. Multiple areas can be specified separated by a comma (,).
all-paths Used for routes with multiple paths. A match is made if area for every path of the route is
configured in the route-policy.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The route policy define by using ospf-area is useful in redistributing routes from a specific area of a routing
domain into OSPF. After the route policy is crated, use the redistribute ospf route-policy command for route
redistribution.
route-policy read,
write
Example
In the following example, an explicit area is specified as the matching criteria.
In the following example, an area set is specified as the matching criteria. As a pre-requisite, the area
set must be defined.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1584
Routing Policy Language Commands
ospf-area
RP/0/RSP0/CPU0:router(config)# ospf-area-set S1
RP/0/RSP0/CPU0:router(config-ospf-area)# 1 , 2.2.2.2 end-set
RP/0/RSP0/CPU0:router(config)# route-policy P1
RP/0/RSP0/CPU0:router(config-rpl)# if ospf-area in S1 then pass else drop endif
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1585
Routing Policy Language Commands
ospf-area-set
ospf-area-set
Defines an OSPF area set to be used in routing policy statements.
<A.B.C.D> IPv4 Address used to identify the set, or the IPv4 address of the ACL.
route-policy read,
write
Example
The example shows how you can configure OSPF area sets with wildcards in routing policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1586
Routing Policy Language Commands
ospf-area-set
ospf-metric 300
RP/0/RSP0/CPU0:router(config-rpl-elseif)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1587
Routing Policy Language Commands
pass
pass
To pass a route for further processing, use the pass command in route-policy configuration mode.
pass
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the pass command to signify that even though this route has not been modified, the user wants to continue
executing in this policy block.
Note The pass command can be used as an action statement within an if statement. For a list of all action statements
available within an if statement, see the if command.
When a policy block has finished executing, any route that has been modified in this policy block or has
received a pass disposition in this policy block passes the policy and execution finishes for that policy. If this
policy block is applied from within another policy block and the route is either passed or modified, then
execution continues in the policy block that applied this policy block.
route-policy read,
write
Examples The following example shows how to accept the route unconditionally without modifying it:
RP/0/RSP0/CPU0:router(config-rpl)# pass
This example accepts the route unconditionally, without modifying it, if the destination is in prefix-set
permitted:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1588
Routing Policy Language Commands
pass
RP/0/RSP0/CPU0:router(config-rpl)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1589
Routing Policy Language Commands
path-type is
path-type is
To match path types, use the path-type is command in route-policy configuration mode.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the path-type is command as a conditional expression within an if statement to match path types.
Note For a list of all conditional expressions available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, if the path is an external BGP path the route is accepted:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1590
Routing Policy Language Commands
policy-global
policy-global
To define global parameters and enter global parameter configuration mode, use the policy-global command
in global configuration mode. To remove global parameters, use the no form of this command.
policy-global
no policy-global
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the policy-global command to define global parameters and enter global parameter configuration mode.
RPL supports the definition of systemwide global parameters that can be used inside a policy definition. The
global parameter values can be used directly inside a policy definition similar to the local parameters of
parameterized policy. When a parameterized policy has a parameter name “collision” with a global parameter
name, parameters local to policy definition take precedence, effectively ‘masking off’ global parameters. In
addition, a validation mechanism is in place to prevent the deletion of a particular global parameter if it is
referred by any policy. For more information on global parameters and parameterization, see the Implementing
Routing Policy module of the Routing Configuration Guide for Cisco ASR 9000 Series Routers
route-policy read,
write
RP/0/RSP0/CPU0:router(config)# policy-global
RP/0/RSP0/CPU0:router(config-rp-gl)# glbpathtype ‘ebgp’
RP/0/RSP0/CPU0:router(config-rp-gl)# glbtag ‘100’
RP/0/RSP0/CPU0:router(config-rp-gl)# end-global
In the following example, the globalparam argument makes use of the global parameters gbpathtype
and glbtag defined above and is defined for a nonparameterized policy:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1591
Routing Policy Language Commands
policy-global
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1592
Routing Policy Language Commands
prefix-set
prefix-set
To enter prefix set configuration mode and define a prefix set for contiguous and non-contiguous set of bits,
use the prefix-set command in global configuration mode. To remove a named prefix set, use the no form
of this command.
prefix-set name
no prefix-set name
Release 5.1.1 The command was modified to accept IPv4 and IPv6 address and address mask to define a
prefix set.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the prefix-set command to enter prefix set configuration mode and define a prefix set.
A prefix set is a comma-separated list of prefix match specifications. It holds IPv4 or IPv6 prefix match
specifications, each of which has four parts: an address, a mask length, a minimum matching length, and a
maximum matching length. The address is required, but the other three parts are optional. The address is a
standard four-part, dotted-decimal numeric IPv4 address or a colon-separated hexadecimal IPv6 address. The
mask length, if present, is a nonnegative decimal integer in the range from 0 to 32 for IPv4 prefixes or 0 to
128 for IPv6 prefixes following the address and separated from it by a slash. The optional minimum matching
length follows the address and optional mask length and is expressed as the keyword ge (mnemonic for
greater than or equal to), followed by a nonnegative decimal integer in the range from 0 to 32 for IPv4 or 0
to 128 for IPv6. The optional maximum matching length follows the rest and is expressed by the keyword
le (mnemonic for less than or equal to), followed by yet another nonnegative decimal integer in the range
from 0 to 32 for IPv4 or 0 to 128 for IPv6. A syntactic shortcut for specifying an exact length for prefixes to
match is the eq keyword, mnemonic for equal to.
If a prefix match specification has no mask length, then the default mask length is 32 for IPv4 or 128 for IPv6.
The default minimum matching length is the mask length. If a minimum matching length is specified, then
the default maximum matching length must be less than 32 for IPv4 prefixes or 128 for IPv6 prefixes. Otherwise,
if neither a minimum nor maximum length is specified, the default maximum length is the mask length.
A prefix set is a list of prefix match specifications. It holds IPv4 or IPv6 prefix match specifications, each of
which has two parts: an address and a mask. The address and mask is a standard dotted-decimal IPv4 or
colon-separated hexadecimal IPv6 address. The prefix set allows the specifying of contiguous and
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1593
Routing Policy Language Commands
prefix-set
non-contiguous set of bits that mus be matched in any route. The set of bits to be matched are provided in the
form of a mask in which a binary 0 means a mandatory match and a binary 1 means a 'do not match' condition.
route-policy read,
write
The first element of the prefix set matches only one possible value, 10.0.1.1/32 or the host address
10.0.1.1. The second element matches only one possible value, 10.0.2.0/24. The third element matches
a range of prefix values, from 10.0.3.0/28 to 10.0.3.255/32. The fourth element matches a range of
values, from 10.0.4.0/24 to 10.0.4.240/28. The fifth element matches prefixes in the range from
10.0.5.0/26 to 10.0.5.252/30. The sixth element matches any prefix of length 28 in the range from
10.0.6.0/28 through 10.0.6.240/28.
The following prefix set consists entirely of invalid prefix match specifications:
Neither the minimum length nor the maximum length is legal without a mask length. The maximum
length must be at least the mask length. The minimum length must be less than 32, the maximum
length of an IPv4 prefix. The maximum length must be equal to or greater than the minimum length.
The following example shows a valid IPv6 prefix set named legal-ipv6-prefix-examples:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1594
Routing Policy Language Commands
prefix-set
In the above example, In the above example, the command defines the prefix-set named acl-prefix-set.
The first element specifies to match all routes having 10 in first octet and 1 in third octet. The second
element matches all routes having prefix as 10.2.2.2 (that is, matches all conditions). The third element
matches all routes having odd numbers in the last octets and the fourth element matches all routes
with any prefix.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1595
Routing Policy Language Commands
prepend as-path
prepend as-path
To prepend the AS path with additional autonomous system numbers, use the prepend as-path command
in route-policy configuration mode.
parameter Parameter name. The parameter name must be preceded with a “$.”
most-recent Specifies that the most recent autonomous system number should be prepended.
number (Optional) Number of times the autonomous system number should be prepended. Range is
1 to 63.
Release 3.9.0 Asplain format for 4-byte Autonomous system numbers notation was supported.
Usage Guidelines Use the prepend as-path command to prepend the AS path with additional autonomous system numbers.
Note The prepend as-path command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
This command can take one or two arguments. The first argument (either a number or parameter) is the
autonomous system number to prepend to the path. The optional second argument (either a number or parameter)
is the number of times the autonomous system number should be prepended.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1596
Routing Policy Language Commands
prepend as-path
Examples The following example shows how to prepend the autonomous system number 666.1 to the AS path
three times:
The following example shows how to prepend the autonomous system number 666.0 to the AS path
one time:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1597
Routing Policy Language Commands
protocol
protocol
To check the protocol that installs the route, use the protocol command in route-policy configuration mode.
Syntax Description in ( protocol-set ) Specifies a member of a set. The protocol-set argument accepts the following
keywords within parentheses:
• bgp —Border Gateway Protocol (BGP)
• connected —Connected routes
• eigrp —Enhanced Interior Gateway Routing Protocol (EIGRP)
• isis —ISO Intermediate System-to-Intermediate System (IS-IS)
• ospf —Open Shortest Path First (OSPF)
• ospfv3 —Open Shortest Path First version 3 (OSPFv3)
• rip —Routing Information Protocol (RIP)
• static —Static routes
Keywords must be separated by a comma.
is protocol-name Specifies a single protocol name, and accepted keywords are similar to the protocol-set
argument.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the protocol command as a conditional expression within an if statement to specify a protocol to install
a route.
Use the in keyword to determine if a protocol listed in the protocol-set is the originator of the route being
filtered.
Use the is keyword to determine if protocol-name is an exact match.
Note For a list of all conditional expressions available within an if statement, see the if command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1598
Routing Policy Language Commands
protocol
route-policy read,
write
Examples The following example shows how to use the protocol command as a conditional expression within
if statements:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1599
Routing Policy Language Commands
rd in
rd in
To compare the route distinguisher (RD) associated with the route to RDs contained in either a named or an
inline RD set, use the rd in command in route-policy configuration mode.
rd in {rd-set-nameinline-rd-setparameter}
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the rd in command as a conditional expression within an if statement to match a destination entry in
a named prefix set or inline prefix set.
Note For a list of all conditional expressions available within an if statement, see the if command.
This command takes either a named RD set or an inline RD set value as an argument. The condition returns
true if the destination entry matches any entry in the RD set or inline RD set. An attempt to match an RD
using an RD set that is defined but contains no elements returns false.
route-policy read,
write
Examples The following example shows the rd in command with an inline RD set value as an argument:
RP/0/RSP0/CPU0:router(config)# route-policy
RP/0/RSP0/CPU0:router(config-rpl)# if rd in (128.1.0.0/16:100) then
RP/0/RSP0/CPU0:router(config-rpl-if)# pass
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1600
Routing Policy Language Commands
rd-set
rd-set
To define a route distinguisher (RD) set and enter RD configuration mode, use the rd-set command in global
configuration mode.
rd-set name
no rd-set name
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the rd-set command to create a set with RD elements and enter RD configuration mode. An RD set is
a 64-bit value prepended to an IPv4 address to create a globally unique Border Gateway Protocol (BGP) VPN
IPv4 address.
route-policy read,
write
Examples The following example shows how to create an RD set called my_rd_set:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1601
Routing Policy Language Commands
rd-set
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1602
Routing Policy Language Commands
replace as-path
replace as-path
To replace a sequence of AS numbers or private AS numbers in the AS path with the configured local AS
number, use the replace as-path command in route-policy configuration mode.
Syntax Description as-number-list (Optional) Sequence of AS numbers to replace. The sequence must be enclosed in single
quotes (‘ ’). You can use 2-byte or 4-byte AS numbers.
• The 2-byte value is entered as a 16-bit unsigned decimal value. The range is 0 to 65535.
• The 4-byte value is entered as two 16-bit unsigned decimal values separated by a period.
The range is 1.0 to 65535.65535.
parameter (Optional) Parameter name. The parameter name must be preceded with a “$.”
private-as Matches within the BGP private AS range. Range is from 64512 to 65534.
Release 4.1.0 This command was supported on ASR 9000 Ethernet Line Card (Cisco ASR 9000's
A9K-SIP-700).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the replace as-path command to replace a sequence of AS numbers or private AS numbers in the AS
path with the local AS numbers. For example, if the AS path is ‘67 65534 100 65533 5 78 89 90’ and the local
AS number is 900, then:
replaces‘5 78’ in the AS path with 900 (from the local AS), and the new path would be‘67 65534 100 65533
900 89 90’.
Consider following statement:
Because 65534 and 65533 are within the private AS range, they are replaced with 900. The path is ‘67 900
100 900 5 78 89 90’. The length of the path remains the same.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1603
Routing Policy Language Commands
replace as-path
The replace as-path command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
Caution The replace as-path command changes the AS path content which can lead to routing loops.
route-policy read,
write
Examples The following example shows how to use the replace as-path command to replace AS numbers
in the AS path:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1604
Routing Policy Language Commands
remove as-path private-as
Syntax Description entire-aspath (Optional) Removes the entire private autonomous system numbers from an autonomous
system path only if all the autonomous systems in the path are private.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples This example shows how to remove BGP private AS numbers from as-path structure:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# route-policy rm_private_as
RP/0/RSP0/CPU0:router(config-rpl)# remove as-path private-as entire-aspath
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1605
Routing Policy Language Commands
rib-has-route
rib-has-route
To check if a route listed in the prefix set exists in the Routing Information Base (RIB), use the rib-has-route
command in route-policy configuration mode.
rib-has-route in {prefix-set-nameinline-prefix-setparameter}
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If routes are active, then they are advertised. Routes are considered active if they are already installed in the
Routing Information Base (RIB).
The prefix sets used in the rib-has-route command contain two match specifications. The first is where an
exact route match is requested (for example, 10.10.0.0/16 will match exactly one route) and the second is
where a route match or any more-specific route match is allowed (for example, 10.10.0.0/16 le 32 will match
the 10.10.0.0/16 route and any longer prefix).
Use the rib-has-route command as a conditional expression within an if statement to check if there is an
active route with a specific prefix contained in the RIB. If the statement reveals an active route that meets that
criteria, additional actions are executed.
For a list of all conditional expressions available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, an if statement is used to learn if a route contained in a prefix set
10.10.0.0/16 is in the RIB:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1606
Routing Policy Language Commands
rib-has-route
RP/0/RSP0/CPU0:router(config-rpl)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1607
Routing Policy Language Commands
route-has-label
route-has-label
To check if there is a Multiprotocol Label Switching (MPLS) label in a route during redistribution, use the
route-has-label command in route-policy configuration mode.
route-has-label
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-has-label command as a conditional expression within an if statement to check if there is
an MPLS label in a route during redistribution.
For a list of all conditional expressions available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, an if statement learns if an MPLS label is present in a route:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1608
Routing Policy Language Commands
route-policy (RPL)
route-policy (RPL)
To define a route policy and enter route-policy configuration mode, use the route-policy command in global
configuration mode. To remove a policy definition, use the no form of this command.
parameter (Optional) Parameter name. The parameter name must be preceded with a “$.” The parameters
must be enclosed in parenthesis “()”.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-policy command to define a route policy and enter route-policy configuration mode.
Policy definitions create named bundles of policy statements. A policy definition consists of the route-policy
command followed by a name, a group of policy statements, and the end-policy command.
The policy name serves as a handle for binding the policy to protocols.
route-policy read,
write
Examples The following example shows a simple policy named drop-everything that drops any route it
encounters:
Policies may also refer to other policies such that common blocks of policy can be reused. This
reference to other policies is accomplished by using the apply command. The following is a simple
example:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1609
Routing Policy Language Commands
route-policy (RPL)
The apply command indicates that the policy check-communities should be executed if the route
under consideration passed through autonomous system 1234 before it was received. If so, the
communities of the route are checked, and based on the findings the route may be accepted unmodified,
accepted with changes, or dropped.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1610
Routing Policy Language Commands
route-type is
route-type is
To match route types when redistribution is being performed into Border Gateway Protocol (BGP), Open
Shortest Path First (OSPF), or Integrated Intermediate System-to-Intermediate System (IS-IS), use the
route-type is command in route-policy configuration mode.
Syntax Description local Uses a local value to match locally generated BGP routes.
internal Uses an internal value to match OSPF intra- and interarea routes.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the route-type is command as a conditional expression within an if statement to compare route types
when redistribution is being performed into BGP, OSPF, or IS-IS.
Note For a list of all conditional expressions available within an if statement, see the if command.
The valid keywords are local , internal , interarea , type-1 , type-2 , level-1 , and level-2 . A parameterized
value that fills in one of these values may also be used. The local value is used to match locally generated
BGP routes. The internal value is used to match OSPF intra- and interarea routes. The type-1 and type-2
values are used to match Type 1 and Type 2 OSPF external routes. The level-1 , level-2 , and interarea
values are used to match IS-IS routes of those respective types.
Because the route type is a matching operator, it appears in conditional clauses of if and then statements.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1611
Routing Policy Language Commands
route-type is
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1612
Routing Policy Language Commands
rpl editor
rpl editor
To set the default routing policy language (RPL) editor, use the rpl editor command in global configuration
mode.
Syntax Description nano Sets the default RPL editor to GNU nano.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
route-policy read,
write
Examples In the following example, the default RPL editor is set to Nano:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# rpl editor nano
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# rpl editor emacs
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# rpl editor vim
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1613
Routing Policy Language Commands
rpl maximum
rpl maximum
To configure system limits on the routing policy subsystem, use the rpl maximum command in global
configuration mode.
Syntax Description lines number Configures the number of lines of configuration limit. Range is from 1 to 131072.
policies number Configures the number of policies limit. Range is from 1 to 5000.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the rpl maximum command to configure system limits on the routing policy subsystem. As such, rpl
maximum configuration lines do not appear as statements within a routing policy. This command places
resource limits on the routing policy subsystem. Use the rpl maximum command to configure the maximum
number of lines of configuration and number of policies.
The number of lines of configuration includes the beginning and ending statements , for example, route-policy
and end-policy . Each line of configuration for sets is also counted.
A line of configuration is counted only once; it is not counted each time it is used. Similarly, any multiple use
of policy in an apply statement counts only as one policy.
A user can change the default values for lines and policies but cannot exceed the maximum value, nor can
the value for lines and policies be configured lower than the number of lines or policies that are currently
configured.
route-policy read,
write
Examples In the following example, the maximum number of RPL system limits are modified:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# rpl maximum lines 50
RP/0/RSP0/CPU0:router(config)# rpl maximum policies 6
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1614
Routing Policy Language Commands
rpl maximum
show rpl maximum, on page 1714 Displays the maximum limits for lines of configuration and number of
policies.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1615
Routing Policy Language Commands
rpl set-exit-as-abort
rpl set-exit-as-abort
To change the default exit behavior under RPL configuration mode to abort from the RPL configuration mode
without saving the configuration, use the rpl set-exit-as-abort command in global configuration mode.
rpl set-exit-as-abort
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The default exit command acts as end-policy, end-set, or end-if. If the exit command is executed under route
policy configuration mode, the changes are applied and configuration is updated. This destructs the existing
policy. The rpl set-exit-as-abort command allows to overwrite the default behavior of the exit command
under the route policy configuration mode.
Examples This example shows how change the default exit behavior:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# rpl set-exit-as-abort
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1616
Routing Policy Language Commands
set administrative-distance
set administrative-distance
To set a route with lower administrative distance such that it is preferred to a route with higher administrative
distance, use the set administrative-distance command in route policy configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples This example shows how to set a route with an administrative value such that it is preferred to a route
with higher administrative distance.
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# route-policy sample
RP/0/RSP0/CPU0:router(config-rpl)# set administrative-distance 34
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
RP/0/RSP0/CPU0:router(config-rpl)# exit
RP/0/RSP0/CPU0:router(config)# route bgp 100
RP/0/RSP0/CPU0:router(config-bgp)# address family ipv4 unicast
RP/0/RSP0/CPU0:router(config-bgp-af)# table-policy sample
RP/0/RSP0/CPU0:router(config-bgp-af)# exit
RP/0/RSP0/CPU0:router(config-bgp)# exit
RP/0/RSP0/CPU0:router(config)# end
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1617
Routing Policy Language Commands
set aigp-metric
set aigp-metric
To set originating prefixes with accumulated interior gateway protocol ( AiGP) attribute information, use
theset aigp-metric command in route-policy configuration mode.
set aig-metric{igp-costvalue}
value Specifies the aigp-metric value. 32- bit decimal number. Range is 0-4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples The following example shows how to set the aigp metric as the igp cost for route-policy aigp_policy:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# route-policy aigp_policy
RP/0/RSP0/CPU0:router(config-rpl)# set aigp-metric igp-cost
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1618
Routing Policy Language Commands
set community
set community
To set the Border Gateway Protocol (BGP) community attributes in a route, use the set community command
in route-policy configuration mode.
inline-community-set Inline community set. The inline community set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set community command to set the BGP community attribute.
Note The set community command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
Communities are 32-bit values carried in BGP routes. Each route may have zero or more communities in an
unordered list.
Use this command to replace the communities in a route or add to them using the optional additive keyword.
As with the other community forms that support inline sets, either or both 16-bit portions of the community
can be parameterized. Likewise, the names of the well-known communities internet (0:0), no-advertise
(65535:65281), no-export (65535:65282), and local-AS (65535:65283) can also be used. In an inline
community set, each 16-bit portion can also be specified as the peeras to express the AS number of the
neighbor from which the route was received. If the neighbor AS employs a 4-byte ASN, the IANA-assigned
16-bit value 23456 (AS_TRANS) is used as peeras instead.
Without the additive keyword, any existing communities (other than the well-known communities) are
removed and replaced with the given communities. The additive keyword specifies that all communities
already present in the route be maintained and the list of communities be added to them.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1619
Routing Policy Language Commands
set community
route-policy read,
write
Examples The following are incomplete configuration examples using the set community command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1620
Routing Policy Language Commands
set core-tree
set core-tree
To set a Multicast Distribution Tree (MDT) type, use the set core-tree command in route-policy configuration
mode.
Syntax Description gre-rosen Specifies the IP GRE Rosen core MDT type
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
In this example, the Multicast Distribution Tree type is set to IP GRE Rosen core:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#route-policy policy_mdt_type
RP/0/RSP0/CPU0:router(config-rpl)#set core-tree gre-rosen
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1621
Routing Policy Language Commands
set dampening
set dampening
To configure Border Gateway Protocol (BGP) route dampening, use the set dampening command in
route-policy configuration mode.
Syntax Description halflife minutes Specifies the time (in minutes) after which a penalty is decreased. After the route
has been assigned a penalty, the penalty is decreased by half after the half-life
period. The process of reducing the penalty happens every 5 seconds. Range is
1 to 45 minutes.
parameter Parameter name. The parameter name must be preceded with a “$.”
max-suppress minutes Specifies the maximum time (in minutes) a route can be suppressed. Range is 1
to 20000. If the half-life value is allowed to default, the maximum suppress time
defaults to 60 minutes.
reuse seconds Unsuppresses a route if the penalty for flapping the route decreases enough to
fall below the configured value (in seconds). The process of unsuppressing routes
occurs at 10-second increments. Range is 1 to 20000.
suppress penalty-units Specifies a penalty of 1000 each time a route flaps. When a route penalty exceeds
the configured limit, it is suppressed. Range is 1 to 20000.
others default If all four keyword values are not specified in the command, then the command
must end with others default . This designation indicates that any keyword not
defined is set to its default.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The BGP protocol supports route dampening using an exponential backoff algorithm. The algorithm is
controlled by setting the four supported BGP values: half-life, max-suppress, reuse, and suppress. Use the
set dampening command to configure BGP route dampening.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1622
Routing Policy Language Commands
set dampening
Note The set dampening command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
A value for at least one of the four keywords must be set. If the set dampening command defines values for
three or fewer of the supported keywords, then the configuration must end with the others default , which
indicates that any keyword value not defined in the command is set to its default value.
The keywords may appear in the command in any order.
route-policy read,
write
Examples In the following examples, the half-life is set to 20 minutes and the maximum suppress time is set
to
90 minutes. Each command must end with others default because three or fewer keywords are
defined.
In this example, all four keywords are defined, which means the command does not use others
default .
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1623
Routing Policy Language Commands
set eigrp-metric
set eigrp-metric
To set Enhanced Interior Gateway Routing Protocol (EIGRP) route metrics, use the set eigrp-metric command
in route-policy configuration mode.
Syntax Description bandwidth Minimum bandwidth of the route in kilobits per second. Range is 1 to 4294967295.
delay Route delay in tens of microseconds. Delay is 1 or any positive number that is a multiple of 39.1
nanoseconds. Range is 1 to 4294967295.
reliability Likelihood of successful packet transmission expressed as a number between 0 and 255. The
value 255 means 100 percent reliability; 0 means no reliability.
loading Effective bandwidth of the route expressed as a number from 1 to 255 (255 is 100 percent loading).
mtu Minimum maximum transmission unit (MTU) size of the route in bytes. Range is from 1 to
65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
You can use the add command to further offset an existing EIGRP metric value.
route-policy read,
write
Examples In the following example, the EIGRP metrics are adjusted for route policy policy_1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1624
Routing Policy Language Commands
set eigrp-metric
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1625
Routing Policy Language Commands
set extcommunity cost
cost-inline-extcommunity-set Inline cost extended community set. The inline cost extended community set
must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set extcommunity cost command to either replace the extended communities on the route or add
to them using the optional additive keyword. Cost community is an extended community used to tie break
the best path selection process in BGP so as to have a localized custom decision for packet forwarding. The
extended community format defines generic points of insertion (POI) that influence the decision at different
points of the bestpath algorithm.
Note The set extcommunity cost command can be used as an action statement within an if statement. For a list
of all action statements available within an if statement, see the if command.
As with the other extended community forms that support inline sets, either or both portions of the community
can be parameterized. Similarly to regular communities, the additive keyword can be used to signify adding
these extended communities to those that are already present, as opposed to replacing them. Without the
additive keyword, any existing extended communities for cost (other than the well-known communities) are
removed and replaced with the given communities. The additive keyword specifies that all extended
communities for cost already present in the route be maintained and the set of extended communities be added
to them. Well-known communities include internet, local-AS, no-advertise, and no-export.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1626
Routing Policy Language Commands
set extcommunity cost
route-policy read,
write
Examples The following are incomplete configuration examples using the set extcommunity cost command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1627
Routing Policy Language Commands
set extcommunity rt
set extcommunity rt
To set the Border Gateway Protocol (BGP) route target (RT) extended community attributes, use the set
extcommunity rt command in route-policy configuration mode.
rt-inline-extcommunity-set Inline route target extended community set. The inline route target extended
community set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set extcommunity rt command to either replace the extended communities on the route or add to
them using the optional additive keyword.
Note The set extcommunity rt command can be used as an action statement within an if statement. For a list of
all action statements available within an if statement, see the if command.
As with the other extended community forms that support inline sets, either or both portions of the community
can be parameterized. Similarly to regular communities, the additive keyword can be used to signify adding
these extended communities to those that are already present, as opposed to replacing them.
route-policy read,
write
Examples The following are incomplete configuration examples using the set extcommunity rt command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1628
Routing Policy Language Commands
set extcommunity rt
Without the additive keyword, any existing extended communities for cost (other than the
well-known communities) are removed and replaced with the given communities. The additive
keyword specifies that all extended communities for cost already present in the route be maintained
and the list of extended communities be added to them.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1629
Routing Policy Language Commands
set ip-precedence
set ip-precedence
To set the IP precedence, use the set ip-precedence command in route-policy configuration mode.
Syntax Description number Value of the precedence. The precedence value can be a number from 0 to 7:
• 7 —network (set packets with network control precedence)
• 6 —internet (set packets with internetwork control precedence)
• 5 —critical (set packets with critical precedence)
• 4 —flash-override (set packets with flash override precedence)
• 3 —flash (set packets with flash precedence)
• 2 —immediate (set packets with immediate precedence)
• 1 —priority (set packets with priority precedence)
• 0 —routine (set packets with routine precedence)
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set ip-precedence command to set the IP precedence to classify packets. This command is supported
at the BGP table-policy attachpoint. Prefixes are marked for subsequent processing in the forwarding plane.
After QoS Policy Propagation through Border Gateway Protocol (BGP) (QPPB) is enabled on an interface,
corresponding traffic shaping and policing is completed using packet classification based on the IP precedence
or QoS group ID. See Modular QoS Configuration Guide for Cisco ASR 9000 Series Routers for information
on QPPB.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1630
Routing Policy Language Commands
set ip-precedence
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1631
Routing Policy Language Commands
set isis-metric
set isis-metric
To set the Intermediate System-to-Intermediate System (IS-IS) metric attribute value, use the set is-is metric
command in route-policy configuration mode.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set isis-metric command to set the IS-IS metric attribute value for routes that are redistributed into
IS-IS.
route-policy read,
write
Examples In the following example, the IS-IS metric attribute value is set to 1000:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1632
Routing Policy Language Commands
set label
set label
To set the Border Gateway Protocol (BGP) label attribute value, use the set label command in route-policy
configuration mode.
Syntax Description explicit-null Sets the label to the well-known explicit value of 0.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set label command in a route policy at the allocate label attachpoint to set the label to explicit-null
or implicit-null based on deployment preference. During inter-AS operation, the ASBR sends some of its own
loopbacks to other its peers and labels them either implicit null or explicit null.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1633
Routing Policy Language Commands
set label-mode
set label-mode
To set the type of Border Gateway Protocol (BGP) label mode, use the set label-mode command in route-policy
configuration mode. This command does not have a no form.
Syntax Description per-ce Specifies that the same label is used for all routes advertised from a unique customer edge (CE)
peer or router.
per-vrf Specifies that the same label is used for all routes advertised from a unique VRF.
per-prefix Specifies that the same label is used for all routes advertised from a unique prefix.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set label-mode command in a route policy at the label-mode attachpoint to set the type of label mode
to per-ce or per-vrf or per-prefix, based on deployment preference.
Per-vrf label mode is not supported for Carrier Supporting Carrier (CSC) network with internal and external
BGP multipath setup.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1634
Routing Policy Language Commands
set label-mode
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1635
Routing Policy Language Commands
set level
set level
To configure the Intermediate System-to-Intermediate System (IS-IS) link-state packet (LSP) level advertised
to redistributed routes, use the set level command in route-policy configuration mode.
Syntax Description level-1 Specifies that redistributed routes are advertised in the Level 1 LSP of the router.
level-2 Specifies that redistributed routes are advertised in the Level 2 LSP of the router.
level-1-2 Specifies that redistributed routes are advertised in Level 1 and Level 2 LSPs of the router.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the IS-IS set level command to configure the LSP level advertised to redistributed routes.
Note The set level command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1636
Routing Policy Language Commands
set local-preference
set local-preference
To set the Border Gateway Protocol (BGP) local preference attribute in a route, use the set local-preference
command in route-policy configuration mode.
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is 0 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set local-preference command to specify a preference value for the autonomous system path. Local
preference is a nontransitive (does not cross autonomous system boundaries) attribute and is the second metric
considered in the BGP best path calculation (the highest local preference is chosen). Weight is the first metric
evaluated for best path, but it is local to the router and propagates only to iBGP peers. See the Implementing
BGP module of the Routing Configuration Guide for Cisco ASR 9000 Series Routers for information on the
BGP best path calculation.
Note The set local-preference command can be used as an action statement within an if statement. For a list of
all action statements available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, the local preference value is set to 10:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1637
Routing Policy Language Commands
set med
set med
To set the Border Gateway Protocol (BGP) Multi Exit Discriminator (MED) attribute, use the set med
command in route-policy configuration mode.
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is 0 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
igp-cost Sets the MED value to the cost for the Interior Gateway Protocol (IGP) route to resolve the
next-hop of the BGP route.
+ | - Sets the MED to the MED plus or minus a static offset. An integer or parameter must follow
the plus or minus.
max-reachable Sets the MED value to the maximum possible value of 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set med command to set the MED value, which is a 32-bit unsigned integer.
Note The set med command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
This command can take the following as argument values: an integer, a parameter, the igp-cost keyword, or
a mathematical operator (either plus or minus) followed by an integer or a parameter. Setting the MED to the
IGP cost is supported on outbound BGP policies only. The MED cannot be set to the IGP cost in policies
applied to other BGP attach points.
The max-reachable keyword sets the MED to the maximum value while leaving the route reachable.
The plus or minus variants allow the user to set the MED to the MED plus or minus a static offset. The variants
that allow a user to add or subtract offsets to the MED value are also range checked for underflow or overflow.
If the value underflows as a result of subtraction, then the MED value is set to zero. If the value overflows,
the value is set to 4294967295, which is the maximum value for MED. when MED is set to 4294967295, the
route is unreachable.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1638
Routing Policy Language Commands
set med
route-policy read,
write
Examples The following two examples show how to set the MED to a value that is either specified directly
(using the integer 156) or passed to the policy as a parameter:
The following example shows how to instruct BGP to automatically set the MED value to the cost
of the IGP route that resolves the next-hop of the BGP route:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1639
Routing Policy Language Commands
set metric-type (IS-IS)
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the IS-IS set metric-type command to control whether IS-IS treats the metric as an internal or external
metric.
Note The set metric-type command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, the IS-IS metric type is set to internal:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1640
Routing Policy Language Commands
set metric-type (OSPF)
Syntax Description type-1 Uses the cost set on the route plus the topology-related costs in the calculation for Type 1 metrics.
type-2 Uses only the cost set on the route in the calculation for Type 2 metrics.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the OSPF set metric-type command to control whether OSPF treats the cost as a Type 1 or Type 2
metric.
Note The set metric-type command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
The value of Type 1 or Type 2 controls how OSPF computes the cost for this route. For Type 2 metrics, only
the cost set on the route is used. For Type 1 metrics, the cost set on the route plus the topology- related costs
are used in the calculation.
This command does not support parameterization.
route-policy read,
write
Examples In the following example, the OSPF metric type is set to Type 1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1641
Routing Policy Language Commands
set next-hop
set next-hop
To replace the next-hop associated with a given route, use the set next-hop command in route-policy
configuration mode.
destination-vrf (Optional) Specifies that the next-hop of the route should be resolved in destination VRF
context. This keyword is available when an IPv4 or IPv6 address or parameter is used.
parameter Parameter name. The parameter name must be preceded with a “$.”
peer-address Sets the next-hop to the IP address of the remote Border Gateway Protocol (BGP) peer.
Usage Guidelines Use the set next-hop command to replace the next-hop associated with a specific address.
Note The set next-hop command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
Use the set next-hop peer-address command to set the next-hop to the address of the BGP neighbor, where
this policy is attached.
The next-hop is a valid IPv4 address entered as a dotted decimal or an IPv6 address entered as a colon-separated
hexadecimal.
It is not possible to use this command to set the BGP IPv6 link-local next-hop.
The destination-vrf keyword is used mainly in Layer 3 VPN networks when importing routes.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1642
Routing Policy Language Commands
set next-hop
The set next-hop discard configuration is used in the neighbor inbound policy. When this config is applied
to a path, the primary next-hop is still be associated with the actual path but the RIB is updated with next-hop
set to Null0. Even if the primary received nexthop is unreachable, the Remotely Triggered Blackhole (RTBH)
path will be considered reachable and will be a candidate in the bestpath selection process. The RTBH path
is readvertised to other peers with either the received next-hop or nexthop-self based on normal BGP
advertisement rules.
route-policy read,
write
Examples In the following example, the next-hop is set to a valid IPv4 address:
In this example, the next-hop is set to a valid IPv4 address with a destination VRF context:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1643
Routing Policy Language Commands
set origin
set origin
To change the Border Gateway Protocol (BGP) origin attribute, use the set origin command in route-policy
configuration mode.
Syntax Description igp Sets the origin type to Interior Gateway Protocol (IGP).
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set origin command to change the origin attribute.
Note The set origin command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
The origin of a Border Gateway Protocol (BGP) route is igp , egp , or incomplete .
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1644
Routing Policy Language Commands
set ospf-metric
set ospf-metric
To set an Open Shortest Path First (OSPF) protocol metric attribute value, use the set ospf-metric command
in route-policy configuration mode.
Syntax Description number Value assigned to a 24-bit unsigned integer. Range is 0 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set ospf-metric command to set the metric for routes that are redistributed into OSPF. The OSPF
metric operator accepts either an integer value or a parameter.
route-policy read,
write
Examples In the following example, the OSPF metric attribute value is set to 1000:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1645
Routing Policy Language Commands
set path-selection
set path-selection
Sets Border Gateway Protocol (BGP) path selection criteria.
To set path selection criteria and install or advertise the path for the Border Gateway Protocol, use the set
path-selection command in route-policy configuration mode.
number Specifies the BGP backup path number, which must be a value of 1.
Usage Guidelines This command is used with the additional-path selection command within an appropriate route-policy to
calculate backup paths and to enable Prefix Independent Convergence (PIC) functionality. See the BGP Prefix
Independent Convergence Unipath Primary/Backup section in Routing Configuration Guide for Cisco ASR
9000 Series Routers for details on the PIC functionality.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1646
Routing Policy Language Commands
set path-selection
The group-best is the set of paths that are the best paths from the paths of the same autonomous system (AS).
All the paths that are selected as the group-best set should be advertised to peers, however, if there are multiple
paths that are selected as group-best because they come from different ASs but having the same next-hop the
XR router advertises only one path from these paths to the peer device.
To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Examples The following example shows how to set the backup path for a route-policy:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# route-policy path_selection_policy
RP/0/RSP0/CPU0:router(config-rpl)# set path-selection backup 1 advertise
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1647
Routing Policy Language Commands
set qos-group (RPL)
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set qos-group command to set the QoS group to classify packets.
This command is supported at the BGP table-policy attachpoint. Prefixes are marked for subsequent processing
in the forwarding plane. After QoS Policy Propagation through Border Gateway Protocol (BGP) (QPPB) is
enabled on an interface, corresponding traffic shaping and policing is completed using packet classification
based on the IP precedence or QoS group ID. See the Modular QoS Configuration Guide for Cisco ASR 9000
Series Routers for information on QPPB.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1648
Routing Policy Language Commands
set rib-metric
set rib-metric
To set the Routing Information Base (RIB) metric attribute value for a table policy, use the set rib-metric
command in route-policy configuration mode:
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is 0 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set rib-metric command set the RIB metric attribute value for BGP routes.
Every route in the RIB has a metric associated with it, signifying the cost to reach a specific destination based
on link characteristics. The set rib-metric command modifies the RIB metric while installing BGP routes
into RIB, enabling the upgrading or downgrading of the BGP route installed in RIB.
route-policy read,
write
Examples In the following example, the RIB metric attribute is set to 1000:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1649
Routing Policy Language Commands
set rip-metric
set rip-metric
To set Routing Information Protocol (RIP) metric attributes, use the set rip-metric command in route-policy
configuration mode.
Syntax Description number Value assigned to a 4-bit unsigned integer. Range is from 0 to 16.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set rip-metric command to set the cost attribute for routes that are redistributed into RIP.
You can use the add command to increment the RIP metric value.
route-policy read,
write
Examples In the following example, the RIP metric number is adjusted for route policy policy_1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1650
Routing Policy Language Commands
set rip-tag
set rip-tag
To set a route tag attribute for Routing Information Protocol (RIP) routes, use the set rip-tag command in
route-policy configuration mode.
Syntax Description number Value assigned to a 16-bit unsigned integer. Range is from 0 to 65535.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set rip-tag command to set the RIP tag attribute for routes that are redistributed into RIP. The RIP
tag operator accepts either an integer value or a parameter.
route-policy read,
write
Examples In the following example, the RIP tag is adjusted for route policy policy_1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1651
Routing Policy Language Commands
set rpf-topology
set rpf-topology
To set reverse-path forwarding (RPF) to any default or nondefault tables for particular sources and groups,
use the set rpf-topology command in routing policy configuration mode.
set rpf-topology [vrf vrf-name] {ipv4 | ipv6} {unicast | multicastparameter} topology table-name
parameter Parameter name. The parameter name must be preceded with a “$.”
topology Specifies the default or non-default topology table for the source or group.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
multicast read
Examples The following example shows how to execute the set rpf-topology command:
RP/0/RSP0/CPU0:router# config
RP/0/RSP0/CPU0:router(config)# route-policy green
RP/0/RSP0/CPU0:router(config-rpl)# set rpf-topology ipv6 multicast topology t12
The following example shows the use of set rpf-topology command in the context of creating an
RPF for a topology table in multiple topologies:
route-policy mt4-p1
if destination in (225.0.0.1, 225.0.0.11) then
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1652
Routing Policy Language Commands
set rpf-topology
route-policy mt4-p3
if destination in (225.0.0.8) then
set rpf-topology ipv4 multicast topology t208
elseif destination in (225.0.0.9) then
set rpf-topology ipv4 multicast topology t209
elseif destination in (225.0.0.10) then
set rpf-topology ipv4 multicast topology t210
else
drop
endif
end-policy
!
rpf Assigns a route policy in PIM to select a reverse-path forwarding (RPF) topology.
topology
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1653
Routing Policy Language Commands
set rtset route-limit
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
route-policy read
Examples Based on service agreement, if a user AVPN advertises VPN prefixes with RT-set {1:1, 2:2} and
user Team10 advertises VPN prefixes with RTs {3:3, 4:4}. On the DUT, the user wants to limit
AVPN prefixes to 100, Team10 prefixes to 50, and for all other users, limit each of their prefixes to
80. Note that the fallback limit is per user, not a cumulative one. To achieve this, the user must
configure the following route-policy:
route-policy RTSET-LIMIT
if extcommunity rt matches-every (1:1, 2:2) then
set rtset-route-limit 100
elseif extcommunity rt matches-every (3:3, 4:4) then
set reset-route-limit 50
else
set reset-route-limit 80
endif
end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1654
Routing Policy Language Commands
set spf-priority
set spf-priority
To set OSPF Shortest Path First (SPF) priority, use the set spf-priority command in route-policy configuration
mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#route-policy policy_spf_priority
RP/0/RSP0/CPU0:router(config-rpl)#set spf-priority critical
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1655
Routing Policy Language Commands
set tag
set tag
To set the tag attribute, use the set tag command in route-policy configuration mode.
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is from 0 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set tag command to set the tag attribute.
Note The set tag command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
Tags are routing-protocol independent 32-bit integers that can be associated with a given route in the Routing
Information Base (RIB).
For the Border Gateway Protocol (BGP), the tag attribute can be set only at the table-policy attach point.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1656
Routing Policy Language Commands
set traffic-index
set traffic-index
To set the traffic index attribute, use the set traffic-index command in route-policy configuration mode.
Syntax Description number Integer value assigned to the traffic index attribute. Range is 1 to 63.
parameter Parameter name. The parameter name must be preceded with a “$.”
ignore Specifies that Border Gateway Protocol (BGP) policy accounting is not done.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set traffic-index command to set the traffic index attribute.
Note The set traffic-index command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
Traffic index is a special attribute for BGP. It is used as an index to a set of counters that are maintained by
forwarding hardware. It is also used to track packet and byte counters that are forwarded using routes with
specific attributes. These counters can be enabled and disabled on an individual interface basis.
The traffic index attribute can be set only at the table-policy attach point, and can take a value from 1 to 63,
or a value of ignore . If the traffic index is set to ignore , then BGP policy accounting is not done.
Parameterization of this value is also supported.
route-policy read,
write
Examples In the following example, a policy is created in which the traffic index is set to 10 for all routes that
originated in autonomous system 1234:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1657
Routing Policy Language Commands
set traffic-index
This policy could then be attached using the BGP table-policy command. The counters could then
be enabled on various interfaces with the appropriate commands.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1658
Routing Policy Language Commands
set vpn-distinguisher
set vpn-distinguisher
To change the Border Gateway Protocol (BGP) VPN distinguisher attribute, use the set vpn-distinguisher
command in route-policy configuration mode.
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is from 1 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set vpn-distinguisher command to change the VPN distinguisher attribute.
Note The set origin command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
A VPN distinguisher is used in Layer 3 VPN networks for enhanced individual VPN control and to avoid
route target mapping at AS boundaries in inter-AS VPN networks. Route target extended communities are
removed at neighbor outbound, and the VPN distinguisher value is applied on the BGP route as an extended
community. When the route is received on a neighboring router in another AS, the VPN distinguisher is
removed and mapped to a route target extended community.
route-policy read,
write
Examples In the following example, the VPN distinguisher attribute is set to 456:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1659
Routing Policy Language Commands
set weight
set weight
To set the weight value for Border Gateway Protocol (BGP) routes, use the set weight command in
route-policy configuration mode.
Syntax Description number Number assigned to the weight value for BGP routes. Weight is 16 bits. Range is 0 to 65535.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the set weight command to set the weight value for BGP routes.
Note The set weight command can be used as an action statement within an if statement. For a list of all action
statements available within an if statement, see the if command.
A weight is a value that can be applied to a route to override the BGP local preference. This is not a BGP
attribute announced to BGP peer routers. RPL can be used to set the weight value.
Given two BGP routes with the same network layer reachability information (NLRI), a route with a higher
weight is selected, no matter what the values of other BGP attributes may be. However, weight only has
significance on the local router. It is not sent from one BGP speaker to another, even within the same
autonomous system.
On Cisco routers, if a BGP route is sourced by the local router, its weight is automatically set to 32768; if the
BGP route is learned from another router, its weight is automatically set to 0. Thus, by default, locally sourced
routes are preferred over BGP learned routes.
route-policy read,
write
Examples In the following example, the weight of the route is set to 10 and then to a parameter value
$weight_param:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1660
Routing Policy Language Commands
set weight
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1661
Routing Policy Language Commands
show rpl
show rpl
To display system-wide RPL configuration, use the show rpl command in EXEC mode.
maximum (Optional) Displays the maximum number of lines of configuration and number
of policies.
lines configuration-limit (Optional) Displays the number of lines to which configuration is limited. Range
is 1 to 131072.
The configuration-limit argument is available if the running-config keyword
is specified.
policies policies-limit (Optional) Displays the limit on the number of policies. Range is 1 to 5000.
The configuration-limit argument is available if the running-config keyword
is specified.
editor (Optional) Specifies the default RPL editor. This keyword is available if the
running-config keyword is specified.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
route-policy read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1662
Routing Policy Language Commands
show rpl
Examples The following shows the output of the show running-config rpl command:
extcommunity-set rt ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any com_set_exl) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
show rpl maximum, on page 1714 Displays the maximum limits for lines of configuration and number of
policies.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1663
Routing Policy Language Commands
show rpl active as-path-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for active AS path sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl active as-path-set command to display all AS path sets that are in use in the system and
referenced either directly or indirectly at a policy attach point.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
RP/0/RSP0/CPU0:router# show rpl route-policy policy_2 detail
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1664
Routing Policy Language Commands
show rpl active as-path-set
end-set
!
community-set comm_set_ex1
65500:1,
65500:2,
65500:3
end-set
!
extcommunity-set rt ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
as-path-set as_path_set_ex1
ios-regex '^_655--$',
ios-regex '^_65501_$'
end-set
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
Given this sample configuration, the show rpl active as-path-set command displays the following
information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1665
Routing Policy Language Commands
show rpl active as-path-set
show rpl active community-set, on page Displays the community sets that are referenced by at least one
1667 policy that is being used at an attach point.
show rpl active extcommunity-set, on Displays the extended community sets that are referenced by at
page 1670 least one policy that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the route policies that are referenced by at least one
policy that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the prefix sets that are referenced by at least one policy
that is being used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1666
Routing Policy Language Commands
show rpl active community-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for active community sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl active community-set command to display all community sets that are in use in the system
and referenced either directly or indirectly at a policy attach point.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1667
Routing Policy Language Commands
show rpl active community-set
0.0.0.0/0
end-set
!
community-set comm_set_ex1
65500:1,
65500:2,
65500:3
end-set
!
extcommunity-set rt ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
as-path-set as_path_set_ex1
ios-regex '^_655--$',
ios-regex '^_65501_$'
end-set
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
Given this sample configuration, the show rpl active community-set command displays the
following information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1668
Routing Policy Language Commands
show rpl active community-set
show rpl active as-path-set, on page 1664 Displays the AS path sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active extcommunity-set, on Displays the extended community sets that are referenced by at
page 1670 least one policy that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the route policies that are referenced by at least one policy
that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the prefix sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active rd-set, on page 1676 Displays the route distinguisher sets that are referenced by at least
one policy that is being used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1669
Routing Policy Language Commands
show rpl active extcommunity-set
Syntax Description cost (Optional) Displays all extended community cost sets.
detail (Optional) Displays the content of the object and all referenced objects for active extended community
sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl active extcommunity-set command to display all extended community sets that are in
use in the system and referenced either directly or indirectly at a policy attach point.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1670
Routing Policy Language Commands
show rpl active extcommunity-set
route-policy policy_2 in
!
!
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
community-set comm_set_ex1
65500:1,
65500:2,
65500:3
end-set
!
extcommunity-set rt ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
as-path-set as_path_set_ex1
ios-regex '^_655--$',
ios-regex '^_65501_$'
end-set
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
Given this sample configuration, the show rpl active extcommunity-set command displays the
following information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1671
Routing Policy Language Commands
show rpl active extcommunity-set
show rpl active as-path-set, on page 1664 Displays the AS path sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active community-set, on page Displays the community sets that are referenced by at least one
1667 policy that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the route policies that are referenced by at least one policy
that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the prefix sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active rd-set, on page 1676 Displays the route distinguisher sets that are referenced by at least
one policy that is being used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1672
Routing Policy Language Commands
show rpl active prefix-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for active prefix sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl active prefix-set command to display all prefix sets that are in use in the system and
referenced either directly or indirectly at a policy attach point.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1673
Routing Policy Language Commands
show rpl active prefix-set
0.0.0.0/0
end-set
!
community-set comm_set_ex1
65500:1,
65500:2,
65500:3
end-set
!
extcommunity-set rt ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
as-path-set as_path_set_ex1
ios-regex '^_655--$',
ios-regex '^_65501_$'
end-set
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1674
Routing Policy Language Commands
show rpl active prefix-set
show rpl active as-path-set, on page 1664 Displays the AS path sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active community-set, on page Displays the community sets that are referenced by at least one
1667 policy that is being used at an attach point.
show rpl active extcommunity-set, on Displays the extended community sets that are referenced by at
page 1670 least one policy that is being used at an attach point.
show rpl route-policy attachpoints, on Displays the route policies that are referenced by at least one
page 1734 policy that is being used at an attach point.
show rpl active rd-set, on page 1676 Displays the route distinguisher sets that are referenced by at least
one policy that is being used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1675
Routing Policy Language Commands
show rpl active rd-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for active route policies.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl active rd-set command to display all RD sets that are in use in the system and that are
referenced either directly or indirectly at a policy attach point.
route-policy read
rd-set rdset1
10:151,
100.100.100.1:153,
100.100.100.62/31:63
end-set
!
rd-set rdset2
10:152,
100.100.100.1:154,
100.100.100.62/31:89
end-set
!
route-policy rdsetmatch
if rd in rdset1 then
set community (10:112)
elseif rd in rdset2 then
set community (10:223)
endif
end-policy
!
router bgp 10
bgp router-id 10.0.0.1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1676
Routing Policy Language Commands
show rpl active rd-set
Given this sample configuration, the show rpl active rd-set command displays the following
information:
ACTIVE -- Referenced by at least one policy which is attached INACTIVE -- Only referenced
by policies which are not attached UNUSED -- Not attached (directly or indirectly) and not
referenced
show rpl active as-path-set, on page 1664 Displays the AS path sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active community-set, on page Displays the community sets that are referenced by at least one
1667 policy that is being used at an attach point.
show rpl active extcommunity-set, on Displays the extended community sets that are referenced by at
page 1670 least one policy that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the prefix sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the route policies that are referenced by at least one
policy that is being used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1677
Routing Policy Language Commands
show rpl active route-policy
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for active route policies.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl active route-policy command to display all policies that are in use in the system and that
are referenced either directly or indirectly at a policy attach point.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1678
Routing Policy Language Commands
show rpl active route-policy
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
RP/0/RSP0/CPU0:router# show rpl route-policy policy_2
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
Given this sample configuration, the show rpl active route-policy command displays the following
information:
show rpl active as-path-set, on page 1664 Displays the AS path sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active community-set, on page Displays the community sets that are referenced by at least one
1667 policy that is being used at an attach point.
show rpl active extcommunity-set, on Displays the extended community sets that are referenced by at
page 1670 least one policy that is being used at an attach point.
show rpl active prefix-set, on page 1673 Displays the prefix sets that are referenced by at least one policy
that is being used at an attach point.
show rpl active rd-set, on page 1676 Displays the route distinguisher sets that are referenced by at least
one policy that is being used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1679
Routing Policy Language Commands
show rpl as-path-set
brief (Optional) Limits the display to a list of the names of all AS path sets without their configurations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the optional brief keyword to limit the display to a list of the names of all AS path sets without their
configurations.
route-policy read
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
Given this sample configuration, the show rpl as-path-set as_path_set_ex1 command displays
the following information:
as-path-set as_path_set_ex1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1680
Routing Policy Language Commands
show rpl as-path-set
ios-regex '^_65500_$',
ios-regex '^_65501_$'
end-set
show rpl community-set, on page 1687 Displays the configuration of a named community set.
show rpl extcommunity-set, on page 1694 Displays the configuration of a named extended community set.
show rpl route-policy, on page 1731 Displays the configuration of a named route policy.
show rpl prefix-set, on page 1718 Displays the configuration of a named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1681
Routing Policy Language Commands
show rpl as-path-set attachpoints
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl as-path-set attachpoints command to display all policies used at an attach point that
reference the named set either directly or indirectly.
The AS path set name is required.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy policy_1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1682
Routing Policy Language Commands
show rpl as-path-set attachpoints
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
Given this sample configuration, the show rpl as-path-set as_path_set_ex1 attachpoints command
displays the following information:
BGP Attachpoint:Neighbor
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1683
Routing Policy Language Commands
show rpl as-path-set attachpoints
show rpl community-set attachpoints, on page Displays all the policies used at an attach point that reference
1689 the named community set.
show rpl route-policy attachpoints, on page Displays all the policies used at an attach point that reference
1734 the named policy.
show rpl prefix-set attachpoints, on page 1720 Displays all the policies used at an attach point that reference
the named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1684
Routing Policy Language Commands
show rpl as-path-set references
brief (Optional) Limits the output to just the brief table and not the detailed information for the named
AS path set.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl as-path-set references command to display all policies that reference the named AS path
set either directly or indirectly.
Use the optional brief keyword to limit the output to just a summary table and not the detailed information
for the AS path set.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
RP/0/RSP0/CPU0:router# show rpl route-policy policy_1
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1685
Routing Policy Language Commands
show rpl as-path-set references
Given this sample configuration, the show rpl as-path-set as_path_set_ex1 references command
displays the following information:
Usage/Status count
--------------------------------------------------------------
Direct 1
Indirect 0
ACTIVE 1
INACTIVE 0
UNUSED 0
Field Description
Usage/Status Displays the usage and status of all policies that reference the AS path set.
Values for usage are Direct or Indirect.
Values for policy status are ACTIVE, INACTIVE, or UNUSED.
count Number of policies that match each usage and status option.
route-policy Name of the route policies that reference the AS path set.
show rpl community-set references, on page 1691 Lists all policies that reference the named community set.
show rpl route-policy references, on page 1739 Lists all policies that reference the named policy.
show rpl prefix-set references, on page 1723 Lists all policies that reference the named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1686
Routing Policy Language Commands
show rpl community-set
brief (Optional) Limits the display to a list of the names of all community sets without their configurations.
Release 5.3.2 The command output was modified to display graceful maintenance feature information.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the optional brief keyword to limit the display to a list of the names of community sets without their
configurations.
route-policy read
The following is the sample output of the show rpl community-set command with graceful maintenance
feature attributes displayed:
RP/0/0/CPU0:R5#show rpl community-set
Thu Jan 29 17:55:04.792 PST
Listing for all Community Set objects
community-set gshut
graceful-shutdown
end-set
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1687
Routing Policy Language Commands
show rpl community-set
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
Given this sample configuration, the show rpl community-set comm_set_ex2 command displays
the following information:
community-set comm_set_ex2
65501:1,
65501:2,
65501:3
end-set
show rpl as-path-set, on page 1680 Displays the configuration of a named AS path set.
show rpl extcommunity-set, on page 1694 Displays the configuration of a named extended community set.
show rpl prefix-set, on page 1718 Displays the configuration of a named prefix set.
show rpl rd-set, on page 1725 Displays the configuration of a named RD set.
show rpl route-policy, on page 1731 Displays the configuration of a named route policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1688
Routing Policy Language Commands
show rpl community-set attachpoints
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl community-set attachpoints command to display all the policies used at an attach point
that reference the named community set either directly or indirectly.
The community set name is required.
route-policy read
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1689
Routing Policy Language Commands
show rpl community-set attachpoints
Given this sample configuration, the show rpl community-set attachpoints command displays
the following information:
BGP Attachpoint:Neighbor
Field Description
show rpl as-path-set attachpoints, on page 1682 Displays all the policies used at an attach point that reference
the named AS path set.
show rpl prefix-set attachpoints, on page 1720 Displays all the policies used at an attach point that reference
the named prefix set.
show rpl rd-set attachpoints, on page 1727 Displays all the policies used at an attach point that reference
the named RD set.
show rpl route-policy attachpoints, on page Displays all the policies used at an attach point that reference
1734 the named policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1690
Routing Policy Language Commands
show rpl community-set references
brief (Optional) Limits the output to just the summary table and not the detailed information for the
community set.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl community-set references command to display all the policies that reference the named
community set.
Use the optional brief keyword to limit the output to just a summary table and not the detailed information
for the community set.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1691
Routing Policy Language Commands
show rpl community-set references
Given this sample configuration, the show rpl extcommunity-set comm_set_ex1 references
command displays the following information:
Usage/Status count
--------------------------------------------------------------
Direct 1
Indirect 0
ACTIVE 1
INACTIVE 0
UNUSED 0
Field Description
Usage/Status Displays the usage and status of all policies that reference the community set.
Values for usage are Direct or Indirect.
Values for status are ACTIVE, INACTIVE, and UNUSED.
count Number of policies that match each usage and status option.
route-policy Name of the route policies that reference the community set.
show rpl as-path-set references, on page 1685 Lists all policies that reference the named AS path set.
show rpl prefix-set references, on page 1723 Lists all policies that reference the named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1692
Routing Policy Language Commands
show rpl community-set references
Command Description
show rpl rd-set references, on page 1729 Lists all policies that reference the named RD set.
show rpl route-policy references, on page 1739 Lists all policies that reference the named policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1693
Routing Policy Language Commands
show rpl extcommunity-set
show rpl extcommunity-set [name [{attachpoints | references}]] [{cost | rt | soo}] [name] [brief]
[states]
attachpoints (Optional) Displays all attach points for this community set.
references (Optional) Displays all policies that use this community set.
brief (Optional) Limits the display to a list of the names of all extended community sets without
their configurations.
Command Default If an attachpoint or reference is not specified, all configured extended community sets are displayed
If a cost, RT, or SoO sets is not specified, all configured extended community sets are displayed
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the optional brief keyword to limit the display to a list of the names of extended community sets without
their configurations.
route-policy read
Examples In the following example, the configuration of an extended community is displayed for the RT
community set named ext_comm_set_rt_ex1:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1694
Routing Policy Language Commands
show rpl extcommunity-set
ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
In the following example, the configuration of an extended community is displayed with all RT set
objects:
extcommunity-set rt extrt1
66:60001
end-set
!
extcommunity-set rt rtset1
10:615,
10:6150,
15.15.15.15:15
end-set
!
extcommunity-set rt rtset3
11:11,
11.1.1.1:3
end-set
!
extcommunity-set rt extsoo1
66:70001
end-set
!
extcommunity-set rt rtsetl1
100:121,
100:122,
100:123,
100:124,
100:125,
100:126,
100:127,
100:128,
7.7.7.7:21
end-set
!
In the following example, the configuration of an extended community is displayed with all cost set
objects:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1695
Routing Policy Language Commands
show rpl extcommunity-set
IGP:94:918,
Pre-Bestpath:95:919
end-set
!
In the following example, the configuration of an extended community is displayed with all SoO set
objects:
show rpl as-path-set, on page 1680 Displays the configuration of a named AS path set.
show rpl community-set, on page 1687 Displays the configuration of a named community set.
show rpl prefix-set, on page 1718 Displays the configuration of a named prefix set.
show rpl rd-set, on page 1725 Displays the configuration of a named RD set.
show rpl route-policy, on page 1731 Displays the configuration of a named route policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1696
Routing Policy Language Commands
show rpl inactive as-path-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for inactive AS path sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl inactive as-path-set command to display all AS path sets that are not in use at an attach
point either directly or indirectly but are referenced by at least one policy in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy sample
if (destination in sample) then
drop
endif
end-policy
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1697
Routing Policy Language Commands
show rpl inactive as-path-set
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample1
apply policy_3
end-policy
Given this sample configuration, the show rpl inactive as-path-set command displays the following
information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1698
Routing Policy Language Commands
show rpl inactive as-path-set
show rpl inactive community-set, on page Displays the community sets that are referenced by a policy but
1700 not in any policy that is used at an attach point.
show rpl inactive extcommunity-set, on Displays the extended community sets that are referenced by a
page 1703 policy but not in any policy that is used at an attach point.
show rpl inactive prefix-set, on page 1706 Displays the prefix sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive rd-set, on page 1709 Displays the RD sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive route-policy, on page Displays the route policies that are referenced by a policy but not
1711 in any policy that is used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1699
Routing Policy Language Commands
show rpl inactive community-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for inactive community sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl inactive community-set command to display all community sets that are not in use at an
attach point either directly or indirectly but are referenced by at least one policy in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy sample2
if (destination in sample2) then
drop
endif
end-policy
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1700
Routing Policy Language Commands
show rpl inactive community-set
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample2
apply policy_3
end-policy
Given this sample configuration, the show rpl inactive community-set command displays the
following information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1701
Routing Policy Language Commands
show rpl inactive community-set
show rpl inactive as-path-set, on page 1697 Displays the AS path sets that are referenced by a policy but not
in any policy that is used at an attach point.
show rpl inactive extcommunity-set, on Displays the extended community sets that are referenced by a
page 1703 policy but not in any policy that is used at an attach point.
show rpl inactive prefix-set, on page 1706 Displays the prefix sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive rd-set, on page 1709 Displays the RD sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive route-policy, on page Displays the route policies that are referenced by a policy but not
1711 in any policy that is used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1702
Routing Policy Language Commands
show rpl inactive extcommunity-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for inactive extended community
sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl inactive extcommunity-set command to display all extended community sets that are not
in use at an attach point either directly or indirectly but are referenced by at least one policy in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy sample3
if (destination in sample3) then
drop
endif
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1703
Routing Policy Language Commands
show rpl inactive extcommunity-set
end-policy
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample3
apply policy_3
end-policy
Given this sample configuration, the show rpl inactive extcommunity-set command displays the
following information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1704
Routing Policy Language Commands
show rpl inactive extcommunity-set
show rpl inactive as-path-set, on page 1697 Displays the AS path sets that are referenced by a policy but not
in any policy that is used at an attach point.
show rpl inactive community-set, on page Displays the community sets that are referenced by a policy but
1700 not in any policy that is used at an attach point.
show rpl inactive prefix-set, on page 1706 Displays the prefix sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive rd-set, on page 1709 Displays the RD sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive route-policy, on page Displays the route policies that are referenced by a policy but not
1711 in any policy that is used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1705
Routing Policy Language Commands
show rpl inactive prefix-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for inactive prefix sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl inactive prefix-set command to display all prefix sets that are not in use at an attach point
either directly or indirectly but are referenced by at least one policy in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy sample4
if (destination in sample4) then
drop
endif
end-policy
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1706
Routing Policy Language Commands
show rpl inactive prefix-set
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample4
apply policy_3
end-policy
Given this sample configuration, the show rpl inactive prefix-set command displays the following
information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1707
Routing Policy Language Commands
show rpl inactive prefix-set
show rpl inactive as-path-set, on page 1697 Displays the AS path sets that are referenced by a policy but not
in any policy that is used at an attach point.
show rpl inactive community-set, on page Displays the community sets that are referenced by a policy but
1700 not in any policy that is used at an attach point.
show rpl inactive extcommunity-set, on Displays the extended community sets that are referenced by a
page 1703 policy but not in any policy that is used at an attach point.
show rpl inactive route-policy, on page Displays the route policies that are referenced by a policy but not
1711 in any policy that is used at an attach point.
show rpl inactive rd-set, on page 1709 Displays the RD sets that are referenced by a policy but not in
any policy that is used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1708
Routing Policy Language Commands
show rpl inactive rd-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for inactive RD sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl inactive rd-set command to display all RD sets that are not in use at an attach point either
directly or indirectly but are referenced by at least one policy in the system.
route-policy read
rd-set rdset1
10:151,
100.100.100.1:153,
100.100.100.62/31:63
end-set
!
rd-set rdset2
10:152,
100.100.100.1:154,
100.100.100.62/31:89
end-set
!
Given this sample configuration, the show rpl inactive rd-set command displays the following
information:
ACTIVE -- Referenced by at least one policy which is attached INACTIVE -- Only referenced
by policies which are not attached UNUSED -- Not attached (directly or indirectly) and not
referenced
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1709
Routing Policy Language Commands
show rpl inactive rd-set
show rpl inactive as-path-set, on page 1697 Displays the AS path sets that are referenced by a policy but not
in any policy that is used at an attach point.
show rpl inactive community-set, on page Displays the community sets that are referenced by a policy but
1700 not in any policy that is used at an attach point.
show rpl inactive extcommunity-set, on Displays the extended community sets that are referenced by a
page 1703 policy but not in any policy that is used at an attach point.
show rpl inactive prefix-set, on page 1706 Displays the prefix sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive route-policy, on page Displays the route policies that are referenced by a policy but not
1711 in any policy that is used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1710
Routing Policy Language Commands
show rpl inactive route-policy
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for inactive route policies.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl inactive route-policy command to display all policies that are not in use at an attach point
either directly or indirectly but are referenced by at least one other policy in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy sample3
if (destination in sample3) then
drop
endif
end-policy
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1711
Routing Policy Language Commands
show rpl inactive route-policy
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if destination in prefix_set_ex1 then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample3
apply policy_3
end-policy
Given this sample configuration, the show rpl inactive route-policy command displays the following
information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1712
Routing Policy Language Commands
show rpl inactive route-policy
show rpl inactive as-path-set, on page 1697 Displays the AS path sets that are referenced by a policy but not
in any policy that is used at an attach point.
show rpl inactive community-set, on page Displays the community sets that are referenced by a policy but
1700 not in any policy that is used at an attach point.
show rpl inactive extcommunity-set, on Displays the extended community sets that are referenced by a
page 1703 policy but not in any policy that is used at an attach point.
show rpl inactive prefix-set, on page 1706 Displays the prefix sets that are referenced by a policy but not in
any policy that is used at an attach point.
show rpl inactive rd-set, on page 1709 Displays the RD sets that are referenced by a policy but not in
any policy that is used at an attach point.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1713
Routing Policy Language Commands
show rpl maximum
Syntax Description lines (Optional) Displays the number of lines of configuration limit.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl maximum command to display the current total, current limit, and maximum limit for
lines of configuration and policies.
Use the optional lines keyword to limit the display to the number of lines of configuration limits. Use the
optional policies keyword to limit the display to the number of policies limits.
route-policy read
Examples The following example shows sample output from the show rpl maximum command:
Table 178: show rpl maximum Field Descriptions, on page 1715 describes the significant fields shown
in the display.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1714
Routing Policy Language Commands
show rpl maximum
Field Description
Lines of configuration Displays the current total, current limit, and maximum limit of lines for the
policy.
Policies Displays the current total, current limit, and maximum limit of policies.
Compiled policies size (kB) Displays the current compiled total for policies in kilobytes.
rpl maximum, on page 1614 Configures the maximum number of lines of configuration and number of policies.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1715
Routing Policy Language Commands
show rpl policy-global references
Syntax Description brief (Optional) Limits the display to a list of the policy names.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
route-policy read
policy-global
infinity '16'
end-global
!
route-policy set-rip-unreachable
set rip-metric $infinity
end-policy
!
Given this sample configuration, the show rpl policy-global references command displays the
following information:
Usage Direct -- Reference occurs in this policy Usage Indirect -- Reference occurs via an
apply statement
Status UNUSED -- Policy is not in use at an attachpoint (unattached) Status ACTIVE -- Policy
is actively used at an attachpoint Status INACTIVE -- Policy is applied by an unattached
policy
Usage/Status count
--------------------------------------------------------------
Direct 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1716
Routing Policy Language Commands
show rpl policy-global references
Indirect 0
ACTIVE 0
INACTIVE 0
UNUSED 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1717
Routing Policy Language Commands
show rpl prefix-set
brief (Optional) Limits the display to a list of the names of all extended community sets without their
configurations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Because sets cannot hierarchically reference other sets or policies, no detail keyword exists as with the
show rpl policy command.
route-policy read
Examples In the following example, the configuration of prefix set pset1 is displayed:
show rpl as-path-set, on page 1680 Displays the configuration of a named AS path set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1718
Routing Policy Language Commands
show rpl prefix-set
Command Description
show rpl community-set, on page 1687 Displays the configuration of a named community set.
show rpl extcommunity-set, on page 1694 Displays the configuration of a named extended community set.
show rpl route-policy, on page 1731 Displays the configuration of a named route policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1719
Routing Policy Language Commands
show rpl prefix-set attachpoints
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl prefix-set attachpoints command to display all the policies used at an attach point that
reference the named prefix set either directly or indirectly.
The prefix set name is required.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1720
Routing Policy Language Commands
show rpl prefix-set attachpoints
Given this sample configuration, the show rpl prefix-set prefix_set_ex1 attachpoints command
displays the following information:
BGP Attachpoint:Neighbor
Field Description
show rpl as-path-set attachpoints, on page 1682 Displays all the policies used at an attach point that reference
the named AS path set.
show rpl community-set attachpoints, on page Displays all the policies used at an attach point that reference
1689 the named community set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1721
Routing Policy Language Commands
show rpl prefix-set attachpoints
Command Description
show rpl route-policy attachpoints, on page Displays all the policies used at an attach point that reference
1734 the named policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1722
Routing Policy Language Commands
show rpl prefix-set references
brief (Optional) Limits the output to just a summary table and not the detailed information for the named
prefix set.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl prefix-set references command to list all the policies that reference the named prefix set.
Use the optional brief keyword to limit the output to just a summary table and not the detailed information
for the named prefix set.
route-policy read
prefix-set ten-net
10.0.0.0/16 le 32
end-set
prefix-set too-specific
0.0.0.0/0 ge 25 le 32
end-set
route-policy example-one
if destination in ten-net then
drop
else
set local-preference 200
apply set-comms
endif
end-policy
route-policy set-comms
set community (10:1234) additive
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1723
Routing Policy Language Commands
show rpl prefix-set references
end-policy
route-policy example-three
if destination in too-specific then
drop
else
apply example-one
pass
endif
end-policy
The following example displays information showing the usage and status of each policy that
references the prefix set ten-net. The brief keyword limits the display to just a summary table and
not the detailed information for the prefix set.
Usage/Status count
-------------------------------------------------------------
Direct 1
Indirect 1
ACTIVE 0
INACTIVE 1
UNUSED 1
Field Description
Usage/Status Displays the usage and status of all policies that reference the prefix set.
count Number of policies that match each usage and status option.
show rpl as-path-set references, on page 1685 Lists all the policies that reference the named AS path set.
show rpl community-set references, on page 1691 Lists all the policies that reference the named community
set.
show rpl route-policy references, on page 1739 Lists all the policies that reference the named policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1724
Routing Policy Language Commands
show rpl rd-set
brief (Optional) Limits the display to a list of the names of all RD sets without their configurations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Because sets cannot hierarchically reference other sets or policies, no detail keyword exists as with the
show rpl policy command.
route-policy read
rd-set rdset1
10:151,
100.100.100.1:153,
100.100.100.62/31:63
end-set
show rpl as-path-set, on page 1680 Displays the configuration of a named AS path set.
show rpl community-set, on page 1687 Displays the configuration of a named community set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1725
Routing Policy Language Commands
show rpl rd-set
Command Description
show rpl extcommunity-set, on page 1694 Displays the configuration of a named extended community set.
show rpl prefix-set, on page 1718 Displays the configuration of a named prefix set.
show rpl route-policy, on page 1731 Displays the configuration of a named route policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1726
Routing Policy Language Commands
show rpl rd-set attachpoints
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl rd-set attachpoints command to display all the policies used at an attach point that
reference the named RD set either directly or indirectly.
route-policy read
route-policy rdsetmatch
if rd in rdset1 then
set community (10:112)
elseif rd in rdset2 then
set community (10:223)
endif
end-policy
router bgp 10
address-family vpnv4 unicast
exit
neighbor 10.0.101.1
remote-as 11
address-family vpnv4 unicast
route-policy rdsetmatch in
!
Given this sample configuration, the show rpl rd-set rdset1 attachpoints command displays the
following information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1727
Routing Policy Language Commands
show rpl rd-set attachpoints
Field Description
afi/safi BGP address family or subaddress family where the RD set is used.
in/out Direction
show rpl as-path-set attachpoints, on page 1682 Displays all the policies used at an attach point that reference
the named AS path set.
show rpl community-set attachpoints, on page Displays all the policies used at an attach point that reference
1689 the named community set.
show rpl prefix-set attachpoints, on page 1720 Displays all the policies used at an attach point that reference
the named prefix set.
show rpl route-policy attachpoints, on page Displays all the policies used at an attach point that reference
1734 the named policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1728
Routing Policy Language Commands
show rpl rd-set references
brief (Optional) Limits the output to just a summary table and not the detailed information for the RD set.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl rd-set references command to list all the policies that reference the named RD set.
Use the optional brief keyword to limit the output to just a summary table and not the detailed information
for the named RD set.
route-policy read
route-policy rdsetmatch
if rd in rdset1 then
set community (10:112)
elseif rd in rdset2 then
set community (10:223)
endif
end-policy
!
router bgp 10
address-family vpnv4 unicast
!
neighbor 10.0.101.1
remote-as 11
address-family vpnv4 unicast
route-policy rdsetmatch in
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1729
Routing Policy Language Commands
show rpl rd-set references
Given this sample configuration, the show rpl rd-set rdset1 references command displays the
following information:
Usage/Status count
--------------------------------------------------------------
Direct 1
Indirect 0
ACTIVE 1
INACTIVE 0
UNUSED 0
Field Description
show rpl as-path-set references, on page 1685 Lists all the policies that reference the named AS path set.
show rpl community-set references, on page 1691 Lists all the policies that reference the named community
set.
show rpl prefix-set references, on page 1723 Lists all the policies that reference the named prefix set.
show rpl route-policy references, on page 1739 Lists all policies that reference the named policy.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1730
Routing Policy Language Commands
show rpl route-policy
detail (Optional) Displays the configuration of all policies and sets that a policy uses.
brief (Optional) Limits the display to a list of the names of all extended community sets without their
configurations.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the optional brief keyword to limit the display to a list of the names of policies without their
configurations.
route-policy read
Examples In the following example, the configuration of a route policy named policy_1 is displayed.
route-policy policy_1
if destination in prefix_set_1 and not destination in sample1 then
if as-path in aspath_set_1 then
set local-preference 300
set origin igp
elseif as-path in as_allowed then
set local-preference 400
set origin igp
else
set origin igp
endif
else
drop
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1731
Routing Policy Language Commands
show rpl route-policy
endif
set med 120
set community (8660:612) additive
apply set_lpref_from_comm
end-policy
If the optional detail keyword is used, all routing policy language (RPL) policies and sets that route
policy policy_1 uses are displayed, as shown in the following example.
!
prefix-set sample1
0.0.0.0/0,
0.0.0.0/0 ge 25 le 32,
10.0.0.0/8 ge 8 le 32,
192.168.0.0/16 ge 16 le 32,
224.0.0.0/20 ge 20 le 32,
240.0.0.0/20 ge 20 le 32
end-set
!
prefix-set prefix_set_1
10.0.0.1/24 ge 24 le 32,
10.0.0.5/24 ge 24 le 32,
172.16.0.1/24 ge 24 le 32,
172.16.5.5/24 ge 24 le 32,
172.16.20.10/24 ge 24 le 32,
172.30.0.1/24 ge 24 le 32,
10.0.20.10/24 ge 24 le 32,
172.18.0.5/24 ge 24 le 32,
192.168.0.1/24 ge 24 le 32,
192.168.20.10/24 ge 24 le 32,
192.168.200.10/24 ge 24 le 32,
192.168.255.254/24 ge 24 le 32
end-set
!
as-path-set as_allowed
ios-regex '.* _1239_ .*',
ios-regex '.* _3561_ .*',
ios-regex '.* _701_ .*',
ios-regex '.* _666_ .*',
ios-regex '.* _1755_ .*',
ios-regex '.* _1756_ .*'
end-set
!
as-path-set aspath_set_1
ios-regex '_9148_',
ios-regex '_5870_',
ios-regex '_2408_',
ios-regex '_2531_',
ios-regex '_197_',
ios-regex '_2992_'
end-set
!
route-policy set_lpref_from_comm
if community matches-any (2:50) then
set local-preference 50
elseif community matches-any (2:60) then
set local-preference 60
elseif community matches-any (2:70) then
set local-preference 70
elseif community matches-any (2:80) then
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1732
Routing Policy Language Commands
show rpl route-policy
set local-preference 80
elseif community matches-any (2:90) then
set local-preference 90
endif
end-policy
!
route-policy policy_1
if destination in prefix_set_1 and not destination in sample1 then
if as-path in aspath_set_1 then
set local-preference 300
set origin igp
elseif as-path in as_allowed then
set local-preference 400
set origin igp
else
set origin igp
endif
else
drop
endif
set med 120
set community (8660:612) additive
apply set_lpref_from_comm
end-policy
show rpl as-path-set, on page 1680 Displays the configuration of a named AS path set.
show rpl community-set, on page 1687 Displays the configuration of a named community set.
show rpl extcommunity-set, on page 1694 Displays the configuration of a named extended community set.
show rpl prefix-set, on page 1718 Displays the configuration of a named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1733
Routing Policy Language Commands
show rpl route-policy attachpoints
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl route-policy attachpoints command to display all the policies used at an attach point that
reference the named policy either directly or indirectly.
The policy name is required.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1734
Routing Policy Language Commands
show rpl route-policy attachpoints
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
RP/0/RSP0/CPU0:router# show rpl route-policy policy_2
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
The following command displays the route policy attach points for policy_2:
Field Description
vrf name Name of the VPN routing and forwarding (VRF) instance.
show rpl as-path-set attachpoints, on page 1682 Displays all the policies used at an attach point that reference
the named AS path set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1735
Routing Policy Language Commands
show rpl route-policy attachpoints
Command Description
show rpl community-set attachpoints, on page Displays all the policies used at an attach point that reference
1689 the named community set.
show rpl prefix-set attachpoints, on page 1720 Displays all the policies used at an attach point that reference
the named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1736
Routing Policy Language Commands
show rpl route-policy inline
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl route-policy inline command to examine the configuration of a specified route policy.
All policies and sets that a policy uses are gathered together and displayed expanded inline.
The policy name is required.
route-policy read
!
route-policy policy_1
if destination in prefix_set_1 and not destination in martians then
if as-path in aspath_set_1 then
set local-preference 300
set origin igp
elseif as-path in as_allowed then
set local-preference 400
set origin igp
else
set origin igp
endif
else
drop
endif
set med 120
set community (8660:612) additive
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1737
Routing Policy Language Commands
show rpl route-policy inline
apply set_lpref_from_comm
end-policy
The following command displays the route policy policy_1 and all the other sets or policies it refers
too inline. Adding the inline keyword causes the configuration to be displayed inline for all RPL
objects that the route-policy policy_1 uses.
route-policy policy_1
if destination in (91.5.152.0/24 ge 24 le 32, 91.220.152.0/24 ge 24 le 32, 61.106.52.0/24
ge 24 le 32, 222.168.199.0/24
ge 24 le 32, 93.76.114.0/24 ge 24 le 32, 41.195.116.0/24 ge 24 le 32, 35.92.152.0/24 ge
24 le 32, 143.144.96.0/24 ge 24
le 32, 79.218.81.0/24 ge 24 le 32, 75.213.219.0/24 ge 24 le 32, 178.220.61.0/24 ge 24 le
32, 27.195.65.0/24 ge 24 le 32)
and not destination in (0.0.0.0/0, 0.0.0.0/0 ge 25 le 32, 10.0.0.0/8 ge 8 le 32,
192.168.0.0/16 ge 16 le 32, 224.0.0.0/20
ge 20 le 32, 240.0.0.0/20 ge 20 le 32) then
if as-path in (ios-regex '_9148_', ios-regex '_5870_', ios-regex '_2408_', ios-regex
'_2531_', ios-regex '_197_',
ios-regex '_2992_') then
set local-preference 300
set origin igp
elseif as-path in
(ios-regex '.* _1239_ .*', ios-regex '.* _3561_ .*', ios-regex '.* _701_ .*', ios-regex
'.* _666_ .*', ios-regex '.* _1755_ .*',
ios-regex '.* _1756_ .*') then
set local-preference 400
set origin igp
else
set origin igp
endif
else
drop
endif
set med 120
set community (8660:612) additive
# apply set_lpref_from_comm
if community matches-any (2:50) then
set local-preference 50
elseif community matches-any (2:60) then
set local-preference 60
elseif community matches-any (2:70) then
set local-preference 70
elseif community matches-any (2:80) then
set local-preference 80
elseif community matches-any (2:90) then
set local-preference 90
endif
# end-apply set_lpref_from_comm
end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1738
Routing Policy Language Commands
show rpl route-policy references
brief (Optional) Limits the output to just a summary table and not the detailed information for the named
policy.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl route-policy references command to list all the policies that reference the named policy.
Use the optional brief keyword to limit the output to just a summary table and not the detailed information
for the policy.
route-policy read
prefix-set ten-net
10.0.0.0/16 le 32
end-set
prefix-set too-specific
0.0.0.0/0 ge 25 le 32
end-set
route-policy example-one
if destination in ten-net then
drop
else
set local-preference 200
apply set-comms
endif
end-policy
route-policy set-comms
set community (10:1234) additive
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1739
Routing Policy Language Commands
show rpl route-policy references
end-policy
route-policy example-three
if destination in too-specific then
drop
else
apply example-one
pass
endif
end-policy
The following command displays information about the policy set-comms and how it is referenced:
Usage/Status count
--------------------------------------------------------------
Direct 1
Indirect 1
ACTIVE 0
INACTIVE 1
UNUSED 1
The direct usage indicates that the route policy example-one directly applies the policy set-comms,
that is, example-one has a line in the form apply set-comms. The usage Indirect indicates that the
route policy example-three does not directly apply the route policy set-comms. However, the route
policy example-three does apply the policy example-one, which in turn applies the policy set-comms,
so there is an indirect reference from example-three to the route policy set-comms.
The status column indicates one of three states. A policy is active if it is in use at an attach point. In
the example provided, neither example-one nor example-three is in use at an attach point, which
leaves two possible states: UNUSED or INACTIVE. The route policy example-one is inactive because
it has some other policy (example-three) that references it, but neither example-one nor any of the
policies that reference it (example-one) are in use at an attach point. The route policy example-three
has a status of unused because it is not used at an attach point and no other route policies in the system
refer to it.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1740
Routing Policy Language Commands
show rpl route-policy references
Field Description
Usage/Status Displays the usage and status of all policies that reference the specified policy.
Values for usage are Direct or Indirect.
Values for status are ACTIVE, INACTIVE, and UNUSED.
count Number of policies that match each usage and status option.
route-policy One name for multiple policies that reference the specified policy.
show rpl as-path-set references, on page 1685 Lists all policies that reference the named AS path set.
show rpl community-set references, on page 1691 Lists all policies that reference the named community set.
show rpl prefix-set references, on page 1723 Lists all policies that reference the named prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1741
Routing Policy Language Commands
show rpl route-policy uses
policies Generates a list of all policies that the named policy uses.
sets Lists all named sets that are used by the policy.
all Generates a list of both sets and policies that the named policy references.
direct (Optional) Lists only the policies or sets used directly in the named policy block. Set or policy
references that occur as a result of an apply statement are not listed.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl route-policy uses command to display information about a specified named policy.
route-policy read
prefix-set ten-net
10.0.0.0/16 le 32
end-set
prefix-set too-specific
0.0.0.0/0 ge 25 le 32
end-set
route-policy example-one
if destination in ten-net then
drop
else
set local-preference 200
apply set-comms
endif
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1742
Routing Policy Language Commands
show rpl route-policy uses
end-policy
route-policy set-comms
set community (10:1234) additive
end-policy
route-policy example-three
if destination in too-specific then
drop
else
apply example-one
pass
endif
end-policy
The following command lists the policies one and set-comms. It also lists the prefix sets too-specific
and ten-net.
type prefix-set:
ten-net too-specific
The sets example-one and set-comms are listed as policies that are used by the policy example-three.
The policy example-one is listed because route policy example-three uses it in an apply statement.
The policy set-comms is also listed because example-one applies it. Similarly, the prefix-set
too-specific is used directly in the if statement in the policy example-three, and the prefix-set ten-net
is used in the policy example-one. The optional direct keyword can be used to limit the output to
just those sets and policies that are used within the example-three block itself, as shown in the
following example:
As can be seen in the output, the route policy set-comms and the prefix set ten-net are no longer
included in the output when the direct keyword is used. The direct form of the command considers
only those sets or policies used in the specified route policy and any additional policies or sets that
may be used if you follow the hierarchy of apply statements.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1743
Routing Policy Language Commands
show rpl route-policy uses
Field Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1744
Routing Policy Language Commands
show rpl unused as-path-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for unused AS path sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl unused as-path-set command to display all AS path sets that are not used in a policy at
an attach point either directly or indirectly and are not referenced by any policies in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
as-path-set as_path_set_ex1
ios-regex '^_65500_$',
ios-regex '^_65501_$'
end-set
!
as-path-set as_path_set_ex2
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1745
Routing Policy Language Commands
show rpl unused as-path-set
ios-regex '^_65502_$',
ios-regex '^_65503_$'
end-set
!
as-path-set as_path_set_ex3
ios-regex '^_65504_$',
ios-regex '^_65505_$'
end-set
!
route-policy sample
if (destination in sample) then
drop
endif
end-policy
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample
apply policy_3
end-policy
Given this sample configuration, the show rpl unused as-path-set command displays the following
information:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1746
Routing Policy Language Commands
show rpl unused as-path-set
Related Commands show rpl unused community-set, on page 1748 Displays the community sets that are not referenced at all.
show rpl unused extcommunity-set, on page 1751 Displays the extended community sets that are not
referenced at all.
show rpl unused prefix-set, on page 1753 Displays the prefix sets that are not referenced at all.
show rpl unused rd-set, on page 1756 Displays the RD sets that are not referenced at all.
show rpl unused route-policy, on page 1758 Displays the route policies that are not referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1747
Routing Policy Language Commands
show rpl unused community-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for unused community sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl unused community-set command to display all the community sets that are not used in
a policy at an attach point either directly or indirectly and are not referenced by any policies in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
community-set comm_set_ex1
65500:1,
65500:2,
65500:3
end-set
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1748
Routing Policy Language Commands
show rpl unused community-set
!
community-set comm_set_ex2
65501:1,
65501:2,
65501:3
end-set
!
community-set comm_set_ex3
65502:1,
65502:2,
65502:3
end-set
!
route-policy sample
if (destination in sample) then
drop
endif
end-policy
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_5
apply sample
apply policy_3
end-policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1749
Routing Policy Language Commands
show rpl unused community-set
Given this sample configuration, the show rpl unused community-set command displays the
following information:
show rpl unused as-path-set, on page 1745 Displays the AS path sets that are not referenced at all.
show rpl unused extcommunity-set, on page 1751 Displays the extended community sets that are not
referenced at all.
show rpl unused prefix-set, on page 1753 Displays the prefix sets that are not referenced at all.
show rpl unused rd-set, on page 1756 Displays the RD sets that are not referenced at all.
show rpl unused route-policy, on page 1758 Displays the route policies that are not referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1750
Routing Policy Language Commands
show rpl unused extcommunity-set
Syntax Description cost (Optional) Displays the unused extended-community cost objects.
detail (Optional) Displays the content of the object and all referenced objects for unused extended community
sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl unused extcommunity-set command to display all extended community sets that are not
used in a policy at an attach point either directly or indirectly and are not referenced by any policies in the
system.
route-policy read
Examples The following is sample output for the show rpl unused extcommunity-set command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1751
Routing Policy Language Commands
show rpl unused extcommunity-set
show rpl unused as-path-set, on page 1745 Displays the AS path sets that are not referenced at all.
show rpl unused community-set, on page 1748 Displays community sets that are not referenced at all.
show rpl unused prefix-set, on page 1753 Displays prefix sets that are not referenced at all.
show rpl unused rd-set, on page 1756 Displays the RD sets that are not referenced at all.
show rpl unused route-policy, on page 1758 Displays the route policies that are not referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1752
Routing Policy Language Commands
show rpl unused prefix-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for unused prefix sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl unused prefix-set command to display all prefix sets that are not used in a policy at an
attach point either directly or indirectly and are not referenced by any policies in the system.
route-policy read
router bgp 2
address-family ipv4 unicast
!
neighbor 10.0.101.2
remote-as 100
address-family ipv4 unicast
route-policy policy_1 in
!
!
neighbor 10.0.101.3
remote-as 12
address-family ipv4 unicast
route-policy policy_2 in
!
!
!
prefix-set sample
0.0.0.0/0,
0.0.0.0/0 ge 25 le 32,
10.0.0.0/8 ge 8 le 32,
192.168.0.0/16 ge 16 le 32,
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1753
Routing Policy Language Commands
show rpl unused prefix-set
224.0.0.0/20 ge 20 le 32,
240.0.0.0/20 ge 20 le 32
end-set
!
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
prefix-set prefix_set_ex2
220.220.220.0/24 ge 24 le 32,
220.220.120.0/24 ge 24 le 32,
220.220.130.0/24 ge 24 le 32
end-set
!
prefix-set prefix_set_ex3
221.221.220.0/24 ge 24 le 32,
221.221.120.0/24 ge 24 le 32,
221.221.130.0/24 ge 24 le 32
end-set
!
route-policy sample
if (destination in sample) then
drop
endif
end-policy
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
if (destination in prefix_set_ex2) then
if (community matches-any comm_set_ex2) then
set community (10:666) additive
endif
if (extcommunity matches-any ext_comm_set_rt_ex2) then
set community (10:999) additive
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1754
Routing Policy Language Commands
show rpl unused prefix-set
endif
endif
end-policy
!
route-policy policy_5
apply sample
apply policy_3
end-policy
--------------------------
ext_comm_set_ex3
Given this sample configuration, the show rpl unused prefix-set command displays the following
information:
show rpl unused as-path-set, on page 1745 Displays AS path sets that are not referenced at all.
show rpl unused community-set, on page 1748 Displays community sets that are not referenced at all.
show rpl unused extcommunity-set, on page 1751 Displays extended community sets that are not referenced
at all.
show rpl unused rd-set, on page 1756 Displays the RD sets that are not referenced at all.
show rpl unused route-policy, on page 1758 Displays the route policies that are not referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1755
Routing Policy Language Commands
show rpl unused rd-set
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for unused RD sets.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl unused rd-set command to display all of the RD sets that are not used in a policy at an
attach point either directly or indirectly and are not referenced by any policies in the system.
route-policy read
Examples The show rpl unused rd-set command displays the following information:
show rpl unused as-path-set, on page 1745 Displays the AS path sets that are not referenced at all.
show rpl unused community-set, on page 1748 Displays the community sets that are not referenced at all.
show rpl unused extcommunity-set, on page 1751 Displays the extended community sets that are not
referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1756
Routing Policy Language Commands
show rpl unused rd-set
Command Description
show rpl unused prefix-set, on page 1753 Displays the prefix sets that are not referenced at all.
show rpl unused route-policy, on page 1758 Displays the route policies that are not referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1757
Routing Policy Language Commands
show rpl unused route-policy
Syntax Description detail (Optional) Displays the content of the object and all referenced objects for unused route policies.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the show rpl unused route-policy command to display route policies that are defined but not used at
an attach point or referenced from another policy using an apply statement.
route-policy read
Building configuration...
prefix-set prefix_set_ex1
10.0.0.0/16 ge 16 le 32,
0.0.0.0/0 ge 25 le 32,
0.0.0.0/0
end-set
!
prefix-set prefix_set_ex2
220.220.220.0/24 ge 24 le 32,
220.220.120.0/24 ge 24 le 32,
220.220.130.0/24 ge 24 le 32
end-set
!
as-path-set as_path_set_ex1
ios-regex '^_65500_$',
ios-regex '^_65501_$'
end-set
!
as-path-set as_path_set_ex2
ios-regex '^_65502_$',
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1758
Routing Policy Language Commands
show rpl unused route-policy
ios-regex '^_65503_$'
end-set
!
as-path-set as_path_set_ex3
ios-regex '^_65504_$',
ios-regex '^_65505_$'
end-set
!
community-set comm_set_ex1
65500:1,
65500:2,
65500:3
end-set
!
community-set comm_set_ex2
65501:1,
65501:2,
65501:3
end-set
!
extcommunity-set rt ext_comm_set_rt_ex1
1.2.3.4:34
end-set
!
extcommunity-set rt ext_comm_set_rt_ex2
2.3.4.5:36
end-set
!
route-policy sample
if (destination in sample) then
drop
endif
end-policy
!
route-policy policy_1
if (destination in prefix_set_ex1) then
set local-preference 100
endif
if (as-path in as_path_set_ex1) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_2
if (destination in prefix_set_ex1) then
if (community matches-any comm_set_ex1) then
set community (10:666) additive
endif
if (extcommunity rt matches-any ext_comm_set_rt_ex1) then
set community (10:999) additive
endif
endif
end-policy
!
route-policy policy_3
if (destination in prefix_set_ex2) then
set local-preference 100
endif
if (as-path in as_path_set_ex2) then
set community (10:333) additive
endif
end-policy
!
route-policy policy_4
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1759
Routing Policy Language Commands
show rpl unused route-policy
In the following example, route policies that are defined but not used at an attach point or referenced
from another policy using an apply statement are displayed using the show rpl unused route-policy
command.
show rpl unused as-path-set, on page 1745 Displays AS path sets that are not referenced at all.
show rpl unused community-set, on page 1748 Displays community sets that are not referenced at all.
show rpl unused extcommunity-set, on page 1751 Displays extended community sets that are not referenced
at all.
show rpl unused prefix-set, on page 1753 Displays prefix sets that are not referenced at all.
show rpl unused rd-set, on page 1756 Displays the RD sets that are not referenced at all.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1760
Routing Policy Language Commands
source in
source in
To test the source of a Border Gateway Protocol (BGP) route against the address contained in either a named
or an inline prefix set, use the source in command in route-policy configuration mode.
source in {prefix-set-nameinline-prefix-setparameter}
inline-prefix-set Inline prefix set. The inline prefix set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the source in command as a conditional expression within an if statement to test the source of the route
against the data in either a named or an inline prefix set. A comparison that references a prefix set with zero
elements in it returns false.
Note For a list of all conditional expressions available within an if statement, see the if command.
The source of a BGP route is the IP peering address of the neighboring router from which the route was
received.
The prefix set can contain both IPv4 and IPv6 prefix specifications.
route-policy read,
write
Examples In the following example, the source of a BGP route is tested against the data in the prefix set
my-prefix-set:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1761
Routing Policy Language Commands
source in
In this example, the source of a BGP route is tested against the data in an inline IPv4 prefix set:
In this example, the source of a route is tested against the data in an inline IPv6 prefix set:
prefix-set, on page 1593 Enters a prefix set configuration mode and defines a prefix set.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1762
Routing Policy Language Commands
suppress-route
suppress-route
To indicate that a given component of a BGP aggregate should be suppressed, use the suppress-route
command in route-policy configuration mode.
suppress-route
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the suppress-route command to indicate that a given component of an aggregate should be suppressed,
that is, not advertised by BGP. See the unsuppress-route, on page 1768 command for information on overriding
the suppress-route command for individual neighbors.
The suppress-route command can be used as an action statement within an if statement. For a list of all
action statements available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, if the destination is in 10.1.0.0/16, then the route is not advertised:
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl-if)# end-policy
unsuppress-route, on page 1768 Indicates that a given component of an aggregate should be unsuppressed
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1763
Routing Policy Language Commands
tag
tag
To match a specific tag value, use the tag command in route-policy configuration mode.
Syntax Description eq | ge | le | is Equal to; greater than or equal to; less than or equal to.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the tag command as a conditional expression within an if statement to match a specific tag value.
Note For a list of all conditional expressions available within an if statement, see the if command.
A tag is a 32-bit integer that can be associated with a given route within the RIB.
The eq operator matches either a specific tag value or a parameter value. Its variants ge and le match a
range of tag values that are either greater than or equal to or less than or equal to the supplied value or parameter.
route-policy read,
write
Examples In the following example, if the tag equals 10, then the condition returns true:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1764
Routing Policy Language Commands
tag in
tag in
To match a tag entry in a named tag set or inline tag set, use the tag in command in route-policy configuration
mode.
tag in {tag-set-nameinline-tag-setparameter}
Syntax Description tag-set-name Name of a tag set. The tag-set accepts 32-bit Integer value. Range is 0 to 4294967295.
inline-tag-set Inline tag set. The inline tag set must be enclosed in parentheses.
parameter Parameter name. The parameter name must be preceded with a “$.”
parameter
Usage Guidelines Use the tag in command as a conditional expression within an if statement to match a tag entry in a named
tag set or inline tag set.
Note For a list of all conditional expressions available within an if statement, see the if command.
This command takes either a named tag set or an inline tag set value as an argument. The condition returns
true if the tag entry matches any entry in the tag set or inline tag set. An attempt to match a tag using a tag set
that is defined but contains no elements returns false.
The routing policy language (RPL) provides the ability to test tags for a match to a list of tag match
specifications using the in operator. The tag in command is protocol-independent.
route-policy read,
write
Examples In the following example, a tag set named my-tag-set is defined and a route policy named use-tag-in
is created. Within the use-tag-in route policy, the tag in command is used within an if statement
to learn if the tag is in the tag-set named my-tag-set. If it is, then local preference is set to 100. If
it is not in my-tag-set but does match the next tag specifications, then local preference is set to 200.
RP/0/RSP0/CPU0:router(config)#tag-set my-tag-set
RP/0/RSP0/CPU0:router(config-tag)#1000
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1765
Routing Policy Language Commands
tag in
RP/0/RSP0/CPU0:router(config-tag)#3000
RP/0/RSP0/CPU0:router(config-tag)#end-set
RP/0/RSP0/CPU0:router(config)#route-policy use-tag-in
RP/0/RSP0/CPU0:router(config-rpl)#if tag in my-tag-set then
RP/0/RSP0/CPU0:router(config-rpl-if)#set local-preference 100
RP/0/RSP0/CPU0:router(config-rpl-if)#elseif tag in (2000, 4000) then
RP/0/RSP0/CPU0:router(config-rpl-elseif)#set local-preference 200
RP/0/RSP0/CPU0:router(config-rpl-elseif)#endif
RP/0/RSP0/CPU0:router(config-rpl)#end policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1766
Routing Policy Language Commands
tag-set
tag-set
To enter tag set configuration mode and define a tag set, use the tag-set command in global configuration
mode. To remove a named tag set, use the no form of this command.
tag-set name
no tag-set name
Usage Guidelines Use the tag-set command to enter tag set configuration mode and define a tag set. A tag-set is a 32-bit integer
that can be associated with a given route within the RIB.
route-policy read,
write
Examples In the following example, a tag set named my-tag-set is defined and a route policy named use-tag-in
is created. Within the use-tag-in route policy, the tag in command is used within an if statement
to learn if the tag is in the tag-set named my-tag-set. If it is, then local preference is set to 100. If
it is not in my-tag-set but does match the next tag specifications, then local preference is set to 200.
RP/0/RSP0/CPU0:router(config)#tag-set my-tag-set
RP/0/RSP0/CPU0:router(config-tag)#1000
RP/0/RSP0/CPU0:router(config-tag)#3000
RP/0/RSP0/CPU0:router(config-tag)#end-set
RP/0/RSP0/CPU0:router(config)#route-policy use-tag-in
RP/0/RSP0/CPU0:router(config-rpl)#if tag in my-tag-set then
RP/0/RSP0/CPU0:router(config-rpl-if)#set local-preference 100
RP/0/RSP0/CPU0:router(config-rpl-if)#elseif tag in (2000, 4000) then
RP/0/RSP0/CPU0:router(config-rpl-elseif)#set local-preference 200
RP/0/RSP0/CPU0:router(config-rpl-elseif)#endif
RP/0/RSP0/CPU0:router(config-rpl)#end policy
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1767
Routing Policy Language Commands
unsuppress-route
unsuppress-route
To indicate that a given component of a BGP aggregate should be unsuppressed, use the unsuppress-route
command in route-policy configuration mode.
unsuppress-route
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the unsuppress-route command to indicate that a given component of an aggregate should be
unsuppressed, that is, allowed to be advertised by BGP again. This command affects routes that have been
suppressed in the generation of BGP aggregates. If the request to unsuppress a route is encountered in a policy
at a neighbor-out attach point, it guarantees that the routes that it affects are advertised to that neighbor even
if that route was suppressed using the suppress-route command in a policy at the aggregation attach point.
The unsuppress-route command can be used as an action statement within an if statement. For a list of
all action statements available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, if the destination is in 10.1.0.0/16, then the route is not advertised:
RP/0/RSP0/CPU0:router(config-rpl-if)# endif
RP/0/RSP0/CPU0:router(config-rpl)# end-policy
Assuming that the policy is attached at a neighbor-out attach point, if the route 10.1.0.0/16 was
suppressed in a policy at an aggregation attach point, 10.1.0.0/16 is advertised to the neighbor. Routes
continue to be suppressed in advertisements to other BGP neighbors unless a specific policy is
attached to unsuppress the route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1768
Routing Policy Language Commands
unsuppress-route
suppress-route, on page 1763 Indicates that a given component of a BGP aggregate should be suppressed.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1769
Routing Policy Language Commands
var globalVarN
var globalVarN
To assign a value to route-policy global variable "globalVar1, globalVar2, globalVar3, globalVar4, and
globalVar5", use the var globalVarN command in route-policy configuration mode.
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is from 1 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Command Default If the var globalVarN statement is not present then the value for globalVarN is zero.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The globalVarN variables can be used to control policy execution flow. You can assign a weightage to mark
the flow and check the value using an if statement.
Note The var globalVarN represents statements "var globalVar1" , "var globalVar2" , "var globalVar3" , "var
globalVar4" and "var globalVar5". This command can be used as an assignment statement within an if statement
or in child policies and the value can be used to compare in an if statement.
Example
In the following example, the globalVar1 is set to 123 and globalVar2 is set to the value stored in
parameter $param.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1770
Routing Policy Language Commands
vpn-distinguisher is
vpn-distinguisher is
To match a specific Border Gateway Protocol (BGP) VPN distinguisher, use the vpn-distinguisher is
command in route-policy configuration mode.
vpn-distinguisher is {numberparameter}
Syntax Description number Value assigned to a 32-bit unsigned integer. Range is from 1 to 4294967295.
parameter Parameter name. The parameter name must be preceded with a “$.”
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vpn-distinguisher is command as a conditional expression within an if statement to test the value
of the origin attribute.
A VPN distinguisher is used in Layer 3 VPN networks for enhanced individual VPN control and to avoid
route target mapping at AS boundaries in inter-AS VPN networks. Route target extended communities are
removed at neighbor outbound and the VPN distinguisher value is applied on the BGP route as an extended
community. When the route is received on a neighboring router in another AS, the VPN distinguisher is
removed and mapped to a route target extended community.
Note For a list of all conditional expressions available within an if statement, see the if command.
route-policy read,
write
Examples In the following example, the origin is tested within an if statement to learn if it is either igp or
egp :
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1771
Routing Policy Language Commands
vpn-distinguisher is
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1772
Static Routing Commands
This module describes the commands used to establish static routes on Cisco ASR 9000 Series Aggregation
Services Routers .
For detailed information about static routing concepts, configuration tasks, and examples, see the Implementing
Static Routes on Cisco ASR 9000 Series Router module in the Routing Configuration Guide for Cisco ASR
9000 Series Routers.
• address-family (static), on page 1774
• maximum path (static), on page 1776
• metric (static), on page 1778
• route (static), on page 1780
• router static, on page 1783
• vrf (static), on page 1785
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1773
Static Routing Commands
address-family (static)
address-family (static)
To enter various address family configuration modes while configuring static routes, use the address-family
command in the appropriate configuration mode. To disable support for an address family, use the no form
of this command.
ipv6 Specifies IP Version 6 address prefixes. This option is available only in static router configuration
mode.
multicast Specifies multicast address prefixes. This option is available only in static router configuration
mode.
Command Default All static routes belong to the default VRF if you enter address family configuration mode without entering
VRF configuration mode.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the address-family command to enter various address family configuration modes while configuring
static routing sessions. From address family configuration mode, you can configure static routes using the
route command.
static read,
write
Examples The following example shows how to enter IPv6 unicast address family mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1774
Static Routing Commands
address-family (static)
RP/0/RSP0/CPU0:router(config-static-afi)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1775
Static Routing Commands
maximum path (static)
Syntax Description ipv4 | ipv6 Specifies IP Version 4 (IPv4) or IP Version 6 (IPv6) address prefixes.
value Maximum number of static routes for the given AFI. The range is 1 to 140000.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If you use the maximum path command to reduce the configured maximum allowed number of static routes
for a given table below the number of static routes currently configured, the change is rejected. In addition,
if you commit a batch of routes that would, when grouped, push the number of static routes configured above
the maximum allowed, the first n routes in the batch and the number previously configured are accepted,
and the remainder rejected. The n argument is the difference between the maximum number allowed and
the number previously configured.
static read,
write
Examples The following example shows how to set the maximum number of static IPv4 routes to 100000:
The following example shows how to remove the preceding configuration and set the maximum
number of static IPv4 routes back to the default:
RP/0/RSP0/CPU0:router(config-static)# no maximum path ipv4 100000
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1776
Static Routing Commands
maximum path (static)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1777
Static Routing Commands
metric (static)
metric (static)
To set metric values for static routes, use the metric command on a route after you have entered address
family configuration mode. To disable metric values, use the no form of this command.
Syntax Description ip-address The IP address is required and, if the interface-path-id arguments are not specified,
then the metric option is not displayed.
metric metric-value Set a metric value for a static route based on the available bandwidth. Ideal range is
0 to 32.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the metric command to provide metric values for a static route with weights.
Example
This example shows how to set the metric value as 5 for a route:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1778
Static Routing Commands
metric (static)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1779
Static Routing Commands
route (static)
route (static)
To establish static routes, use the route command in address family configuration mode. To remove the
route command from the configuration, use the no form of this command.
Syntax Description prefix / mask IP route prefix and prefix mask for the destination.
The network mask can be specified in either of two ways:
• The network mask can be a four-part, dotted-decimal address. For example,
255.0.0.0 indicates that each bit equal to 1 means the corresponding address
bit is a network address.
• The network mask can be indicated as a slash (/) and number. For example, /8
indicates that the first 8 bits of the mask are 1s, and the corresponding bits of
the address are the network address.
vrf vrf-name (Optional) Specifies a destination VRF. This option is available when IPv4 address
families are specified.
The following names cannot be used: all, default, and global.
The following example shows how to configure IPv4 VRF:
router static
address-family ipv4 unicast
10.1.1.0/24 vrf vrf_a 192.168.1.1
router static
vrf vrf_a
address-family ipv4 unicast
10.1.1.0/24 192.168.1.1
ip-address IP address of the next hop that can be used to reach that network.
• For IPv4 address–the IP address is required, not optional, if the interface type
and interface-path-id arguments are not specified. You can specify an IP address
and an interface type and interface path.
• For IPv6 link-local address–the interface type and interface-path-id arguments
are required. The route is not valid, if the interface type and interface-path-id
arguments are not specified.
type Interface type. For more information, use the question mark (?) online help function.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1780
Static Routing Commands
route (static)
For more information about the syntax for the router, use the question mark ( ? )
online help function.
Note A forwarding router's IP address or an interface or virtual interface path
ID can be configured, in any order.
tag tag (Optional) Specifies a tag value that can be used as a match for controlling
redistribution using route policies. Range is 1 to 4294967295.
permanent (Optional) Specifies that the route is not removed from the routing table, even if the
next-hop interface shuts down or next-hop IP address is not reachable.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
A static route is appropriate when the software cannot dynamically build a route to the destination.
Static routes have a default administrative distance of 1, in which a low number indicates a preferred route.
By default, static routes are preferred to routes learned by routing protocols. You can configure an administrative
distance with a static route if you want the static route to be overridden by dynamic routes. For example, you
could have routes installed by the Open Shortest Path First (OSPF) protocol with an administrative distance
of 120. To have a static route that would be overridden by an OSPF dynamic route, specify an administrative
distance greater than 120.
The routing table considers the static routes that point to an interface as “directly connected.” Directly connected
networks are advertised by IGP routing protocols if a corresponding interface command is contained under
the router configuration stanza of that protocol.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1781
Static Routing Commands
route (static)
A static route is always associated with a VPN routing and forwarding (VRF) instance. The VRF can be the
default VRF or a specified VRF. Specifying a VRF allows you to enter VRF configuration mode where you
can configure a static route. If you do not specify a VRF you can configure a default VRF static route.
Use the router static command to configure static routes. To configure a static route, you must enter router
static configuration mode and then enter an address family configuration mode or VRF configuration mode.
See the vrf (static) command for information on configuring a static route in VRF configuration mode. After
you enter an address family mode, you can enter multiple static routes. The following example shows how
to configure multiple static routes in IPv4 and IPv6 address family configuration modes:
Note You cannot create a VRF named default, but you can reference the default VRF.
static read,
write
Examples The following example shows how to configure IPv6 unicast address family static routes:
network (BGP) Specifies a list of networks for the BGP routing process.
show route summary Displays the current contents of the routing table in summary format.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1782
Static Routing Commands
router static
router static
To enter static router configuration mode, use the router static command in global configuration mode. To
remove all static route configurations and terminate the static routing process, use the no form of this
command.
router static
no router static
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
static read,
write
Examples The following example shows how to enter static router configuration mode:
show route summary Displays the current contents of the routing table in summary format.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1783
Static Routing Commands
router static
Command Description
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1784
Static Routing Commands
vrf (static)
vrf (static)
To configure a VPN routing and forwarding (VRF) instance and enter VRF configuration mode, use the vrf
command in router configuration mode. To remove the VRF instance from the configuration file and restore
the system to its default condition, use the no form of this command.
vrf vrf-name
no vrf vrf-name
Syntax Description vrf-name Name of the VRF instance. The following names cannot be used: all, default, and global.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the vrf command to configure a VRF instance. A VRF instance is a collection of VPN routing and
forwarding tables maintained at the provider edge (PE) router.
A static route is always associated with a VRF, which is entirely user configurable. Static route is unique
within a VRF. A static route can point to a next-hop interface, next-hop IP address, or both, which can be
resided in the same VRF configured for the static route or in a different VRF. For example, routes
172.168.40.0/24 and 172.168.50.0/24 are configured as follows:
router static
vrf vrf_A
address ipv4 unicast
172.168.40.0/24 loopback 1
172.168.50.0/24 vrf vrf_B 192.168.1.2
Routes 172.168.40.0/24 and 172.168.50.0/24 belong to vrf_A. Route 172.168.50.0/24 is not installed in vrf_A
until next-hop 192.168.1.2 (a vrf_B route) is reachable.
If you are configuring a default VRF route, you do not need to enter VRF configuration mode. For example,
routes 192.168.1.0/24 and 192.168.2.0/24 are configured as follows:
router static
address ipv4 unicast
192.168.1.0/24 loopback 5
192.168.2.0/24 10.1.1.1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1785
Static Routing Commands
vrf (static)
Note You cannot create a VRF named default, but you can reference the default VRF.
You must remove IPv4/IPv6 addresses from an interface prior to assigning, removing, or changing a VRF on
an IP interface. If this is not done in advance, any attempt to change the VRF on an IP interface is rejected.
static read,
write
Examples The following example shows how to configure a VRF instance and enter VRF configuration mode:
address-family (static), on page 1774 Enters address family configuration mode and allows you to configure
a static route.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1786
RCMD Commands
This module describes the commands used to configure and diagnose RCMD.
For detailed information about RCMD concepts, configuration tasks, and examples, see the Implementing
RCMD module in the Routing Configuration Guide for Cisco ASR 9000 Series Routers.
• router-convergence, on page 1788
• monitor-convergence (IS-IS), on page 1789
• monitor-convergence (OSPF), on page 1790
• collect-diagnostics (RCMD), on page 1791
• event-buffer-size (RCMD), on page 1793
• max-events-stored (RCMD), on page 1794
• monitoring-interval (RCMD), on page 1795
• node disable (RCMD), on page 1797
• prefix-list (monitor-convergence IS-IS), on page 1799
• prefix-list (monitor-convergence OSPF), on page 1801
• priority (RCMD), on page 1803
• protocol (RCMD), on page 1805
• show rcmd isis event prefix, on page 1806
• show rcmd ospf event prefix, on page 1808
• show rcmd ospf event spf , on page 1810
• storage-location, on page 1813
• track-external-routes, on page 1815
• track-summary-routes, on page 1816
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1787
RCMD Commands
router-convergence
router-convergence
To configure route convergence monitoring and enter router convergence monitoring and diagnostics (rcmd)
configuration mode, use the router-convergence command in global configuration mode. To remove all
router convergence monitoring configurations and exit the rcmd mode, use the no form of this command.
router-convergence [disable]
no router-convergence
Syntax Description disable [Optional] Disables the monitoring of route convergence on the entire router.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure router-convergence command and enable rcmd configuration
mode:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1788
RCMD Commands
monitor-convergence (IS-IS)
monitor-convergence (IS-IS)
To enable route convergence monitoring for IS-IS protocol, use the monitor-convergence command in address
family configuration mode. To disable, route convergence monitoring, use the no form of this command.
monitor-convergence
no monitor-convergence
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure route convergence monitoring for IS-IS under IPv6 unicast
SAFI:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router isis isp
RP/0/RSP0/CPU0:router(config-isis)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-isis-af)#monitor-convergence
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1789
RCMD Commands
monitor-convergence (OSPF)
monitor-convergence (OSPF)
To enable OSPF route convergence monitoring, use the monitor-convergence command in router OSPF
configuration mode. To disable OSPF route convergence monitoring, use the no form of this command.
monitor-convergence
no monitor-convergence
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable route convergence monitoring for an OSPF process:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#monitor-convergence
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1790
RCMD Commands
collect-diagnostics (RCMD)
collect-diagnostics (RCMD)
To collect diagnostics on specified node, use the collect-diagnostic command in router-convergence
configuration mode. To disable collection of diagnostics, use the no form of this command.
collect-diagnostics location
no collect-diagnostics location
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
For enabling diagnostics collection on specific line-card locations, you can user can specify partially qualified
semantics. However, it is not allowed to configure over-lapping locations so as to avoid errors. The following
combinations of Rack and Slot are accepted:
• */*/*
• R/*/*
• R/S/*
If a wildcard combination for any location is already disabled, then any other combination that overlaps with
it would be rejected. For example,
• If */*/* is disabled, then all other disable commands will be rejected
• If R/*/* is disabled, then disable for */*/* and R/S/* will be rejected
• If R/S/* is disabled, then disable for */*/* and R/*/* will be rejected
This example shows how to enable RCMD diagnostics collection on node 0/3/CPU0:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1791
RCMD Commands
collect-diagnostics (RCMD)
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#collect-diagnostics 0/3/CPU0
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1792
RCMD Commands
event-buffer-size (RCMD)
event-buffer-size (RCMD)
To specify event buffer size (in terms of number of events) for storing event traces, use the event-buffer-size
command in router-convergence configuration mode. To disable buffer size configuration, use the no form
of this command.
event-buffer-size number
no event-buffer-size
Syntax Description number Specifies the Specify the number of events. The range is 100 to 500.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The event-buffer-size configuration controls the ltrace buffer size. Ltraces will be stored for only the configured
number of events. The default is 100 events and can be set based on the expected churn in the network. Value
for event buffer impact memory usage on all RPs and monitored LCs.
rcmd read,
write
Examples This example shows how to configure event buffer size as 500 events:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#event-buffer-size 500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1793
RCMD Commands
max-events-stored (RCMD)
max-events-stored (RCMD)
To configure maximum number of events to be stored in the RCMD server, use the max-events-stored
command in router-convergence configuration mode. To remove the number of events to be stored, use the
no form of this command.
max-events-stored number
Syntax Description number Specifies the maximum number of events stored. The range is 10 to 500.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The max-events-stored configuration controls the number of events that are stored in RCMD server, before
the older events are deleted. The default is 100 events and can be set based on the expected churn in the
network. Value for events stored impact memory usage by RCMD server.
rcmd read,
write
Examples This example shows how to configure 500 number of events to be stored in RCMD server:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#max-events-stored 500
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1794
RCMD Commands
monitoring-interval (RCMD)
monitoring-interval (RCMD)
To configure interval (in minutes) in which to collect logs, use the monitoring-interval command in
router-convergence configuration mode. To disable monitoring interval configuration, use the no form of this
command.
monitoring-interval minutes
no monitoring-interval minutes
Syntax Description minutes Specifies the interval (in minutes) for collecting logs. The range is 5 to 120 minutes.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The monitoring-interval timer controls the collection, processing, and archival (optional) of convergence data
by RCMD server.
Periodic processing can get triggered if number of events detected exceed configured sizing parameters to
prevent loss of data . However, this is not guaranteed since the mechanism is throttled.
To collect logs manually, use the rcmd trigger-data-collect command. Syslogs are generated when high
churn is detected and collection mechanism is getting throttled. This indicates possible loss of data for some
events. Throttling mechanism is for one processing every minute.
rcmd read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1795
RCMD Commands
monitoring-interval (RCMD)
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#monitoring-interval 5
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1796
RCMD Commands
node disable (RCMD)
Syntax Description node-id Specifies line card locations for which RCMD monitoring be disabled. Disables RCMD monitoring
on the specified node. No data from this node will be available in the reports that are generated.
You can enter specific LCs or use wild cards.
Command Default Update times are gathered and reported for all LCs. Diagnostic mode is disabled on all LCs.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Disable monitoring on specific LCs or racks for better scalability. Disable monitoring on LCs whose update
times is not going to impact the core IGP/LDP convergence that RCMD is measuring.
On LCs where monitoring is enabled, the diagnostic mode can be enabled (with threshold value) for triggering
script using EEM infra for debug data collection from the router. Use diagnostic mode only for debugging
purpose since it is more CPU intensive as compared to normal RCMD monitoring.
Only the following combinations of Rack and Slot are acceptable:
• */*/*
• R/*/*
• R/S/*
If a wildcard combination for any location is already disabled, then any other combination that overlaps with
it would be rejected. For example,
• If */*/* is disabled, then all other disable commands would be rejected
• If R/*/* is disabled, then disable for */*/* and R/S/* would be rejected
• If R/S/* is disabled, then disable for */*/* and R/*/* would be rejected
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1797
RCMD Commands
node disable (RCMD)
rcmd read,
write
Examples This example shows how to disable monitoring on all nodes with Rack 0 and any slot (used wild
card *) :
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#node 0/*/* disable
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1798
RCMD Commands
prefix-list (monitor-convergence IS-IS)
prefix-list prefix-list-name
no prefix-list prefix-list-name
Command Default All IS-IS prefixes are marked for monitoring, if the prefix-list is not configured
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
To enable monitoring of individual prefixes, first configure a prefix-list using the {ipv4 | ipv6} prefix-list
command. Then, use this prefix list with the prefix-list (monitor-convergence IS-IS).
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#ipv4 prefix-list isis_monitor
RP/0/RSP0/CPU0:router(config-ipv4_pfx)#10 permit 35.0.0.0/8 eq 32
RP/0/RSP0/CPU0:router(config-ipv4_pfx)#commit
RP/0/RSP0/CPU0:router(config-ipv4_pfx)#exit
Then, configure the prefix list command under Router IS-IS monitor-convergence configuration
mode:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1799
RCMD Commands
prefix-list (monitor-convergence IS-IS)
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1800
RCMD Commands
prefix-list (monitor-convergence OSPF)
prefix-list prefix-list-name
no prefix-list prefix-list-name
Command Default All OSPF prefixes are marked for monitoring, if the prefix-list is not configured.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
To enable monitoring of individual prefixes, first configure a prefix-list using the {ipv4 | ipv6} prefix-list
command. Then, use this prefix list with the prefix-list (monitor-convergence OSPF).
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#ipv4 prefix-list ospf_monitor
RP/0/RSP0/CPU0:router(config-ipv4_pfx)#10 permit 35.0.0.0/8 eq 32
RP/0/RSP0/CPU0:router(config-ipv4_pfx)#commit
RP/0/RSP0/CPU0:router(config-ipv4_pfx)#exit
Then, configure the prefix list command under Router OSPF monitor-convergence configuration
mode:
RP/0/RSP0/CPU0:router(config)#router ospf 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1801
RCMD Commands
prefix-list (monitor-convergence OSPF)
RP/0/RSP0/CPU0:router(config-ospf)#monitor-convergence
RP/0/RSP0/CPU0:router(config-ospf-af-rcmd)#prefix-list ospf_monitor
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1802
RCMD Commands
priority (RCMD)
priority (RCMD)
To configure RCMD reporting parameters for low/high/critical/medium priority updates, use the priority
command in RCMD protocol configuration mode. To disable setting up priority use the no form of this
command.
Syntax Description Critical Configures the monitoring of route convergence for critical routes.
High Configures the monitoring of route convergence for high priority routes.
Low Configures the monitoring of route convergence for low priority routes.
Medium Configures the monitoring of route convergence for medium priority routes.
leaf-network Configures the monitoring of route convergence for leaf networks. Lists up to 100
leaf networks that were added or deleted as part of SPF.
leaf-network-number Specifies the maximum number of leaf networks monitored. The range is 10 to 100.
threshold Sets the threshold value for convergence in milliseconds. If the convergence time
exceeds this configured value, diagnostics collection will be triggered.
value Specifies the threshold value (in msec). The range is 0 to 4294967295.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the priority command for collecting data and applying threshold for particular protocol and prefix priority.
Maximum of 100 leaf networks can get logged because of scalability reasons. No default value available for
threshold and this needs to be determined with deployment experience for specific network. Threshold
specification is required for triggering diagnostics collection. Disable monitoring for medium and or low
priority routes to help scale better. No specific order is guaranteed for leaf networks and first N prefixes that
change are logged.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1803
RCMD Commands
priority (RCMD)
rcmd read,
write
Examples This example shows how Configures the monitoring of route convergence for critical routes for 100
leaf networks and at a threshold value of 1 millisecond for OSPF protocol:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#protocol OSPF
RP/0/RSP0/CPU0:router(config-rcmd-proto)#priority high
RP/0/RSP0/CPU0:router(config-rcmd-proto-prio)#leaf-network 100
RP/0/RSP0/CPU0:router(config-rcmd-proto-prio)#threshold 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1804
RCMD Commands
protocol (RCMD)
protocol (RCMD)
To specify the protocol for which to configure RCMD parameters, use the protocol command in
router-convergence configuration mode. To remove the protocol from RCMD, use the no form of this command.
Syntax Description ISIS Configures parameters related to OSPF protocol within RCMD
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RCMD monitoring needs to be enabled for a specific OSPF or ISIS protocol instance.
rcmd read,
write
Examples This example shows how to enable RCMD parameters for OSPF protocol:
RP/0/RSP0/CPU0:router(config)#router
RP/0/RSP0/CPU0:router(config)#router-convergence
RP/0/RSP0/CPU0:router(config-rcmd)#protocol OSPF
RP/0/RSP0/CPU0:router(config-rcmd-proto)#priority high
RP/0/RSP0/CPU0:router(config-rcmd-proto-prio)#leaf-network 100
RP/0/RSP0/CPU0:router(config-rcmd-proto-prio)#threshold 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1805
RCMD Commands
show rcmd isis event prefix
show rcmd isis isis-instance event prefix [{event-numberprefix | after event_number | last event_number
| priority {critical | high | low | medium} | threshold-exceeded}] [detail] [xml]
event-number (Optional) Specifies the number of a specific event that is run. Range is 0-4294967295.
prefix (Optional) Specifies events with a prefix. Specify prefix in ip-address/length format.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1806
RCMD Commands
show rcmd isis event prefix
This is sample output from the show rcmd isis event prefix command:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1807
RCMD Commands
show rcmd ospf event prefix
event-number (Optional) Specifies the number of a specific event that is run. Range is 0-4294967295.
prefix (Optional) Specifies events with a prefix. Specify prefix in ip-address/length format.
Usage Guidelines
Task ID Task Operation
ID
ospf read,
write
This is sample output from show rcmd ospf event prefix command:
OSPF process: 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1808
RCMD Commands
show rcmd ospf event prefix
Event: 1
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1809
RCMD Commands
show rcmd ospf event spf
show rcmd ospf ospf-instance event spf [{spf-run | after | last | no-route-change | pending |
route-change | threshold-exceeded}] [detail] [xml]
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1810
RCMD Commands
show rcmd ospf event spf
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This is sample output from the show rcmd ospf event spf command:
Event Status:
^ no route change # threshold exceeded ~ incomplete data * collection pending
OSPF process: 1
SPF run: 16
Trigger: Apr 10 23:07:01.614 Start: 0 Duration: 2
Dijkstra Statistics: Runs: 1 LSA changes: 0
IA/Ext Statistics: Runs: 4 LSA processed: 36
Timeline Summary:
Priority: Critical
Route Count: Added: 18 Deleted: 0 Modified:
0
FRR Coverage: Routes: 9/9(100%) Paths: 18/18(100%)
Priority: High
Route Count: Added: 18 Deleted: 0 Modified:
0
FRR Coverage: Routes: 9/9(100%) Paths: 18/18(100%)
Priority: Medium
Route Count: Added: 18 Deleted: 0 Modified:
0
FRR Coverage: Routes: 9/9(100%) Paths: 18/18(100%)
Priority: Low
Route Count: Added: 21 Deleted: 0 Modified:
0
FRR Coverage: Routes: 10/10(100%) Paths: 21/21(100%)
Dijkstra Info:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1811
RCMD Commands
show rcmd ospf event spf
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1812
RCMD Commands
storage-location
storage-location
To specify where to store the extended routing-diagnostics that are collected when threshold exceeds, use the
storage-location command in router-convergence configuration mode. To disable storing routing-diagnostics
to a specific location, use the no form of this command.
Syntax Description diagnostics Specifies an absolute directory path for storing diagnostic reports.
directory-path Specifies the path of the absolute directory for storing diagnostic reports.
maximum-directory-size Specified the size of the diagnostics directory. The range is 5% to 80%.
directory-path Specifies the path of the absolute directory for storing reports.
reports-size Specifies the maximum size of the reports directory. The range is 5% to 80%.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The storage location can be local disk or remote tftp space.
RCMD server can periodically archive reports in XML format for persistency. This mechanism is enabled
when archival location is configured. Debug data collected in diagnostics mode is dumped to the configured
diagnostic location (else it would get lost). When using local disk, the percentage of disk space to be used can
be specified, and RCMD server will delete older reports on reaching the limit. Archival (specifically on local
disk) is CPU intensive. Use a remote XML server to periodically collect reports from the router and archive
on the server’s local storage.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1813
RCMD Commands
storage-location
rcmd read,
write
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1814
RCMD Commands
track-external-routes
track-external-routes
To enable tracking of external (Type-3/5/7) LSAs prefix monitoring, use the track-external-routes command
in Router OSPF monitor-convergence configuration mode. To disable, tracking of external LSAs prefix
monitoring, use the no form of this command.
track-external-routes
no track-external-routes
This command has no keywords or arguments.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable tracking of external LSAs prefix monitoring:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#monitor-convergence
RP/0/RSP0/CPU0:router(config-ospf-af-rcmd)#track-external-routes
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1815
RCMD Commands
track-summary-routes
track-summary-routes
To enable tracking of summary (inter-area) routes prefix monitoring, use the track-summary-routes command
in Router OSPF monitor-convergence configuration mode. To disable tracking of summary router prefix
monitoring, use the no form of this command.
track-summary-routes
no track-summary-routes
This command has no keywords or arguments.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable tracking of summary routes prefix monitoring:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router ospf 100
RP/0/RSP0/CPU0:router(config-ospf)#monitor-convergence
RP/0/RSP0/CPU0:router(config-ospf-af-rcmd)#track-summary-routes
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1816
Locator/ID Separation Protocol Commands
This module describes the commands used to configure and monitor Locator/ID Separation Protocol (LISP)
on Cisco IOS XR.
• Locator/ID Separation Protocol on Cisco IOS XR, on page 1818
• address-family (LISP), on page 1819
• clear lisp vrf, on page 1821
• decapsulation filter rloc source, on page 1822
• eid-mtu, on page 1824
• eid-table, on page 1826
• etr, on page 1828
• etr accept-map-request-mapping, on page 1829
• etr map-cache-ttl, on page 1831
• etr map-server, on page 1833
• itr map-resolver, on page 1835
• locator reachability, on page 1837
• locator-set, on page 1838
• locator-table, on page 1840
• loc-reach-algorithm rloc-probing, on page 1842
• map-cache-limit, on page 1844
• map-cache, on page 1845
• map-request-source, on page 1847
• map-server rloc members distribute, on page 1848
• map-server rloc members modify-discovered {add | override} , on page 1850
• other-xtr-probe, on page 1852
• proxy-etr, on page 1854
• proxy-itr, on page 1856
• remote-rloc-probe, on page 1858
• router lisp, on page 1859
• show lisp decapsulation filter, on page 1861
• show lisp session, on page 1862
• show lisp site rloc members, on page 1863
• show lisp site, on page 1864
• solicit-map-request, on page 1866
• use-petr, on page 1868
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1817
Locator/ID Separation Protocol Commands
Locator/ID Separation Protocol on Cisco IOS XR
Note The LISP command line interface, show commands output, and schema is to be changed in Cisco IOS XR
Release 4.3.1 to be similar to the LISP command line interface on Cisco IOS.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1818
Locator/ID Separation Protocol Commands
address-family (LISP)
address-family (LISP)
To enter Locator ID and separation protocol (LISP) address family configuration mode, use the address-family
command in LISP configuration mode. To exit the LISP address family configuration mode, use the no form
of this command.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to enable IPv6 address family configuration for LISP:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-afi)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1819
Locator/ID Separation Protocol Commands
address-family (LISP)
Command Description
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache entries
allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-etr, on page 1854 Configures a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel
Router (PETR).
proxy-itr, on page 1856 Configures a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel
Router (PITR).
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1820
Locator/ID Separation Protocol Commands
clear lisp vrf
Syntax Description vrf-name VRF instance. The transport session information for this VRF instance will be cleared.
Note The vrf-name is a locator VRF, rather than an EID VRF. TCP sessions are formed
per locator VRF. Hence, if you have shared mode configured where the locator
VRF is default, then to clear the TCP sessions use the clear lisp vrf default session
{peer-address|*} command.
session Specifies that the reliable transport session for either the specified peer address or all transport
sessions be cleared, based on your choice.
peer-address IPv4 or IPv6 peer address. When you specify a peer-address, the TCP connection to the peer
will be cleared.
* Clears all LISP reliable transport sessions for this particular locator VRF.
Note If you have multiple router LISP instances, other router LISP instances will not be
affected.
The following example shows how to clear all reliable TCP transport sessions with locator VRF v1
using the * option:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1821
Locator/ID Separation Protocol Commands
decapsulation filter rloc source
Syntax Description locator-set Specifies the full set of locators from which traffic will be accepted, both from
locator-set-name other ITRs and PITRs.
member Specifies that the registered RLOC membership list be automatically obtained
from the Map-Server.
Note Either or both of the member or locator-set keywords must be
specified.
Usage Guidelines Configure this command on an xTR or a PxTR to enable LISP decapsulation filtering. When enabled, the
source RLOC addresses of incoming LISP packets are validated against the 'member' filter list. RLOCs that
match the filter list are decapsulated while those that do not are dropped.
When the member keyword is used, the registered RLOC membership list will be automatically obtained from
the Map-Server. The member keyword enables the establishment of a reliable transport (TCP) session with
configured map-servers, and downloads the decapsulation filter list maintained by the map-servers. When the
locator-set locator-set-name keyword is used, the prefixes named in the locator-set are used, if included
alone or added to the (downloaded) dynamic list when used in conjunction with the member keyword.
This option is used to add PITRs which do not register with a Map-Server and are thus not automatically
included in the registered RLOC membership list.
• On an xTR, the TCP-based reliable transport session is established only after the UDP-based (normal)
Map-Registration process successfully completes.
• On a PxTR, since this device does not (normally) register with a Map-Server, a “stub” (fake)
Map-Registration configuration must be added to allow the establishment of the reliable transport session
and the download of any filter lists. The Map-Server requires the PETR RLOC(s) to be included in a
map-server rloc members modify-discovered add command to permit this session establishment.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1822
Locator/ID Separation Protocol Commands
decapsulation filter rloc source
• A (P)xTR normally communicates with multiple Map-Servers. However, in the event that all reliable
transport session goes down, any existing (possibly stale) filter list will remain in use during a small
window of time (several minutes), during which time the (P)xTR tries to re-establish the session(s) with
the MS and refresh its membership.
• If no filter list can be downloaded, or the existing list times out, packets will be dropped. (fail closed.)
• If the xTR changes RLOCs (using DHCP for example), as soon as the RLOC is changed, the registration
with the Map-Server is updated and the new registered RLOC is pushed to all “members” of this IID/VPN
(event-driven).
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#decapsulation filter rloc source member
RP/0/RSP0/CPU0:router(config-lisp)#exit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1823
Locator/ID Separation Protocol Commands
eid-mtu
eid-mtu
To configure MTU sizes for IPv4 or IPv6 LISP payloads, use the eid-mtu command in the LISP address
family configuration mode. To remove the configured the eid-mtu size, use the no form of this command.
Syntax Description ipv4-locator Specifies the MTU for packets transported through IPv4 RLOC space.
ipv4_bytes Specifies the MTU in bytes for packets transported through IPv4 RLOC space. The value
ranges from 68 to 65535.
ipv6-locator Specifies the MTU for packets transported through IPv6 RLOC space.
ipv6_bytes Specifies the MTU in bytes for packets transported through IPv6 RLOC space. The value
ranges from 1280 to 65535.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure MTU size of 1300 bytes for the IPv6 LISP payloads:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1824
Locator/ID Separation Protocol Commands
eid-mtu
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1825
Locator/ID Separation Protocol Commands
eid-table
eid-table
To configure a Locator ID Separation Protocol (LISP) instance ID for association with a virtual routing and
forwarding (VRF) table or default table through which the endpoint identifier (EID) address space is reachable,
use the eid-table command in the LISP configuration mode. To remove this association, use the no form of
this command.
Syntax Description default Selects the default (global) routing table for association with the configured instance ID.
vrf Selects the specified VRF table for association with the configured instance ID.
instance_id Specifies the instance ID value. This value ranges between 0 and 16777215.
Command Default A router configured for LISP associates the default table with instance ID 0.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The eid-table command is used to associate a LISP instance ID with either the default routing table, or a VRF
table through which its EID address space is reachable. When a LISP instance ID is specified, LISP Map
Registration (control plane) messages include this instance ID along with the associated EID prefixes upon
registering and LISP data plane packets include this instance ID in the LISP header.
This example shows how to configure LISP instance ID for association with a virtual routing and
forwarding (VRF) table:
RP/0/RSP0/CPU0:router#configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1826
Locator/ID Separation Protocol Commands
eid-table
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#eid-table vrf vrf1 instance-id 45
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration mode.
itr map-resolver, on page 1835 Configures an IPv4 or IPv6 locator address of the LISP Map-Resolver to
be used by the ITR.
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache entries
allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1827
Locator/ID Separation Protocol Commands
etr
etr
To enable Egress Tunnel Router functionality, use the etr command in the LISP address family configuration
mode. To disable the ETR functionality, use the no form of this command.
etr
no etr
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
The example shows how to turn on ETR functionality in all eid-tables, unless it is explicitly disabled.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-af)#etr
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1828
Locator/ID Separation Protocol Commands
etr accept-map-request-mapping
etr accept-map-request-mapping
To configure an Egress Tunnel Router (ETR) to cache to cache EID-to-RLOC mapping data contained, that
ITRs may attach to a map-request message, use the etr accept-map-request-mapping command in the LISP
address family configuration mode. To remove this functionality, use the no form of this command.
Syntax Description verify (Optional) Specifies that mapping data should be cached but not used for forwarding packets until
the ETR can send its own map request to one of the locators from the mapping data record and
receive a map reply with the same data in response.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
If an ETR receives a map-request message that contains mapping data for the invoking IPv6 source-EID's
packet, then the ETR, by default, ignores the mapping data. However, if you configure the etr
accept-map-request-mapping command, the ETR caches the mapping data in its map cache and immediately
uses it for forwarding packets.
This example shows how to configure etr accept-map-request-mapping command in the LISP
IPv6 address family configuration mode:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1829
Locator/ID Separation Protocol Commands
etr accept-map-request-mapping
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1830
Locator/ID Separation Protocol Commands
etr map-cache-ttl
etr map-cache-ttl
To configure the time-to-live (TTL) value inserted into LISP IPv4 or IPv6 map-reply messages, use the etr
map-cache-ttl command in the LISP address family configuration mode. To remove the configured TTL
value and return to the default value, use the no form of this command.
Syntax Description minutes Specifies the value, in minutes, to be inserted in the TTL field in map-reply messages. The value
ranges from 60 to 10080 minutes.
Command Default The default TTL value is 1440 minutes (24 hours).
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use this command to change the default value associated with the Time-to-Live (TTL) field in map-reply
messages. Entering this command changes the default TTL that remote ITRs will cache and use for your site's
endpoint identifier (EID) prefix. The default value is 1440 minutes (24 hours), and the minimum value is 60
minutes.
This example shows how to configure etr map-cache-ttl command with TTL value of 60 minutes:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-af)#etr map-cache-ttl 60
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1831
Locator/ID Separation Protocol Commands
etr map-cache-ttl
Command Description
address-family (LISP), on page 1819 Enters Locator ID and separation protocol (LISP) address family
configuration mode.
etr, on page 1828 Enables Egress Tunnel Router (ETR) functionality.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1832
Locator/ID Separation Protocol Commands
etr map-server
etr map-server
To configure the options related to the etr map-server (MS) such as locator, authentication key and whether
or not the map server is allowed to respond on the ETR's behalf to map-requests (proxy-reply option), use the
etr map-server command in the LISP address family configuration mode. To remove the configured options,
use the no form of this command.
Syntax Description ip_address Specifies the IPv4 or IPv6 address of the map server.
key Specifies that an authentication key will follow either encrypted or unencrypted option.
proxy-reply Specifies that the map-server with the specified RLOC is allowed to respond to map-requests
on behalf of the ETR.
Command Default LISP map server locator addresses are not configured by default.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1833
Locator/ID Separation Protocol Commands
etr map-server
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1834
Locator/ID Separation Protocol Commands
itr map-resolver
itr map-resolver
To configure an IPv4 or IPv6 locator address of the LISP Map-Resolver to be used by the ITR, when sending
Map-Requests for IPv4 EID-to-RLOC mapping resolution, use the itr map-resolver command in LISP address
family configuration mode. To remove the configured locator address of the LISP Map-Resolver, use the no
form of this command.
Syntax Description map-resolver-address Specifies the IPv4 or IPv6 locator addresses of the Map-Resolver.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example configures an ITR to use the Map-Resolver located at 10.2.3.4 when sending its Map-
Request messages:
RP/0/RSP0/CPU0:routerconfigure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-afi)#itr map-resolver 10.2.3.4
This example configures and ITR to use the Map-Resolver located at 2001:DB8:0A::1 when sending
its Map-Request messages:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1835
Locator/ID Separation Protocol Commands
itr map-resolver
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache entries
allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-etr, on page 1854 Configures a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel
Router (PETR).
proxy-itr, on page 1856 Configures a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel
Router (PITR).
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1836
Locator/ID Separation Protocol Commands
locator reachability
locator reachability
To configure the conditions that must be met for a routing locator (RLOC) to be treated as being reachable,
use the locator reachability command in the LISP address family configuration mode. To remove the
configuration, use the no form of the command.
Syntax Description exclude-default If a remote RLOC is reached via the default route, then it is treated as unreachable.
Command Default
Command Modes LISP IPv4 address family
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-af)#locator reachability exclude-default
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1837
Locator/ID Separation Protocol Commands
locator-set
locator-set
To configure a named locator set, use the locator-set command in the in LISP configuration mode. To disable
a the locator-set, use the no form of the command.
ip_address Specifies the RLOC IP address of Loopback or other Egress Tunnel Router (ETR)
interfaces.
priority Configures the preferred locators from the locator set. When multiple locators have
the same priority traffic may be load-balanced across them.
priority_value Specifies the value of the priority assigned to the RLOC. The value ranges from 0 to
255. A lower value indicates a higher priority.
weight Specifies how to determine to load-share traffic between multiple locators when the
priorities assigned to multiple locators are the same.
weight_value Specifies the value of the percentage of traffic to be load-shared. The value ranges
from 0 to 100.
auto-discover-rlocs Configures the Egress Tunnel Router (ETR) to discover the locators of all routers
configured to function as both an ETR and an Ingress Tunnel Router (ITR)--such
routers are referred to as xTRs--in ETRs LISP site when the site uses multiple xTRs
and each xTR is configured to use DHCP-learned locators or configured with only its
own locators.
Command Default
Command Modes LISP configuration
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
A locator set is a named group of Routing LOCators (RLOCs). It can be used in conjunction with the
database-mapping and map-cache configuration commands.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1838
Locator/ID Separation Protocol Commands
locator-set
This example shows how to configure the locator-set priority such that 2001:1::2 would have the
highest priority and receive all the traffic. 2001:2::3 and 64.10.10.5 would each receive 50% of the
traffic if 2001:1::2 is unreachable.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#locator-set loc1
RP/0/RSP0/CPU0:router(config-lisp)#2001:1::2 priority 1 weight 100
RP/0/RSP0/CPU0:router(config-lisp)#2001:2::3 priority 2 weight 50
RP/0/RSP0/CPU0:router(config-lisp)#64.10.10.5 priority 2 weight 50
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1839
Locator/ID Separation Protocol Commands
locator-table
locator-table
To associate a virtual routing and forwarding (VRF) table through which the routing locator address space is
reachable to a router Locator ID Separation Protocol (LISP) instantiation, use the locator-table command in
LISP configuration mode. To remove this association, use the no form of this command.
Syntax Description default Selects the default (global) routing table for association with the routing locator address space.
vrf Selects the routing table for the specified VRF name for association with the routing locator address
space.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
When a LISP device is deployed in a multitenant (virtualized) network environment with segmented routing
locator (RLOC) address space, separate router LISP instantiations are required for each locator address space.
Separate instantiations are created by including the optional id entry with the router lisp command. Each
router LISP instantiation is considered to be standalone and must be associated with an RLOC address space.
The locator-table command is used to associate a VRF table through which the routing locator address space
is reachable to a router LISP instantiation. All necessary LISP components used in the operation of that
particular router LISP instantiation, (for example, map server, map resolver, proxy ingress tunnel router
(PITR), proxy egress tunnel router (PETR), and other routers that function as both egress and ingress tunnel
routers, also known as xTRs) must be reachable via the routing locator address space referred to by the
locator-table command.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1840
Locator/ID Separation Protocol Commands
locator-table
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#locator-table mplsvpn
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1841
Locator/ID Separation Protocol Commands
loc-reach-algorithm rloc-probing
loc-reach-algorithm rloc-probing
To configure locator reachability algorithm, RLOC Probing, and to determine reachability status for other
iBGP peers through the IGP domain, use the loc-reach-algorithm rloc-probing command in LISP configuration
mode. To disable the locator reachability algorithm, use the no form of this command .
loc-reach-algorithm rloc-probing
no loc-reach-algorithm rloc-probing
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure the location reachability algorithm RLOC probing:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#loc-reach-algorithm rloc-probing
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1842
Locator/ID Separation Protocol Commands
loc-reach-algorithm rloc-probing
Command Description
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-etr, on page 1854 Configures a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel
Router (PETR).
proxy-itr, on page 1856 Configures a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel
Router (PITR).
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1843
Locator/ID Separation Protocol Commands
map-cache-limit
map-cache-limit
To configure the maximum limit of IPv4 LISP or IPv6 LISP map-cache entries allowed to be stored by the
router, use the map-cache-limit command in LISP address family configuration mode. To remove the
configured map-cache limit, use the no form of this command.
map-cache-limit map-cache-size
no map-cache-limit map-cache-size
Syntax Description map-cache-size Specifies the map cache size value. Range is 1 to 65535.
Router(config-lisp-afi)#map-cache-limit 2000
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1844
Locator/ID Separation Protocol Commands
map-cache
map-cache
To configure a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping relationship and its associated
traffic policy, or to statically configure the packet handling behavior associated with a destination IPv4
EID-prefix or a destination IPv6 EID-prefix, use the map-cache command in LISP address family configuration
mode. To remove the configuration, use the no form of this command.
locator locator-address The IPv4 or IPv6 Routing Locator (RLOC) associated with the
EID-prefix/prefix-length.
priority priority-value The priority (value between 0 and 255) assigned to the RLOC. When
multiple locators have the same priority they may be used in load-shared
fashion. A lower value indicates a higher priority.
weight weight-value The weight (value between 0 and 100) assigned to the locator. Used in
order to determine how to load-share traffic between multiple locators
when the priorities assigned to multiple locators are the same. The value
represents the percentage of traffic to be load-shared.
Command Default No IPv6 EID-to-RLOC mapping relationships or static IPv6 EID-to-RLOC mapping destinations are configured.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1845
Locator/ID Separation Protocol Commands
map-cache
configures a destination EID-to-RLOC mapping and associated traffic policy for the IPv6 EID-prefix
block 2001:DB8:BB::/48. The locator for this EID-prefix block is 2001:DB8:0A::1 and the traffic
policy for this locator has a priority of 1 and a weight of 100.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-afi)#map-cache
RP/0/RSP0/CPU0:router(config-lisp-afi-map-cache)#2001:db8:bb::/48 locator 2001:db8:a::1
priority 1 weight 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1846
Locator/ID Separation Protocol Commands
map-request-source
map-request-source
To configure inner header source address to be used as the source address for Locator/ID Separation Protocol
(LISP) map-request messages, use the map-request-source command in LISP address family configuration
mode. To remove the configured map-request source address, use the no form of this command.
map-request-source ip_address
no map-request-source
Syntax Description ip_address Specifies the IPv4 or IPv6 source address of the inner header in the map-request message.
Command Default
Command Modes LISP IPv4 address family
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure the IPv6 source address to be used as the source address for
LISP map-request messages:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-af)#map-request-source 4:5::6
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1847
Locator/ID Separation Protocol Commands
map-server rloc members distribute
Command Default Map-Servers are not enabled to distribute a membership list of RLOCs to xTRs.
Usage Guidelines When an ETR or PETR decapsulates LISP-encapsulated packets, it normally does so without consideration
of the outer (RLOC) header source address. In networking environments where the source address can be
trusted, it may be useful for devices to consider the source address of the LISP packet prior to decapsulation.
A Map-Server can be configured to dynamically create, maintain, and distribute decapsulation filter lists, on
a per instance-ID basis, to appropriate LISP devices using the map-server rloc members distribute command
in site configuration mode. When configured:
• The Map-Server allows the establishment of TCP-based LISP reliable transport sessions with appropriate
xTRs
• The Map-Server creates/maintains lists (per-IID) of LISP site RLOCs based on RLOC addresses of
registered LISP sites
• The Map-Server pushes/updates filters lists over the reliable transport mechanism to established devices
Note Data-plane security is enabled by the use of the map-server roc members distribute command. The optional
command map-server rloc members modified-discovered [add | override] is used to append to or override
the dynamically maintained RLOC filter list.
This feature is used in conjunction with the decapsulation filter rloc source command, configured on (P)xTR
devices which are performing the decapsulation.
The following example shows how to enable Map-Servers to distribute an updated list of EID prefixes
to xTRs:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1848
Locator/ID Separation Protocol Commands
map-server rloc members distribute
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#map-server rloc members distribute
RP/0/RSP0/CPU0:router(config-lisp)#exit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1849
Locator/ID Separation Protocol Commands
map-server rloc members modify-discovered {add | override}
Syntax Description add Adds RLOC addresses in the specified locator set to the list of discovered RLOC
addresses.
override Replaces automatically discovered list of RLOC addresses with the RLOC
addresses in the specified locator-set. When you use this option, the list of RLOC
addresses discovered by the Map-Server is completely removed.
locator-set Specifies a locator set. The locator set contains RLOC addresses that are
locator-set-name previously configured.
Command Default The option to modify the automatically discovered list of RLOC addresses is disabled.
Usage Guidelines When an ETR or PETR is configured to source-filter LISP-encapsulated packets prior to decapsulation, it
may be useful to add to, or in some cases, override this filter list, and this can be accomplished by configuring
the map-server rloc members modify-discovered command in EID-table configuration mode. Uses may
include:
• When a PxTR is included in the architecture, the PITR LISP-encapsulates packets to an ETR – and the
ETR must therefore include the PITR RLOC in its decapsulation filter list. Since PITRs do not register
with Map-Servers, their RLOCs are not automatically included in the decapsulation filter list and must
be added via configuration using this command.
• A PETR can also be configured to filter upon decapsulation, but again, because a PETR does not register
with a Map-Server, it needs a way to obtain the decapsulation filter list. The add form of this command
includes the mechanisms to establish the reliable transport session with the Map-Server for obtaining
the decapsulation filter list on the PETR.
• For diagnostic/troubleshooting reasons, it may be useful to (temporarily) override the entire decapsulation
filter list.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1850
Locator/ID Separation Protocol Commands
map-server rloc members modify-discovered {add | override}
The following example shows how to enable Map-Servers to distribute an updated list of EID prefixes
to xTRs:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#eid-table vrf cust-A instance-id 1
RP/0/RSP0/CPU0:router(config-lisp-eid-table)#map-server rloc members modify-discovered add
locator-set PTR_set
RP/0/RSP0/CPU0:router(config-lisp-eid-table)#exit
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1851
Locator/ID Separation Protocol Commands
other-xtr-probe
other-xtr-probe
To configure parameters for probing of other xTRs site-local routing locators (RLOCs), use the other-xtr-probe
command in the LISP configuration mode. To return to the default setting, use the no form of this command.
seconds Specifies the value of the probing period in seconds. The range is between 5 to 900.
Command Default Probing of site-local RLOCs is enabled by default and cannot be disabled. The default interval is 30 seconds.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Use the other-xtr-probe command to change the probe interval for sending RLOC probes to all site-other
RLOCs.
This command probes site-local rlocs, whereas rloc-probing probes remote RLOCs. The latter can be turned
on or off with loc-reach-algorithm rloc-probing. Remote-rloc-probe also probes remote RLOCs.
Note This functionality is enabled by default and cannot be disabled. The default interval is 30 seconds. Use the
show run|include other-xtr-probe command to display the configured interval. When an output value is
displayed, the value is configured for something other than the default value. When no output is displayed, it
is configured for the default.
This example shows how to configure the probing period of 86 seconds for probing RLOCs:
RP/0/RSP0/CPU0:router#configure
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1852
Locator/ID Separation Protocol Commands
other-xtr-probe
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#other-xtr-probe period 86
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1853
Locator/ID Separation Protocol Commands
proxy-etr
proxy-etr
To configure a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel Router (PETR), use the proxy-etr
command in LISP address family configuration mode. To remove LISP PETR functionality, use the no form
of this command.
proxy-etr
no proxy-etr
This command has no keywords or arguments.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure PETR functionality under LISP IPv6 on the router:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-afi)#proxy-etr
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1854
Locator/ID Separation Protocol Commands
proxy-etr
Command Description
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache
entries allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-itr, on page 1856 Configures a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel
Router (PITR).
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1855
Locator/ID Separation Protocol Commands
proxy-itr
proxy-itr
To configure a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel Router (PITR), use the proxy-itr
command in LISP address family configuration mode. To remove LISP PITR functionality, use the no form
of this command.
proxy-itr IPv4-source-locator-address
noproxy-itr IPv4-source-locator-address
Syntax Description IPv4-source-locator-address Specifies the IPv4 source locator for PITR.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure LISP PITR functionality on the router:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-afi)#proxy-itr 10.2.3.4
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1856
Locator/ID Separation Protocol Commands
proxy-itr
Command Description
loc-reach-algorithm rloc-probing, on Configures locator reachability algorithm, RLOC Probing, and determines
page 1842 reachability status for other iBGP peers through the IGP domain.
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache
entries allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-etr, on page 1854 Configures a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel
Router (PETR).
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1857
Locator/ID Separation Protocol Commands
remote-rloc-probe
remote-rloc-probe
To configure parameters for probing of remote local routing locators (RLOCs), use the remote-rloc-probe
command in the LISP configuration mode. To return to the default setting, use the no form of this command.
remote-rloc-probe on-route-change
no remote-rloc-probe on-route-change
Syntax Description on-route-change Specifies the probing of the trigger on routing changes for remote RLOCs.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure the remote-rloc-probe command for remote RLOCs:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#remote-rloc-probe on-route-change
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1858
Locator/ID Separation Protocol Commands
router lisp
router lisp
To enter Locator and ID Separation Protocol (LISP) configuration mode, use the router lisp command in
global configuration mode. To remove all LISP configurations and exit the LISP configuration mode, use
the no form of this command.
Syntax Description process-number Specifies the router LISP process number. The range is 0-15.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1859
Locator/ID Separation Protocol Commands
router lisp
Command Description
loc-reach-algorithm rloc-probing, Configures locator reachability algorithm, RLOC Probing, and determines
on page 1842 reachability status for other iBGP peers through the IGP domain.
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache entries
allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-etr, on page 1854 Configures a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel
Router (PETR).
proxy-itr, on page 1856 Configures a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel
Router (PITR).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1860
Locator/ID Separation Protocol Commands
show lisp decapsulation filter
Syntax Description IPv4-rloc-address (Optional) Source RLOC address. If you want to know how a specific IPv4 RLOC
address was configured, use this option.
IPv6-rloc-address (Optional) Source RLOC address. If you want to know how a specific IPv6 RLOC
address was configured, use this option.
eid-table eid-table-vrf (Optional) Specifies the EID table and the associated VRF. Source RLOC addresses
corresponding to the VRF is displayed.
instance-id iid (Optional) Specifies the instance ID. Source RLOC addresses corresponding to the
specified instance ID is displayed.
The following sample output from the show lisp decapsulation filter command displays source
RLOC address configuration details for a specific EID Instance ID. The RLOC address configuration
details (whether it is manually configured or discovered) on a (P)xTR is displayed in the above table.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1861
Locator/ID Separation Protocol Commands
show lisp session
Syntax Description vrf vrf-name (Optional) Specifies the VRF instance. The transport session information for this VRF
instance will be displayed.
session (Optional) Specifies that reliable transport session information is displayed. If there are
multiple transport sessions due to multiple roles, you can view information for all the
sessions.
The following sample output from the show lisp session command displays transport session
information for a LISP VRF instance:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1862
Locator/ID Separation Protocol Commands
show lisp site rloc members
Syntax Description instance-id iid (Optional) Specifies the instance ID for which the RLOC addresses will be displayed.
registrations ((Optional) Specifies that RLOC EID instance membership registration details be displayed.
rloc-address (Optional) IPv4 or IPv6 RLOC address. If you want to view details for a specific RLOC
address, you need to use this option.
The following sample output from the show lisp decapsulation filter command displays source RLOC
address configuration details for a specific EID Instance ID. The RLOC address configuration details
(whether it is manually configured or discovered) on a MS/MR is displayed in the above table.
LISP RLOC membership for EID table default (IID 0), 2 entries
RLOC Origin Valid
10.0.1.2 registration Yes
10.0.2.2 config & registration Yes
The Origin column displays configuration details of the RLOC member. If an RLOC address is
manually configured, automatically gleaned from received registrations, or both, the details are
displayed. The Valid column shows whether the RLOC is a valid member that is distributed to
(P)xTRs. A listed RLOC may not be valid if it is gleaned from registrations but the “override” option
is used in the “modify-discovered” configuration and the specified locator-set does not include the
RLOC.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1863
Locator/ID Separation Protocol Commands
show lisp site
Syntax Description IPv4-dest-EID (Optional) Displays LISP site information matching this destination endpoint identifier
(EID).
IPv4-dest-EID-prefix (Optional) Displays LISP site information matching this destination EID prefix.
IPv6-dest-EID (Optional) Displays LISP site information matching this destination EID.
IPv6-dest-EID-prefix (Optional) Displays LISP site information matching this destination EID prefix.
namesite-name (Optional) Displays LISP site information matching this site name.
detail (Optional) Increases the detail of all displayed LISP site information when no other
parameters are used.
Usage Guidelines This command is used on a LISP map server to display information related to configured LISP sites. The
displayed output indicates, among other things, whether a site is actively registered. When the base form of
the command is used (show lisp site), summary information related to all configured LISP sites is displayed.
When the IPv4-dest-EID form is used, a longest match is done to return the site with the best matching EID
prefix and the displayed information applies specifically to that LISP site. When the IPv4-dest-EID-prefix
form is used, an exact match is done to return the site configured with the EID prefix and the displayed
information applies specifically to that LISP site. When the site-name form is used, the displayed information
contains all EID prefixes configured for the named LISP site. When the detail keyword is added, all available
details for the specific command form are presented.
The following sample output from the show lisp site command displays summary information related
to all configured LISP sites:
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1864
Locator/ID Separation Protocol Commands
show lisp site
Register Registered
site1-xtr 00:00:04 yes 10.0.2.1 192.168.1.0/24
00:00:04 yes 10.0.2.1 2001:DB8:A::/48
site2-xtr 00:00:35 yes 10.0.9.1 192.168.11.0/24
00:00:35 yes 10.0.10.1 2001:DB8:B::/48
map-cache-limit, on page 1844 Configures the maximum limit of IPv4 LISP or IPv6 LISP map-cache entries
allowed to be stored by the router.
map-cache, on page 1845 Configures a static IPv4 EID-to-RLOC or static IPv6 EID-to-RLOC mapping
relationship and its associated traffic policy, or statically configures the
packet handling behavior associated with a destination IPv4 EID-prefix
or a destination IPv6 EID-prefix.
proxy-etr, on page 1854 Configures a router to act as an IPv4 or IPv6 LISP Proxy Egress Tunnel
Router (PETR).
proxy-itr, on page 1856 Configures a router to act as an IPv4 or IPv6 LISP Proxy Ingress Tunnel
Router (PITR).
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1865
Locator/ID Separation Protocol Commands
solicit-map-request
solicit-map-request
To configure the solicit map request (SMR) handling, use the solicit-map-request command in the LISP
address family configuration mode. To disable solicit map request handling, use the no form of this command.
Syntax Description ignore Ignores an IPv4 or IPv6 map-request message that has the solicit-map-request (SMR) bit
set.
max-per-entry Specifies the maximum number of solicit-map-requests (SMRs) for addresses under a
map-cache entry.
number Specifies the maximum number of SMRs. The value ranges from 1 to 100.
suppression-time Specifies how long to suppress repeated solicit-map-requests (SMRs) for the same address.
seconds Specifies the seconds to suppress repeated SMRs for the same address. The value ranges
from 1 to 600.
Command Default
Command Modes LISP IPv4 address family
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
This example shows how to configure the solicit-map-request command to ignore a map-request
message, to specify a maximum number of 50 SMRs, and to specify a suppression time of 500 s:
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-af)#solicit-map-request ignore
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1866
Locator/ID Separation Protocol Commands
solicit-map-request
RP/0/RSP0/CPU0:router(config-lisp-af)#solicit-map-request max-per-entry 50
RP/0/RSP0/CPU0:router(config-lisp-af)#solicit-map-request suppression-time 500
address-family (LISP), on page 1819 Enters Locator ID and separation protocol (LISP) address family
configuration mode.
router lisp, on page 1859 Enters Locator and ID Separation Protocol (LISP) configuration
mode.
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1867
Locator/ID Separation Protocol Commands
use-petr
use-petr
To specify that packets hitting a forward-native map-cache entry should be LISP encapsulated and forwarded
to a PETR, instead of attempting to forward them natively, use the use-petr command in LISP address family
configuration mode. To revert to the default behavior of forwarding packets natively, if they hit a forward-native
map cache entry, use the no form of this command.
Syntax Description ip_address Specifies the IPv4 or IPv6 locator address of the PETR.
priority Specifies the value of the priority assigned to this PETR. This value ranges from 0 to 255. A
lower value indicates a higher priority.
weight Specifies the weight in value of the percentage of traffic to be load-shared. The value ranges
from 0 to 100.
Usage Guidelines To use this command, you must be in a user group associated with a task group that includes appropriate task
IDs. If the user group assignment is preventing you from using a command, contact your AAA administrator
for assistance.
Multiple PETRs can be configured. If you configure a priority and weight for one of them, you must configure
a priority and weight for all of the PETRs.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1868
Locator/ID Separation Protocol Commands
use-petr
This example shows how to configure a fallback PETR. This type of configuration is useful if, by
default, you want to reach your PETR over IPv6, but in case you loose IPv6 connectivity to the
outside world, you fall back to using IPv4. That way, your IPv6 EID prefix will maintain IPv6
connectivity to the outside world regardless of whether or not you have IPv6 connectivity at the ITR.
RP/0/RSP0/CPU0:router#configure
RP/0/RSP0/CPU0:router(config)#router lisp
RP/0/RSP0/CPU0:router(config-lisp)#address-family ipv6 unicast
RP/0/RSP0/CPU0:router(config-lisp-af)# use-petr 2001:db8::1 priority 1 weight 100
RP/0/RSP0/CPU0:router(config-lisp-af)#use-petr 64.10.10.1 priority 2 weight 100
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1869
Locator/ID Separation Protocol Commands
use-petr
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
1870
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-1
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-2
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-3
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-4
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-5
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-6
INDEX
show isis adjacency-log command 788 show protocols (OSPF) command 1154
show isis checkpoint adjacency command 790 show protocols (OSPFv3) command 1316
show isis checkpoint interface command 792 show protocols (RIP) command 1471
show isis checkpoint lsp command 794 show rcc command 1364
show isis command 784 show rib afi-all command 1371
show isis database command 796 show rib attributes command 1373
show isis database-log command 797 show rib client-id command 1374
show isis fast-reroute command 799 show rib clients command 1376
show isis hostname command 802 show rib command 1369
show isis interface command 804 show rib extcomms command 1378
show isis lsp-log command 808 show rib firsthop command 1380
show isis mesh-group command 810 show rib history command 1382
show isis mpls traffic-eng adjacency-log command 812 show rib next-hop command 1384
show isis mpls traffic-eng advertisements command 814 show rib opaques command 1386
show isis mpls traffic-eng tunnel command 817 show rib protocols command 1388
show isis neighbors command 819 show rib recursion-depth-max command 1390
show isis protocol command 822 show rib statistics command 1392
show isis route command 824 show rib tables command 1395
show isis spf-log command 828 show rib trace command 1397
show isis statistics command 835 show rib vpn-attributes command 1399
show isis topology command 839 show rib vrf command 1401
show lcc statistics command 1362 show rip command 1473
show lisp decapsulation filter 1861 show rip database command 1475
show lisp site 1864 show rip interface command 1477
show lisp site rloc members 1863 show rip statistics command 1484
show lpts punt excessive-flow-trap command 478 show route backup command 1409
show ospf border-routers command 1104 show route best-local command 1412
show ospf command 1101 show route command 1403
show ospf database command 1106 show route connected command 1414
show ospf flood-list command 1119 show route local command 1416
show ospf interface command 1121 show route longer-prefixes command 1418
show ospf message-queue command 1129 show route next-hop command 1420
show ospf mpls traffic-eng command 1124 show route quarantined command 1422
show ospf neighbor command 1132 show route resolving-next-hop command 1424
show ospf request-list command 1139 show route static command 1426
show ospf retransmission-list command 1142 show route summary command 1428
show ospf routes command 1144 show rpl active as-path-set command 1664
show ospf sham-links command 1147 show rpl active community-set command 1667
show ospf summary-prefix command 1150 show rpl active extcommunity-set command 1670
show ospf virtual-links command 1152 show rpl active prefix-set command 1673
show ospfv3 border-routers command 1275 show rpl active rd-set command 1676
show ospfv3 command 1269 show rpl active route-policy command 1678
show ospfv3 database command 1277 show rpl as-path-set attachpoints command 1682
show ospfv3 flood-list command 1289 show rpl as-path-set command 1680
show ospfv3 interface command 1291 show rpl as-path-set references command 1685
show ospfv3 message-queue command 1294 show rpl command 1662
show ospfv3 neighbor command 1296 show rpl community-set attachpoints command 1689
show ospfv3 request-list command 1302 show rpl community-set command 1687
show ospfv3 retransmission-list command 1305 show rpl community-set references command 1691
show ospfv3 routes command 1307 show rpl extcommunity-set command 1694
show ospfv3 statistics rib-thread command 1310 show rpl inactive as-path-set command 1697
show ospfv3 summary-prefix command 1312 show rpl inactive community-set command 1700
show ospfv3 virtual-links command 1314 show rpl inactive extcommunity-set command 1703
show protocols (BGP) command 476 show rpl inactive prefix-set command 1706
show protocols (EIGRP) command 934 show rpl inactive rd-set command 1709
show protocols (IS-IS) command 842 show rpl inactive route-policy command 1711
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-7
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-8
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-9
INDEX
Cisco ASR 9000 Series Aggregation Services Router Routing Command Reference, Release 6.1.x
IN-10