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
Customer Order Number:
Text Part Number: OL-14356-01
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.
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.
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of
Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step,
Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study,
LightStream, Linksys, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way
to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0711R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Obtaining Documentation and Submitting a Service RequestRC-xiii
Implementing BGP on Cisco IOS XR SoftwareRC-1
ContentsRC-2
Prerequisites for Implementing BGP on Cisco IOS XR SoftwareRC-2
Information About Implementing BGP on Cisco IOS XR SoftwareRC-2
BGP Functional OverviewRC-3
BGP Router IdentifierRC-3
BGP Default LimitsRC-4
BGP Next Hop TrackingRC-5
Autonomous System Number Formats in BGPRC-7
BGP ConfigurationRC-7
No Default Address FamilyRC-19
Routing Policy EnforcementRC-20
Table PolicyRC-21
Update GroupsRC-22
BGP Cost CommunityRC-22
BGP Best Path AlgorithmRC-27
Administrative DistanceRC-30
Multiprotocol BGPRC-32
Route DampeningRC-33
BGP Routing Domain ConfederationRC-34
BGP Route ReflectorsRC-34
Default Address Family for show CommandsRC-37
Distributed BGPRC-37
MPLS VPN Carrier Supporting CarrierRC-38
BGP KeychainsRC-39
IPv6/IPv6 VPN Provider Edge Transport over MPLSRC-39
VPNv4/VPNv6 over the IP Core Using L2TPv3 TunnelsRC-40
How to Implement BGP on Cisco IOS XR SoftwareRC-42
Enabling BGP RoutingRC-44
Configuring a Routing Domain Confederation for BGPRC-47
Cisco IOS XR Routing Configuration Guide
RC-iii
Contents
Resetting an eBGP Session Immediately Upon Link FailureRC-49
Logging Neighbor ChangesRC-49
Adjusting BGP TimersRC-50
Changing the BGP Default Local Preference ValueRC-51
Configuring the MED Metric for BGPRC-53
Configuring BGP WeightsRC-54
Tuning the BGP Best-Path CalculationRC-56
Indicating BGP Back-door RoutesRC-58
Configuring Aggregate AddressesRC-60
Redistributing iBGP Routes into IGPRC-61
Redistributing Prefixes into Multiprotocol BGPRC-63
Configuring BGP Route DampeningRC-66
Applying Policy When Updating the Routing TableRC-71
Setting BGP Administrative DistanceRC-73
Configuring a BGP Neighbor Group and NeighborsRC-74
Configuring a Route Reflector for BGPRC-77
Configuring BGP Route Filtering by Route PolicyRC-79
Configuring BGP Next-hop Trigger DelayRC-81
Disabling Next-hop Processing on BGP UpdatesRC-83
Configuring BGP Community and Extended-Community AdvertisementsRC-84
Configuring the BGP Cost CommunityRC-86
Configuring Software to Store Updates from a NeighborRC-91
Configuring Distributed BGPRC-93
Configuring a VPN Routing and Forwarding Instance in BGPRC-96
Configuring Keychains for BGPRC-114
Configuring an MDT Address Family Session in BGPRC-115
Disabling a BGP NeighborRC-118
Resetting Neighbors Using BGP Inbound Soft ResetRC-120
Resetting Neighbors Using BGP Outbound Soft ResetRC-120
Resetting Neighbors Using BGP Hard ResetRC-121
Clearing Caches, Tables, and DatabasesRC-122
Displaying System and Network StatisticsRC-123
Displaying BGP Process InformationRC-125
Monitoring BGP Update GroupsRC-126
RC-iv
Configuration Examples for Implementing BGP on Cisco IOS XR SoftwareRC-127
BGP MDT Address Family Configuration: ExampleRC-132
Where to Go NextRC-132
Additional ReferencesRC-133
Related DocumentsRC-133
StandardsRC-133
MIBsRC-134
RFCs RC-134
Technical AssistanceRC-134
Implementing EIGRP on Cisco IOS XR SoftwareRC-135
ContentsRC-135
Prerequisites for Implementing EIGRP on Cisco IOS XR SoftwareRC-136
Restrictions for Implementing EIGRP on Cisco IOS XR SoftwareRC-136
Information About Implementing EIGRP on Cisco IOS XR SoftwareRC-136
EIGRP Functional OverviewRC-137
EIGRP FeaturesRC-137
EIGRP ComponentsRC-138
EIGRP Configuration GroupingRC-139
EIGRP Configuration ModesRC-139
EIGRP InterfacesRC-140
Redistribution for an EIGRP ProcessRC-140
Metric Weights for EIGRP RoutingRC-141
Percentage of Link Bandwidth Used for EIGRP PacketsRC-142
Floating Summary Routes for an EIGRP ProcessRC-142
Split Horizon for an EIGRP ProcessRC-144
Adjustment of Hello Interval and Hold Time for an EIGRP ProcessRC-145
Stub Routing for an EIGRP ProcessRC-145
Route Policy Options for an EIGRP ProcessRC-146
EIGRP Layer 3 VPN PE-CE Site-of-OriginRC-147
IPv6 and IPv6 VPN Provider Edge Support over MPLS and IPRC-148
Contents
How to Implement EIGRP on Cisco IOS XR SoftwareRC-148
Enabling EIGRP RoutingRC-149
Configuring Route Summarization for an EIGRP ProcessRC-151
Redistributing Routes for EIGRPRC-153
Creating a Route Policy and Attaching It to an EIGRP ProcessRC-155
Configuring Stub Routing for an EIGRP ProcessRC-158
Configuring EIGRP as a PE-CE ProtocolRC-159
Redistributing BGP Routes into EIGRPRC-161
Monitoring EIGRP RoutingRC-163
Cisco IOS XR Routing Configuration Guide
RC-v
Contents
Configuration Examples for Implementing EIGRP on Cisco IOS XR SoftwareRC-166
Configuring a Basic EIGRP Configuration: ExampleRC-166
Configuring an EIGRP Stub Operation: ExampleRC-167
Configuring an EIGRP PE-CE Configuration with Prefix-Limits: ExampleRC-167
Additional ReferencesRC-168
Related DocumentsRC-168
StandardsRC-168
MIBsRC-168
RFCsRC-168
Technical AssistanceRC-169
Implementing OSPF on Cisco IOS XR SoftwareRC-171
ContentsRC-172
Prerequisites for Implementing OSPF on Cisco IOS XR SoftwareRC-172
Information About Implementing OSPF on Cisco IOS XR SoftwareRC-173
OSPF Functional OverviewRC-173
Key Features Supported in the Cisco IOS XR OSPF ImplementationRC-175
Comparison of Cisco IOS XR OSPFv3 and OSPFv2RC-175
OSPF Hierarchical CLI and CLI InheritanceRC-176
OSPF Routing ComponentsRC-176
OSPF Process and Router IDRC-179
Supported OSPF Network TypesRC-179
Route Authentication Methods for OSPFRC-180
Neighbors and Adjacency for OSPFRC-181
Designated Router (DR) for OSPFRC-181
Default Route for OSPFRC-181
Link-State Advertisement Types for OSPF Version 2RC-181
Link-State Advertisement Types for OSPFv3RC-182
Virtual Link and Transit Area for OSPF RC-183
OSPFv2 Shamlink Support for MPLS VPNRC-184
Route Redistribution for OSPFRC-186
OSPF Shortest Path First ThrottlingRC-186
Nonstop Forwarding for OSPF Version 2RC-187
Graceful Restart for OSPFv3RC-188
Warm Standby and Nonstop Routing for OSPF Version 2RC-190
Multicast-Intact Support for OSPFRC-190
Load Balancing in OSPF Version 2 and OSPFv3RC-191
Multi-Area Adjacency for OSPF Version 2RC-191
Label Distribution Protocol IGP Auto-configuration for OSPFRC-192
OSPF Authentication Message Digest ManagementRC-193
RC-vi
Cisco IOS XR Routing Configuration Guide
GTSM TTL Security Mechanism for OSPFRC-193
Path Computation Element for OSPFv2RC-193
How to Implement OSPF on Cisco IOS XR SoftwareRC-194
Enabling OSPFRC-194
Configuring Stub and Not-So-Stubby Area TypesRC-197
Configuring Neighbors for Nonbroadcast NetworksRC-199
Configuring Authentication at Different Hierarchical Levels for OSPF Version 2RC-204
Controlling the Frequency That the Same LSA Is Originated or Accepted for OSPFRC-207
Creating a Virtual Link with MD5 Authentication to Area 0 for OSPFRC-209
Summarizing Subnetwork LSAs on an OSPF ABRRC-213
Redistributing Routes from One IGP into OSPFRC-215
Configuring OSPF Shortest Path First ThrottlingRC-219
Configuring Nonstop Forwarding Specific to Cisco for OSPF Version 2RC-224
Configuring OSPF Version 2 for MPLS Traffic EngineeringRC-226
Configuring OSPFv3 Graceful RestartRC-230
Configuring an OSPFv2 Sham LinkRC-233
Enabling Nonstop Routing for OSPFv2RC-236
Enabling Multicast-intact for OSPFv2RC-237
Associating Interfaces to a VRFRC-238
Configuring OSPF as a Provider Edge to Customer Edge (PE-CE) ProtocolRC-240
Creating Multiple OSPF Instances (OSPF Process and a VRF)RC-243
Configuring Multi-area AdjacencyRC-244
Configuring Label Distribution Protocol IGP Auto-configuration for OSPFRC-246
Configuring Authentication Message Digest Management for OSPFRC-247
Configuring Generalized TTL Security Mechanism (GTSM) for OSPFRC-251
Verifying OSPF Configuration and OperationRC-254
Contents
Configuration Examples for Implementing OSPF on Cisco IOS XR SoftwareRC-255
Cisco IOS XR for OSPF Version 2 Configuration: ExampleRC-255
CLI Inheritance and Precedence for OSPF Version 2: ExampleRC-257
MPLS TE for OSPF Version 2: ExampleRC-258
ABR with Summarization for OSPFv3: ExampleRC-258
ABR Stub Area for OSPFv3: ExampleRC-258
ABR Totally Stub Area for OSPFv3: ExampleRC-258
Route Redistribution for OSPFv3: ExampleRC-259
Virtual Link Configured Through Area 1 for OSPFv3: ExampleRC-259
Virtual Link Configured with MD5 Authentication for OSPF Version 2: ExampleRC-260
VPN Backbone and Sham Link Configured for OSPF Version 2: ExampleRC-260
Where to Go NextRC-262
Additional ReferencesRC-262
Cisco IOS XR Routing Configuration Guide
RC-vii
Contents
Related DocumentsRC-262
StandardsRC-262
MIBsRC-263
RFCsRC-263
Technical AssistanceRC-264
Implementing IS-IS on Cisco IOS XR SoftwareRC-265
ContentsRC-266
Prerequisites for Implementing IS-IS on Cisco IOS XR SoftwareRC-266
Restrictions for Implementing IS-IS on Cisco IOS XR SoftwareRC-266
Information About Implementing IS-IS on Cisco IOS XR SoftwareRC-266
IS-IS Functional OverviewRC-267
Key Features Supported in the Cisco IOS XR IS-IS ImplementationRC-267
IS-IS Configuration GroupingRC-268
IS-IS Configuration ModesRC-268
IS-IS InterfacesRC-269
Multitopology ConfigurationRC-269
IPv6 Routing and Configuring IPv6 AddressingRC-269
Limit LSP FloodingRC-269
Maximum LSP Lifetime and Refresh IntervalRC-270
Overload Bit Configuration During Multitopology OperationRC-270
Single-Topology IPv6 SupportRC-271
Multitopology IPv6 SupportRC-271
IS-IS AuthenticationRC-271
Nonstop ForwardingRC-272
Multi-Instance IS-ISRC-272
Multiprotocol Label Switching Traffic EngineeringRC-273
Overload Bit on RouterRC-273
Default RoutesRC-273
Attached Bit on an IS-IS InstanceRC-273
IS-IS Support for Route TagsRC-274
Multicast-Intact FeatureRC-274
Multicast Topology Support Using IS-ISRC-275
MPLS Label Distribution Protocol IGP SynchronizationRC-275
Label Distribution Protocol IGP Auto-configurationRC-276
MPLS TE Forwarding AdjacencyRC-276
MPLS TE Interarea TunnelsRC-276
IP Fast RerouteRC-276
RC-viii
How to Implement IS-IS on Cisco IOS XR SoftwareRC-277
Enabling IS-IS and Configuring Level 1 or Level 2 RoutingRC-277
Cisco IOS XR Routing Configuration Guide
Configuring Single Topology for IS-ISRC-280
Configuring Multitopology for IS-ISRC-284
Controlling LSP Flooding for IS-ISRC-285
Configuring Nonstop Forwarding for IS-ISRC-289
Configuring Authentication for IS-ISRC-291
Configuring Keychains for IS-ISRC-293
Configuring MPLS Traffic Engineering for IS-ISRC-295
Tuning Adjacencies for IS-ISRC-298
Setting SPF Interval for a Single-Topology IPv4 and IPv6 ConfigurationRC-301
Customizing Routes for IS-ISRC-303
Configuring MPLS LDP IS-IS SynchronizationRC-306
Enabling Multicast-IntactRC-308
Tagging IS-IS Interface RoutesRC-309
Setting the Priority for Adding Prefixes to the RIBRC-311
Configuring IP Fast Reroute Loop-free AlternateRC-313
Contents
Configuration Examples for Implementing IS-IS on Cisco IOS XR SoftwareRC-314
Configuring Single-Topology IS-IS for IPv6: ExampleRC-315
Configuring Multitopology IS-IS for IPv6: ExampleRC-315
Redistributing IS-IS Routes Between Multiple Instances: ExampleRC-315
Tagging Routes: ExampleRC-316
Where to Go NextRC-316
Additional ReferencesRC-317
Related DocumentsRC-317
StandardsRC-317
MIBsRC-318
RFCsRC-318
Technical AssistanceRC-318
Implementing and Monitoring RIB on Cisco IOS XR SoftwareRC-319
ContentsRC-320
Prerequisites for Implementing RIB on Cisco IOS XR SoftwareRC-320
Information About RIB ConfigurationRC-320
Overview of RIBRC-320
RIB Data Structures in BGP and Other ProtocolsRC-321
RIB Administrative DistanceRC-321
RIB Support for IPv4 and IPv6RC-322
RIB StatisticsRC-322
IPv6 and IPv6 VPN Provider Edge Transport over MPLSRC-322
IP Fast RerouteRC-323
Cisco IOS XR Routing Configuration Guide
RC-ix
Contents
RIB QuarantiningRC-323
How to Deploy and Monitor RIBRC-324
Verifying RIB Configuration Using the Routing TableRC-324
Verifying Networking and Routing ProblemsRC-324
Disabling RIB Next-hop DampeningRC-326
Configuration Examples for RIB MonitoringRC-327
Output of show route Command: ExampleRC-328
Output of show route backup Command: ExampleRC-328
Output of show route best-local Command: ExampleRC-328
Output of show route connected Command: ExampleRC-329
Output of show route local Command: ExampleRC-329
Output of show route longer-prefixes Command: ExampleRC-329
Output of show route next-hop Command: ExampleRC-329
Where to Go NextRC-330
Additional ReferencesRC-330
Related DocumentsRC-331
StandardsRC-331
MIBsRC-332
RFCsRC-332
Technical AssistanceRC-332
Implementing RIP on Cisco IOS XR SoftwareRC-333
ContentsRC-333
Information About Implementing RIP on Cisco IOS XR SoftwareRC-334
Prerequisites for Implementing RIP on Cisco IOS XR SoftwareRC-334
RIP Functional OverviewRC-334
Split Horizon for RIPRC-335
Route Timers for RIPRC-335
Route Redistribution for RIPRC-336
Default Administrative Distances for RIPRC-336
Routing Policy Options for RIPRC-337
How to Implement RIP on Cisco IOS XR SoftwareRC-337
Enabling RIPRC-338
Customize RIPRC-339
Control Routing InformationRC-342
Creating a Route Policy for RIPRC-344
Configuration Examples for Implementing RIP on Cisco IOS XR SoftwareRC-347
Configuring a Basic RIP Configuration: ExampleRC-347
Configuring RIP on the Provider Edge: ExampleRC-348
RC-x
Cisco IOS XR Routing Configuration Guide
Adjusting RIP Timers for each VRF Instance: ExampleRC-348
Configuring Redistribution for RIP: ExampleRC-349
Configuring Route Policies for RIP: ExampleRC-349
Configuring Passive Interfaces and Explicit Neighbors for RIP: ExampleRC-350
Controlling RIP Routes: ExampleRC-350
Additional ReferencesRC-350
Related DocumentsRC-351
StandardsRC-351
MIBsRC-351
RFCsRC-351
Technical AssistanceRC-352
Implementing Routing Policy on Cisco IOS XR SoftwareRC-353
ContentsRC-354
Prerequisites for Implementing Routing Policy on Cisco IOS XR SoftwareRC-354
Contents
Information About Implementing Routing Policy on Cisco IOS XR SoftwareRC-354
How to Implement Static Routes on Cisco IOS XR SoftwareRC-424
Configuring a Static RouteRC-424
Configuring a Floating Static RouteRC-425
Configuring Static Routes Between PE-CE RoutersRC-427
Changing the Maximum Number of Allowable Static RoutesRC-429
Associating a VRF with a Static RouteRC-430
Configuration ExamplesRC-432
Configuring Traffic Discard: ExampleRC-432
Configuring a Fixed Default Route: ExampleRC-432
Configuring a Floating Static Route: ExampleRC-432
Configuring a Static Route Between PE-CE Routers: ExampleRC-432
Where to Go NextRC-433
Additional ReferencesRC-433
Related DocumentsRC-433
StandardsRC-433
MIBsRC-434
RFCsRC-434
Technical AssistanceRC-434
RC-xii
Index
Cisco IOS XR Routing Configuration Guide
Preface
The Cisco IOS XR Routing Configuration Guide provides information and procedures related to routing
on Cisco IOS XR software.
The preface contains the following sections:
• Changes to This Document
• Obtaining Documentation and Submitting a Service Request
Changes to This Document
Table 1 lists the technical changes made to this document since it was first printed.
Table 1Changes to This Document
RevisionDateChange Summary
OL-14356-01December 2007Initial release of this document.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
OL-14356-01
Cisco IOS XR Routing Configuration Guide
RC-xiii
Preface
RC-xiv
Cisco IOS XR Routing Configuration Guide
OL-14356-01
Implementing BGP on Cisco IOS XR Software
Border Gateway Protocol (BGP) is an Exterior Gateway Protocol (EGP) that allows you to create
loop-free interdomain routing between autonomous systems. An autonomous system is a set of routers
under a single technical administration. Routers in an autonomous system can use multiple Interior
Gateway Protocols (IGP) to exchange routing information inside the autonomous system and an EGP to
route packets outside the autonomous system.
This module provides the conceptual and configuration information for BGP on Cisco IOS XR software.
NoteFor more information about BGP on the Cisco IOS XR software and complete descriptions of the BGP
commands listed in this module, you can see the “Related Documents” section of this module. To locate
documentation for other commands that might appear while performing a configuration task, search
online in the Cisco IOS XR software master command index.
Feature History for Implementing BGP on Cisco IOS XR Software
ReleaseModification
Release 2.0 This feature was introduced on the Cisco CRS-1.
Release 3.0No modification.
Release 3.2Support was added for the Cisco XR 12000 Series Router.
Release 3.3.0VPN routing and forwarding (VRF) support was added, including
information on VRF command modes and command syntax.
OL-14356-01
BGP cost community information was added.
Release 3.4.0The following features were supported:
• Four-byte autonomous system (AS) number
• Carrier supporting carrier (CSC) for BGP was added. See
Cisco IOS XR Multiprotocol Label Switching Protocol Configuration
Guide for information
• Key chains
Cisco IOS XR Routing Configuration Guide
RC-1
Contents
Contents
Implementing BGP on Cisco IOS XR Software
Release 3.5.0The following features were supported:
• IPv6 Provider Edge and IPv6 VPN Provider Edge over Multiprotocol
Label Switching
• Neighbor-specific VRF IPv6 address family configurations
• Address family group-specific VPNv6 configurations
• VPN4/VPNv6 over IP Core using L2TPv3 Tunnels
• Multicast Distribution Tree (MDT) Subaddress Family Identifier
Information (SAFI) support for Multicast VPN (MVPN)
Release 3.6.0No modification.
• Prerequisites for Implementing BGP on Cisco IOS XR Software, page RC-2
• Information About Implementing BGP on Cisco IOS XR Software, page RC-2
• How to Implement BGP on Cisco IOS XR Software, page RC-42
• Configuration Examples for Implementing BGP on Cisco IOS XR Software, page RC-127
• Where to Go Next, page RC-132
• Additional References, page RC-133
Prerequisites for Implementing BGP on Cisco IOS XR Software
You must be in a user group associated with a task group that includes the proper task IDs for BGP
commands. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Information About Implementing BGP on Cisco IOS XR Software
To implement BGP, you need to understand the following concepts:
• BGP Functional Overview, page RC-3
• BGP Router Identifier, page RC-3
• BGP Default Limits, page RC-4
• BGP Next Hop Tracking, page RC-5
• Autonomous System Number Formats in BGP, page RC-7
• BGP Configuration, page RC-7
• No Default Address Family, page RC-19
RC-2
• Routing Policy Enforcement, page RC-20
• Table Policy, page RC-21
• Update Groups, page RC-22
• BGP Best Path Algorithm, page RC-27
Cisco IOS XR Routing Configuration Guide
OL-14356-01
Implementing BGP on Cisco IOS XR Software
• Administrative Distance, page RC-30
• Administrative Distance, page RC-30
• Multiprotocol BGP, page RC-32
• Route Dampening, page RC-33
• BGP Routing Domain Confederation, page RC-34
• BGP Route Reflectors, page RC-34
• Default Address Family for show Commands, page RC-37
• Distributed BGP, page RC-37
• MPLS VPN Carrier Supporting Carrier, page RC-38
• BGP Keychains, page RC-39
• IPv6/IPv6 VPN Provider Edge Transport over MPLS, page RC-39
• VPNv4/VPNv6 over the IP Core Using L2TPv3 Tunnels, page RC-40
BGP Functional Overview
Information About Implementing BGP on Cisco IOS XR Software
BGP uses TCP as its transport protocol. Two BGP routers form a TCP connection between one another
(peer routers) and exchange messages to open and confirm the connection parameters.
BGP routers exchange network reachability information. This information is mainly an indication of the
full paths (BGP autonomous system numbers) that a route should take to reach the destination network.
This information helps construct a graph that shows which autonomous systems are loop free and where
routing policies can be applied to enforce restrictions on routing behavior.
Any two routers forming a TCP connection to exchange BGP routing information are called peers or
neighbors. BGP peers initially exchange their full BGP routing tables. After this exchange, incremental
updates are sent as the routing table changes. BGP keeps a version number of the BGP table, which is
the same for all of its BGP peers. The version number changes whenever BGP updates the table due to
routing information changes. Keepalive packets are sent to ensure that the connection is alive between
the BGP peers and notification packets are sent in response to error or special conditions.
NoteFor information on configuring BGP to distribute Multiprotocol Label Switching (MPLS) Layer 3
NoteFor information on BGP support for Bidirectional Forwarding Detection (BFD), see Cisco IOS XR
Interface and Hardware Configuration Guide and Cisco IOS XR Interface and Hardware Command
Reference.
BGP Router Identifier
For BGP sessions between neighbors to be established, BGP must be assigned a router ID. The router
ID is sent to BGP peers in the OPEN message when a BGP session is established.
BGP attempts to obtain a router ID in the following ways (in order of preference):
OL-14356-01
Cisco IOS XR Routing Configuration Guide
RC-3
Information About Implementing BGP on Cisco IOS XR Software
• By means of the address configured using the bgp router-id command in router configuration mode.
• By using the highest IPv4 address on a loopback interface in the system if the router is booted with
saved loopback address configuration.
• By using the primary IPv4 address of the first loopback address that gets configured if there are not
any in the saved configuration.
If none of these methods for obtaining a router ID succeeds, BGP does not have a router ID and cannot
establish any peering sessions with BGP neighbors. In such an instance, an error message is entered in
the system log, and the show bgp summary command displays a router ID of 0.0.0.0.
After BGP has obtained a router ID, it continues to use it even if a better router ID becomes available.
This usage avoids unnecessary flapping for all BGP sessions. However, if the router ID currently in use
becomes invalid (because the interface goes down or its configuration is changed), BGP selects a new
router ID (using the rules described) and all established peering sessions are reset.
NoteWe strongly recommend that the bgp router-id command is configured to prevent unnecessary changes
to the router ID (and consequent flapping of BGP sessions).
Implementing BGP on Cisco IOS XR Software
BGP Default Limits
Cisco IOS XR BGP imposes maximum limits on the number of neighbors that can be configured on the
router and on the maximum number of prefixes that are accepted from a peer for a given address family.
This limitation safeguards the router from resource depletion caused by misconfiguration, either locally
or on the remote neighbor. The following limits apply to BGP configurations:
• The default maximum number of peers that can be configured is 4000. The default can be changed
using the bgp maximum neighbor command. The limit range is 1 to 15000. Any attempt to
configure additional peers beyond the maximum limit or set the maximum limit to a number that is
less than the number of peers currently configured will fail.
• To prevent a peer from flooding BGP with advertisements, a limit is placed on the number of
prefixes that are accepted from a peer for each supported address family. The default limits can be
overridden through configuration of the maximum-prefix limit command for the peer for the
appropriate address family. The following default limits are used if the user does not configure the
maximum number of prefixes for the address family:
–
–
–
–
–
–
512K (524,288) prefixes for IPv4 unicast.
128K (131,072) prefixes for IPv4 multicast.
128K (131,072) prefixes for IPv6 unicast.
128K (131,072) prefixes for IPv6 multicast
512K (524,288) prefixes for VPNv4 unicast
512K (524,288) prefixes for VPNv6 unicast
RC-4
A cease notification message is sent to the neighbor and the peering with the neighbor is terminated
when the number of prefixes received from the peer for a given address family exceeds the maximum
limit (either set by default or configured by the user) for that address family.
It is possible that the maximum number of prefixes for a neighbor for a given address family has been
configured after the peering with the neighbor has been established and a certain number of prefixes have
already been received from the neighbor for that address family. A cease notification message is sent to
Cisco IOS XR Routing Configuration Guide
OL-14356-01
Implementing BGP on Cisco IOS XR Software
the neighbor and peering with the neighbor is terminated immediately after the configuration if the
configured maximum number of prefixes is fewer than the number of prefixes that have already been
received from the neighbor for the address family.
BGP Next Hop Tracking
BGP receives notifications from the Routing Information Base (RIB) when next-hop information
changes (event-driven notifications). BGP obtains next-hop information from the RIB to:
• Determine whether a next hop is reachable.
• Find the fully recursed IGP metric to the next hop (used in the best-path calculation).
• Validate the received next hops.
• Calculate the outgoing next hops.
• Verify the reachability and connectedness of neighbors.
BGP is notified when any of the following events occurs:
• Next hop becomes unreachable
Information About Implementing BGP on Cisco IOS XR Software
• Next hop becomes reachable
• Fully recursed IGP metric to the next hop changes
• First hop IP address or first hop interface change
• Next hop becomes connected
• Next hop becomes unconnected
• Next hop becomes a local address
• Next hop becomes a nonlocal address
NoteReachability and recursed metric events trigger a best-path recalculation.
Event notifications from the RIB are classified as critical and noncritical. Notifications for critical and
noncritical events are sent in separate batches. However, a noncritical event is sent along with the critical
events if the noncritical event is pending and there is a request to read the critical events.
• Critical events are related to the reachability (reachable and unreachable), connectivity (connected
and unconnected), and locality (local and nonlocal) of the next hops. Notifications for these events
are not delayed.
• Noncritical events include only the IGP metric changes. These events are sent at an interval of 3
seconds. A metric change event is batched and sent 3 seconds after the last one was sent.
The next-hop trigger delay for critical and noncritical events can be configured to specify a minimum
batching interval for critical and noncritical events using the nexthop trigger-delay command. The
trigger delay is address family dependent.
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.
OL-14356-01
• 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.
Cisco IOS XR Routing Configuration Guide
RC-5
Information About Implementing BGP on Cisco IOS XR Software
This route policy filtering is possible because RIB identifies the source protocol of route that resolved a
next hop as well as the mask length associated with the route. The nexthop route-policy command is
used to specify the route-policy.
For information on route policy filtering for next hops using the next-hop attach point, see the
Implementing Routing Policy Language on Cisco IOS XR Software module of Cisco IOS XR Routing
Configuration Guide.
Scoped IPv4/VPNv4 Table Walk
To determine which address family to process, a next-hop notification is received by first dereferencing
the gateway context associated with the next hop, then looking into the gateway context to determine
which address families are using the gateway context. The IPv4 unicast and VPNv4 unicast address
families share the same gateway context, because they are registered with the IPv4 unicast table in the
RIB. As a result, both the global IPv4 unicast table and the VPNv4 table are processed when an IPv4
unicast next-hop notification is received from the RIB. A mask is maintained in the next hop, indicating
whether the next hop belongs to IPv4 unicast or VPNv4 unicast, or both. This scoped table walk localizes
the processing in the appropriate address family table.
Implementing BGP on Cisco IOS XR Software
Reordered Address Family Processing
The Cisco IOS XR software walks address family tables based on the numeric value of the address
family. When a next-hop notification batch is received, the order of address family processing is
reordered to the following order:
• IPv4 tunnel
• VPNv4 unicast
• VPNv6 unicast
• IPv4 labeled unicast
• IPv4 unicast
• IPv4 MDT
• IPv4 multicast
• IPv6 unicast
• IPv6 multicast
• IPv6 labeled unicast
New Thread for Next-Hop Processing
The critical-event thread in the spkr process handles only next-hop, Bidirectional Forwarding Detection
(BFD), and fast-external-failover (FEF) notifications. This critical-event thread ensures that BGP
convergence is not adversely impacted by other events that may take a significant amount of time.
show, clear, and debug Commands
The show bgp nexthops command provides statistical information about next-hop notifications, the
amount of time spent in processing those notifications, and details about each next hop registered with
the RIB. The clear bgp nexthop performance-statistics command ensures that the cumulative statistics
associated with the processing part of the next-hop show command can be cleared to help in monitoring.
Cisco IOS XR Routing Configuration Guide
RC-6
OL-14356-01
Implementing BGP on Cisco IOS XR Software
The clear bgp nexthop registration command performs an asynchronous registration of the next hop
with the RIB. See the BGP Commands on Cisco IOS XR Software module of Cisco IOS XR Routing Commands for information on the next-hop show and clear commands.
The debug bgp nexthop command displays information on next-hop processing. The
provides debug information only about BGP registration of next hops with RIB. The in keyword displays
debug information about next-hop notifications received from RIB. The out keyword displays debug
information about next-hop notifications sent to the RIB. See BGP Debug Commands on Cisco IOS XR Software.
Autonomous System Number Formats in BGP
Autonomous system numbers (ASNs) are globally unique identifiers used to identify autonomous
systems (ASs) and enable ASs to exchange exterior routing information between neighboring ASs. A
unique ASN is allocated to each AS for use in BGP routing.
Currently, ASNs are encoded as 2-byte numbers in BGP. The 2-byte range is 1 to 65535. To prepare for
the eventual exhaustion of 2-byte ASNs, BGP has the capability to support 4-byte ASNs. The 4-byte
range is 1.0 to 65535.65535 and the format is high-order 16-bit value in decimal . low-order 16-bit value in decimal. The BGP 4-byte ASN capability is used to propagate 4-byte-based AS path information
across BGP speakers that do not support 4-byte AS numbers. This capability allows for the gradual
transition from 2-byte ASNs to 4-byte ASNs. See draft-ietf-idr-as4bytes-12.txt for information on
increasing the size of an ASN from 2 bytes to 4 bytes.
Information About Implementing BGP on Cisco IOS XR Software
out keyword
BGP Configuration
Cisco IOS XR BGP follows a neighbor-based configuration model that requires that all configurations
for a particular neighbor be grouped in one place under the neighbor configuration. Peer groups are not
supported for either sharing configuration between neighbors or for sharing update messages. The
concept of peer group has been replaced by a set of configuration groups to be used as templates in BGP
configuration and automatically generated update groups to share update messages between neighbors.
BGP configurations are grouped into four major categories:
• Router Configuration Mode, page RC-8
• Router Address Family Configuration Mode, page RC-8
• Neighbor Configuration Mode, page RC-8
• Neighbor Address Family Configuration Mode, page RC-8
• VRF Configuration Mode, page RC-8
• VRF Address Family Configuration Mode, page RC-8
• VRF Neighbor Configuration Mode, page RC-8
• VRF Neighbor Address Family Configuration Mode, page RC-9
Configuration Modes
The following sections show how to enter some of the configuration modes. From a mode, you can enter
the ? command to display the commands available in that mode.
OL-14356-01
Cisco IOS XR Routing Configuration Guide
RC-7
Information About Implementing BGP on Cisco IOS XR Software
Router Configuration Mode
The following example shows how to enter router configuration mode:
Information About Implementing BGP on Cisco IOS XR Software
Neighbor Submode
Cisco IOS XR BGP uses a neighbor submode to make it possible to enter configurations without having
to prefix every configuration with the neighbor keyword and the neighbor address:
• Cisco IOS XR software has a submode available for neighbors in which it is not necessary for every
command to have a “neighbor x.x.x.x” prefix:
In Cisco IOS XR software, the configuration is as follows:
• You must enter neighbor-specific IPv4 and IPv6 commands in VRF neighbor address-family
configuration submode. In Cisco IOS XR software, the configuration is as follows:
RP/0/RP0/CPU0:router(config)# router bgp 110
Cisco IOS XR Routing Configuration Guide
RC-9
Information About Implementing BGP on Cisco IOS XR Software
RP/0/RP0/CPU0:router(config-bgp)# vrf vrf_A
RP/0/RP0/CPU0:router(config-bgp-vrf)# neighbor 11.0.1.2
RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# address-family ipv4 unicast
RP/0/RP0/CPU0:router(config-bgp-vrf-nbr-af)# route-policy pass all in
Configuration Templates
The af-group, session-group, and neighbor-group configuration commands provide template support
for the neighbor configuration in Cisco IOS XR software:
The af-group command is used to group address family-specific neighbor commands within an IPv4,
IPv6, VPNv4, or VPNv6 address family. Neighbors that have the same address family configuration are
able to use the address family group (af-group) name for their address family-specific configuration. A
neighbor inherits the configuration from an address family group by way of the use command. If a
neighbor is configured to use an address family group, the neighbor (by default) inherits the entire
configuration from the address family group. However, a neighbor does not inherit all of the
configuration from the address family group if items are explicitly configured for the neighbor. The
address family group configuration is entered under the BGP router configuration mode. The following
example shows how to enter address family group configuration mode.
The session-group command allows you to create a session group from which neighbors can inherit
address family-independent configuration. A neighbor inherits the configuration from a session group
by way of the use command. If a neighbor is configured to use a session group, the neighbor (by default)
inherits the entire configuration of the session group. A neighbor does not inherit all of the configuration
from a session group if a configuration is done directly on that neighbor. The following example shows
how to enter session group configuration mode:
The neighbor-group command helps you apply the same configuration to one or more neighbors.
Neighbor groups can include session groups and address family groups and can comprise the complete
configuration for a neighbor. After a neighbor group is configured, a neighbor can inherit the
configuration of the group using the use command. If a neighbor is configured to use a neighbor group,
the neighbor inherits the entire BGP configuration of the neighbor group.
The following example shows how to enter neighbor group configuration mode:
• However, a neighbor does not inherit all of the configuration from the neighbor group if items are
explicitly configured for the neighbor. In addition, some part of the configuration of the neighbor
group could be hidden if a session group or address family group was also being used.
Cisco IOS XR Routing Configuration Guide
OL-14356-01
Implementing BGP on Cisco IOS XR Software
Configuration grouping has the following effects in Cisco IOS XR software:
• Commands entered at the session group level define address family-independent commands (the
same commands as in the neighbor submode).
• Commands entered at the address family group level define address family-dependent commands
for a specified address family (the same commands as in the neighbor-address family configuration
submode).
• Commands entered at the neighbor group level define address family-independent commands and
address family-dependent commands for each address family (the same as all available neighbor
commands), and define the use command for the address family group and session group commands.
Template Inheritance Rules
In Cisco IOS XR software, BGP neighbors or groups inherit configuration from other configuration
groups.
For address family-independent configurations:
• Neighbors can inherit from session groups and neighbor groups.
• Neighbor groups can inherit from session groups and other neighbor groups.
Information About Implementing BGP on Cisco IOS XR Software
• Session groups can inherit from other session groups.
• If a neighbor uses a session group and a neighbor group, the configurations in the session group are
preferred over the global address family configurations in the neighbor group.
For address family-dependent configurations:
• Address family groups can inherit from other address family groups.
• Neighbor groups can inherit from address family groups and other neighbor groups.
• Neighbors can inherit from address family groups and neighbor groups.
Configuration group inheritance rules are numbered in order of precedence as follows:
1. If the item is configured directly on the neighbor, that value is used. In the example that follows, the
advertisement interval is configured both on the neighbor group and neighbor configuration and the
advertisement interval being used is from the neighbor configuration:
The following output from the show bgp neighbors command shows that the advertisement interval
used is 20 seconds:
RP/0/RP0/CPU0:router# show bgp neighbors 10.1.1.1
OL-14356-01
BGP neighbor is 10.1.1.1, remote AS 1, local AS 140, external link
Remote router ID 0.0.0.0
BGP state = Idle
Last read 00:00:00, hold time is 180, keepalive interval is 60 seconds
Received 0 messages, 0 notifications, 0 in queue
Sent 0 messages, 0 notifications, 0 in queue
Minimum time between advertisement runs is 20 seconds
Cisco IOS XR Routing Configuration Guide
RC-11
Information About Implementing BGP on Cisco IOS XR Software
For Address Family: IPv4 Unicast
BGP neighbor version 0
Update group: 0.1
eBGP neighbor with no inbound or outbound policy; defaults to 'drop'
Route refresh request: received 0, sent 0
0 accepted prefixes
Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288
Threshold for warning message 75%
Connections established 0; dropped 0
Last reset 00:00:14, due to BGP neighbor initialized
External BGP neighbor not directly connected.
2. Otherwise, if the neighbor uses a session group or address family group, the configuration value is
obtained from the session group or address family group. If the address family group or session
group has a parent and an item is configured on the parent, the parent configuration is used. If the
item is not configured on the parent but is configured on the parent of the parent, the configuration
of the parent of the parent is used, and so on. In the example that follows, the advertisement interval
is configured on a neighbor group and a session group and the advertisement interval value being
used is from the session group:
The following output from the show bgp neighbors command shows that the advertisement interval
used is 15 seconds:
RP/0/RP0/CPU0:router# show bgp neighbors 192.168.0.1
BGP neighbor is 192.168.0.1, remote AS 1, local AS 140, external link
Remote router ID 0.0.0.0
BGP state = Idle
Last read 00:00:00, hold time is 180, keepalive interval is 60 seconds
Received 0 messages, 0 notifications, 0 in queue
Sent 0 messages, 0 notifications, 0 in queue
Minimum time between advertisement runs is 15 seconds
For Address Family: IPv4 Unicast
BGP neighbor version 0
Update group: 0.1
eBGP neighbor with no inbound or outbound policy; defaults to 'drop'
Route refresh request: received 0, sent 0
0 accepted prefixes
Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288
Threshold for warning message 75%
Connections established 0; dropped 0
Last reset 00:03:23, due to BGP neighbor initialized
External BGP neighbor not directly connected.
RC-12
Cisco IOS XR Routing Configuration Guide
OL-14356-01
Implementing BGP on Cisco IOS XR Software
3. Otherwise, if the neighbor uses a neighbor group and does not use a session group or address family
group, the configuration value can be obtained from the neighbor group either directly or through
inheritance. In the example that follows, the advertisement interval from the neighbor group is used
because it is not configured directly on the neighbor and no session group is used:
The following output from the show bgp neighbors command shows that the advertisement interval
used is 15 seconds:
RP/0/RP0/CPU0:router# show bgp neighbors 192.168.1.1
BGP neighbor is 192.168.2.2, remote AS 1, local AS 140, external link
Remote router ID 0.0.0.0
BGP state = Idle
Last read 00:00:00, hold time is 180, keepalive interval is 60 seconds
Received 0 messages, 0 notifications, 0 in queue
Sent 0 messages, 0 notifications, 0 in queue
Minimum time between advertisement runs is 15 seconds
Information About Implementing BGP on Cisco IOS XR Software
For Address Family: IPv4 Unicast
BGP neighbor version 0
Update group: 0.1
eBGP neighbor with no outbound policy; defaults to 'drop'
Route refresh request: received 0, sent 0
Inbound path policy configured
Policy for incoming advertisements is POLICY_1
0 accepted prefixes
Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288
Threshold for warning message 75%
Connections established 0; dropped 0
Last reset 00:01:14, due to BGP neighbor initialized
External BGP neighbor not directly connected.
To illustrate the same rule, the following example shows how to set the advertisement interval to 15
(from the session group) and 25 (from the neighbor group). The advertisement interval set in the
session group overrides the one set in the neighbor group. The inbound policy is set to POLICY_1
from the neighbor group.
Information About Implementing BGP on Cisco IOS XR Software
RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group ADV
RP/0/RP0/CPU0:router(config-bgp-nbr)# use neighbor-group TIMER
The following output from the show bgp neighbors command shows that the advertisement interval
used is 15 seconds:
RP/0/RP0/CPU0:router# show bgp neighbors 192.168.2.2
BGP neighbor is 192.168.2.2, remote AS 1, local AS 140, external link
Remote router ID 0.0.0.0
BGP state = Idle
Last read 00:00:00, hold time is 180, keepalive interval is 60 seconds
Received 0 messages, 0 notifications, 0 in queue
Sent 0 messages, 0 notifications, 0 in queue
Minimum time between advertisement runs is 15 seconds
For Address Family: IPv4 Unicast
BGP neighbor version 0
Update group: 0.1
eBGP neighbor with no inbound or outbound policy; defaults to 'drop'
Route refresh request: received 0, sent 0
0 accepted prefixes
Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288
Threshold for warning message 75%
Implementing BGP on Cisco IOS XR Software
Connections established 0; dropped 0
Last reset 00:02:03, due to BGP neighbor initialized
External BGP neighbor not directly connected.
4. Otherwise, the default value is used. In the example that follows, neighbor 10.0.101.5 has the
minimum time between advertisement runs set to 30 seconds (default) because the neighbor is not
configured to use the neighbor configuration or the neighbor group configuration:
The following output from the show bgp neighbors command shows that the advertisement interval
used is 30 seconds:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.5
BGP neighbor is 10.0.101.5, remote AS 1, local AS 140, external link
Remote router ID 0.0.0.0
BGP state = Idle
Last read 00:00:00, hold time is 180, keepalive interval is 60 seconds
Received 0 messages, 0 notifications, 0 in queue
Sent 0 messages, 0 notifications, 0 in queue
Minimum time between advertisement runs is 30 seconds
RC-14
For Address Family: IPv4 Unicast
BGP neighbor version 0
Update group: 0.2
eBGP neighbor with no inbound or outbound policy; defaults to 'drop'
Cisco IOS XR Routing Configuration Guide
OL-14356-01
Implementing BGP on Cisco IOS XR Software
Route refresh request: received 0, sent 0
0 accepted prefixes
Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288
Threshold for warning message 75%
Connections established 0; dropped 0
Last reset 00:00:25, due to BGP neighbor initialized
External BGP neighbor not directly connected.
The inheritance rules used when groups are inheriting configuration from other groups are the same
as the rules given for neighbors inheriting from groups.
Template Inheritance
You can use the following show commands described to monitor BGP inheritance information:
• show bgp neighbors, page RC-15
• show bgp af-group, page RC-16
• show bgp session-group, page RC-17
• show bgp neighbor-group, page RC-18
Information About Implementing BGP on Cisco IOS XR Software
show bgp neighbors
Use the show bgp neighbors command to display information about the BGP configuration for
neighbors.
• Use the configuration keyword to display the effective configuration for the neighbor, including any
settings that have been inherited from session groups, neighbor groups, or address family groups
used by this neighbor.
• Use the inheritance keyword to display the session groups, neighbor groups, and address family
groups from which this neighbor is capable of inheriting configuration.
The show bgp neighbors command examples that follow are based on the sample configuration:
Information About Implementing BGP on Cisco IOS XR Software
The following example displays sample output from the show bgp neighbors command using the
inheritance keyword. The example shows that the neighbor inherits session parameters from neighbor
group GROUP_1, which in turn inherits from session group GROUP_2. The neighbor inherits IPv4
unicast parameters from address family group GROUP_3 and IPv4 multicast parameters from neighbor
group GROUP_1:
RP/0/RP0/CPU0:router# show bgp neighbors 192.168.0.1 inheritance
The following example displays sample output from the show bgp neighbors command using the
configuration keyword. The example shows from where each item of configuration was inherited, or if
it was configured directly on the neighbor (indicated by [ ]). For example, the ebgp-multihop 3
command was inherited from neighbor group GROUP_1 and the next-hop-self command was inherited
from the address family group GROUP_3:
RP/0/RP0/CPU0:router# show bgp neighbors 192.168.0.1 configuration