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 ne