-
Cisco IOS XR Routing Command Reference, Release 3.7
-
Preface
-
BGP Commands on Cisco IOS XR Software
-
EIGRP Commands on Cisco IOS XR Software
-
IS-IS Commands on Cisco IOS XR Software
-
OSPFv3 Commands on Cisco IOS XR Software
-
OSPF Commands on Cisco IOS XR Software
-
Routing Policy Commands on Cisco IOS XR Software
-
RIB Commands on Cisco IOS XR Software
-
RIP Commands on Cisco IOS XR Software
-
Static Routing Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
BGP Commands on Cisco IOS XR Software
bgp auto-policy-soft-reset disable
bgp bestpath cost-community ignore
bgp bestpath med missing-as-worst
bgp client-to-client reflection disable
bgp fast-external-fallover disable
bgp graceful-restart graceful-reset
bgp graceful-restart purge-time
bgp graceful-restart restart-time
bgp graceful-restart stalepath-time
bgp log neighbor changes disable
clear bgp nexthop performance-statistics
clear bgp nexthop registration
clear bgp performance-statistics
default-information originate (BGP)
show bgp truncated-communities
BGP Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor Border Gateway Protocol (BGP) for IP Version 4 (IPv4), IP Version 6 (IPv6), Virtual Private Network Version 4 (VPNv4), Virtual Private Network Version 6 (VPNv6), and multicast distribution tree (MDT) routing sessions.
For detailed information about BGP concepts, configuration tasks, and examples, see Implementing BGP on Cisco IOS XR Software in Cisco IOS XR Routing Configuration Guide.
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 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
no address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
Syntax Description
Defaults
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.
Command Modes
Router configuration
Neighbor configuration
Neighbor group configuration
VRF configuration
VRF neighbor configuration (IPv4 address families)Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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. The IPv6 unicast address family must be configured in router configuration mode before configuring the IPv6 labeled-unicast address family for a neighbor in neighbor configuration mode. See Table 1.
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, multicast, labeled-unicast, and VPNv4 unicast address families. IPv6 neighbor sessions support IPv6 unicast and multicast address families.
Task ID
Examples
The following example shows how to place the router in global address family configuration mode for the IPv4 address family:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/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/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-af)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)#The following example shows how to place the router in global address family configuration mode for the IPv4 address family:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 12RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 tunnelRP/0/RP0/CPU0:router(config-bgp-af)#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
Defaults
Default minimum interval:
For internal BGP (iBGP) peers is 0 seconds
For external BGP (eBGP) peers is 30 seconds
For customer edge (CE) peers is 0 secondsCommand Modes
Neighbor configuration
Neighbor group configuration
Session group configuration
VRF neighbor configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to set the minimum time between sending BGP routing updates to 10 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 5RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100RP/0/RP0/CPU0:router(config-bgp-nbr)# advertisement-interval 10Related Commands
Creates a neighbor group and enters neighbor group configuration mode.
Creates a session group and enters session group configuration mode.
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.
af-group af-group-name address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
no af-group af-group-name address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
Syntax Description
Defaults
No BGP address family group is configured.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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.
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-selfRelated Commands
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.
aggregate-address address/mask-length [as-set] [as-confed-set] [summary-only] [route-policy route-policy-name]
no aggregate-address address/mask-length [as-set] [as-confed-set] [summary-only] [route-policy route-policy-name]
Syntax Description
Defaults
When you do not specify this command, no aggregate entry is created in the BGP routing table.
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.)
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.
Task ID
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.
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# aggregate-address 10.0.0.0/8 as-setRelated Commands
allocate-label
To allocate Multiprotocol Label Switching (MPLS) labels for specific IPv4 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 labeled-unicast 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.
allocate-label {route-policy route-policy-name | all}
no allocate-label {route-policy route-policy-name | all}
Syntax Description
Defaults
No default behavior or values
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 Cisco IOS XR Multiprotocol Label Switching Configuration Guide for information on using the allocate-label command for L3VPN inter-AS deployments and carrier-supporting-carrier IPv4 BGP label distribution.
Task ID
Examples
The following example shows how to enable allocating labels for IPv4 routes:
RP/0/0/CPU0:router(config)# router bgp 6RP/0/0/CPU0:router(config-bgp)# address family ipv4 unicastRP/0/0/CPU0:router(config-bgp-af)# allocate-label route-policy policy_Aallowas-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
Defaults
No default behavior or values
Command Modes
Address family group configuration
Neighbor address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Hub and spoke VPN networks require looping back of routing information to the hub PE through the hub customer edge (CE). See Cisco IOS XR Multiprotocol Label Switching Configuration Guide 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.
Task ID
Examples
The following example shows how to allow five occurrences of the PE ASN:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# af-group group_1 address-family vpnv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# allowas-in 5as-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 in VRF neighbor address family configuration mode. To restore the system to its default condition, use the no form of this command.
as-override [disable]
no as-override [disable]
Syntax Description
Defaults
Automatic override of the ASN is disabled.
Command Modes
VRF neighbor address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure an ASN override:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# vrf vrf_ARP/0/RP0/CPU0:router(config-bgp-vrf)# neighbor 192.168.70.24RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# remote-as 10RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-vrf-nbr-af)# as-overrideRelated Commands
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:
bfd multiplier (minimum-interval) value
no bfd multiplier (minimum-interval) value
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.
Defaults
No default per neighbor parameters are set.
Command Modes
Neighbor address family independent configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If the minimum interval is changed using the bfd minimum-interval command, 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.
Yes
Yes
BFD value (local)
Yes
No
BFD value (global)
No
Yes
BFD value (local)
No
No
BFD value (default)
Examples
The following example shows how to specify the BFD session's multiplier value for the neighbor:
RP/0/0/CPU0:router # conf tRP/0/0/CPU0:router(config)# router bgp 65000RP/0/0/CPU0:router(config-bgp-nbrgrp)# neighbor 3.3.3.2RP/0/0/CPU0:router(config-bgp-nbr)# bfd minimum-interval 311RP/0/0/CPU0:router(config-bgp-nbr)# bfd multiplier 7RP/0/0/CPU0:router(config-bgp-nbr)# neighbor 5.5.5.2RP/0/0/CPU0:router(config-bgp-nbr)# bfd minimum-interval 318RP/0/0/CPU0:router(config-bgp-nbr)# bfd multiplier 4RP/0/0/CPU0:router(config-bgp-nbr)# vrf oneRP/0/0/CPU0:router(config-bgp-vrf)# neighbor 3.12.1.2RP/0/0/CPU0:router(config-bgp-vrf-nbr)# bfd minimum-interval 119RP/0/0/CPU0:router(config-bgp-vrf-nbr)# bfd multiplier 10RP/0/0/CPU0:router(config-bgp-vrf-nbr)# commitRP/0/0/CPU0:router# show bfd sessionInterface Dest Addr Local det time(int*mult) StateEcho Async-------------------- --------------- ---------------- ---------------- ---------Gi0/2/0/2 3.3.3.2 2177ms(311ms*7) 14s(2s*7) UPGi0/2/0/2.1 3.12.1.2 1190ms(119ms*10) 20s(2s*10) UPPO0/3/0/6 5.5.5.2 1272ms(318ms*4) 8s(2s*4) UPRP/0/0/CPU0:router# show bfd session detailI/f: GigabitEthernet0/2/0/2, Location: 0/2/CPU0, dest: 3.3.3.2, src: 3.3.3.1State: UP for 0d:0h:4m:44s, number of times UP: 1Received parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 7, diag: NoneMy discr: 524295, your discr: 524296, state UP, D/F/P/C/A: 0/0/0/1/0Transmitted parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 7, diag: NoneMy discr: 524296, your discr: 524295, state UP, D/F/P/C/A: 0/0/0/1/0Timer Values:Local negotiated async tx interval: 2 sRemote negotiated async tx interval: 2 sDesired echo tx interval: 311 ms, local negotiated echo tx interval: 311 msEcho detection time: 2177 ms(311 ms*7), async detection time: 14 s(2 s*7)Local Stats:Intervals between async packets:Tx: Number of intervals=100, min=1664 ms, max=2001 ms, avg=1838 msLast packet transmitted 313 ms agoRx: Number of intervals=100, min=1662 ms, max=2 s, avg=1828 msLast packet received 1615 ms agoIntervals between echo packets:Tx: Number of intervals=100, min=181 ms, max=462 ms, avg=229 msLast packet transmitted 289 ms agoRx: Number of intervals=100, min=178 ms, max=461 ms, avg=229 msLast packet received 287 ms agoLatency of echo packets (time between tx and rx):Number of packets: 100, min=0 us, max=4 ms, avg=860 usSession owner information:Client Desired interval Multiplier---------------- -------------------- --------------bgp-0 311 ms 7I/f: GigabitEthernet0/2/0/2.1, Location: 0/2/CPU0, dest: 3.12.1.2, src: 3.12.1.1State: UP for 0d:0h:4m:44s, number of times UP: 1Received parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 10, diag: NoneMy discr: 524296, your discr: 524295, state UP, D/F/P/C/A: 0/0/0/1/0Transmitted parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 10, diag: NoneMy discr: 524295, your discr: 524296, state UP, D/F/P/C/A: 0/0/0/1/0Timer Values:Local negotiated async tx interval: 2 sRemote negotiated async tx interval: 2 sDesired echo tx interval: 119 ms, local negotiated echo tx interval: 119 msEcho detection time: 1190 ms(119 ms*10), async detection time: 20 s(2 s*10)Local Stats:Intervals between async packets:Tx: Number of intervals=100, min=1664 ms, max=2001 ms, avg=1838 msLast packet transmitted 314 ms agoRx: Number of intervals=100, min=1662 ms, max=2 s, avg=1828 msLast packet received 1616 ms agoIntervals between echo packets:Tx: Number of intervals=100, min=120 ms, max=223 ms, avg=125 msLast packet transmitted 112 ms agoRx: Number of intervals=100, min=119 ms, max=223 ms, avg=125 msLast packet received 110 ms agoLatency of echo packets (time between tx and rx):Number of packets: 100, min=0 us, max=2 ms, avg=850 usSession owner information:Client Desired interval Multiplier---------------- -------------------- --------------bgp-0 119 ms 10I/f: POS0/3/0/6, Location: 0/3/CPU0, dest: 5.5.5.2, src: 5.5.5.1State: UP for 0d:0h:4m:50s, number of times UP: 1Received parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 4, diag: NoneMy discr: 786436, your discr: 786433, state UP, D/F/P/C/A: 0/0/0/1/0Transmitted parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 4, diag: NoneMy discr: 786433, your discr: 786436, state UP, D/F/P/C/A: 0/0/0/1/0Timer Values:Local negotiated async tx interval: 2 sRemote negotiated async tx interval: 2 sDesired echo tx interval: 318 ms, local negotiated echo tx interval: 318 msEcho detection time: 1272 ms(318 ms*4), async detection time: 8 s(2 s*4)Local Stats:Intervals between async packets:Tx: Number of intervals=100, min=1663 ms, max=2 s, avg=1821 msLast packet transmitted 1740 ms agoRx: Number of intervals=100, min=1663 ms, max=2001 ms, avg=1832 msLast packet received 160 ms agoIntervals between echo packets:Tx: Number of intervals=100, min=181 ms, max=484 ms, avg=232 msLast packet transmitted 44 ms agoRx: Number of intervals=100, min=179 ms, max=484 ms, avg=232 msLast packet received 41 ms agoLatency of echo packets (time between tx and rx):Number of packets: 100, min=0 us, max=3 ms, avg=540 usSession owner information:Client Desired interval Multiplier---------------- -------------------- --------------bgp-0 318 ms 4RP/0/0/CPU0:router# show bgp nei 3.3.3.2BGP neighbor is 3.3.3.2Remote AS 500, local AS 65000, external linkRemote router ID 16.0.0.1BGP state = Established, up for 00:05:01BFD enabled (session up): mininterval: 311 multiplier: 7Last read 00:00:56, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and received4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedReceived 8 messages, 0 notifications, 0 in queueSent 9 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 30 secondsFor Address Family: IPv4 UnicastBGP neighbor version 2Update group: 0.2AF-dependant capabilities:Graceful Restart Capability advertised and receivedNeighbor preserved the forwarding state during latest restartLocal restart time is 120, RIB purge time is 600 secondsMaximum stalepath time is 360 secondsRemote Restart time is 120 secondsRoute refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all1 accepted prefixes, 1 are bestpathsPrefix advertised 1, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was not received during read-only modeConnections established 1; dropped 0Last reset 00:06:58, due to User clear requested (CEASE notification sent - administrative reset)Time since last notification sent to neighbor: 00:06:58Error Code: administrative resetNotification data sent:NoneRP/0/0/CPU0:router# show bgp nei 5.5.5.2BGP neighbor is 5.5.5.2Remote AS 500, local AS 65000, external linkRemote router ID 16.0.0.1BGP state = Established, up for 00:05:04BFD enabled (session up): mininterval: 318 multiplier: 4Last read 00:00:58, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and received4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedReceived 8 messages, 0 notifications, 0 in queueSent 9 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 30 secondsFor Address Family: IPv4 UnicastBGP neighbor version 2Update group: 0.2AF-dependant capabilities:Graceful Restart Capability advertised and receivedNeighbor preserved the forwarding state during latest restartLocal restart time is 120, RIB purge time is 600 secondsMaximum stalepath time is 360 secondsRemote Restart time is 120 secondsRoute refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all1 accepted prefixes, 0 are bestpathsPrefix advertised 1, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was not received during read-only modeConnections established 1; dropped 0Last reset 00:07:01, due to User clear requested (CEASE notification sent - administrative reset)Time since last notification sent to neighbor: 00:07:01Error Code: administrative resetNotification data sent:NoneRP/0/0/CPU0:router# show bgp vrf one nei 3.12.1.2BGP neighbor is 3.12.1.2, vrf oneRemote AS 500, local AS 65000, external linkRemote router ID 16.0.0.1BGP state = Established, up for 00:05:06BFD enabled (session up): mininterval: 119 multiplier: 10Last read 00:00:01, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and received4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedReceived 9 messages, 0 notifications, 0 in queueSent 9 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 0 secondsFor Address Family: IPv4 UnicastBGP neighbor version 2Update group: 0.2AF-dependant capabilities:Graceful Restart Capability advertised and receivedNeighbor preserved the forwarding state during latest restartLocal restart time is 120, RIB purge time is 600 secondsMaximum stalepath time is 360 secondsRemote Restart time is 120 secondsRoute refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all1 accepted prefixes, 1 are bestpathsPrefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was not received during read-only modeConnections established 1; dropped 0Last reset 00:07:04, due to User clear requested (CEASE notification sent - administrative reset)Time since last notification sent to neighbor: 00:07:04Error Code: administrative resetNotification data sent:Nonebgp 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
Syntax Description
This command has no arguments or keywords.
Defaults
When you do not specify this command, loop checking is performed only for external peers.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure an autonomous system path for loop checking iBGP peers:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# bgp as-path-loopcheckbgp 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
Syntax Description
This command has no arguments or keywords.
Defaults
BGP attribute download is not enabled.
Command Modes
IPv4 unicast address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router# show route bgpB 100.0.1.0/24 [200/0] via 10.0.101.1, 00:00:37B 100.0.2.0/24 [200/0] via 10.0.101.1, 00:00:37B 100.0.3.0/24 [200/0] via 10.0.101.1, 00:00:37B 100.0.4.0/24 [200/0] via 10.0.101.1, 00:00:37B 100.0.5.0/24 [200/0] via 10.0.101.1, 00:00:37RP/0/RP0/CPU0:router(config)# router bgp 50RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# bgp attribute-download!!!RP/0/RP0/CPU0:router# show route bgpB 100.0.1.0/24 [200/0] via 10.0.101.1, 00:00:01Attribute ID 0x2B 100.0.2.0/24 [200/0] via 10.0.101.1, 00:00:01Attribute ID 0x2B 100.0.3.0/24 [200/0] via 10.0.101.1, 00:00:01Attribute ID 0x2B 100.0.4.0/24 [200/0] via 10.0.101.1, 00:00:01Attribute ID 0x2B 100.0.5.0/24 [200/0] via 10.0.101.1, 00:00:01Attribute ID 0x2bgp auto-policy-soft-reset disable
To disable an automatic soft reset of Border Gateway Protocol (BGP) peers when their configured route policy is modified, use the bgp auto-policy-soft-reset disable command in an appropriate configuration mode. To re-enable automatic soft reset of BGP peers, use the no form of this command.
bgp auto-policy-soft-reset disable
no bgp auto-policy-soft-reset disable
Syntax Description
This command has no arguments or keywords.
Defaults
Automatic soft reset of peers is enabled.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following example shows how to disable an automatic soft reset of BGP peers when their configured route policy is modified:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# bgp auto-policy-soft-reset disablebgp bestpath as-path ignore
To ignore the autonomous system path length when calculating preferred paths, use the bgp bestpath as-path ignore command in an appropriate configuration mode. To return the software to the default state in which it considers the autonomous system path length when calculating preferred paths, use the no form of this command.
bgp bestpath as-path ignore
no bgp bestpath as-path ignore
Syntax Description
This command has no arguments or keywords.
Defaults
The autonomous system path length is used (not ignored) when a best path is selected.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure the software to ignore the autonomous system length when performing best-path selection:
RP/0/RP0/CPU0:router(config)# router bgp 65000RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath as-path ignoreRelated Commands
bgp bestpath compare-routerid
To compare identical routes received from external BGP (eBGP) peers during the best-path selection process and select the route with the lowest router ID, use the bgp bestpath compare-routerid command in an appropriate configuration mode. To disable comparing identical routes received from eBGP peers during best-path selection, use the no form of this command.
bgp bestpath compare-routerid
no bgp bestpath compare-routerid
Syntax Description
This command has no arguments or keywords.
Defaults
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.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure the BGP speaker in autonomous system 500 to compare the router IDs of similar paths:
RP/0/RP0/CPU0:router(config)# router bgp 500RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath compare-routeridRelated Commands
bgp bestpath cost-community ignore
To configure a router that is running the Border Gateway Protocol (BGP) to not evaluate the cost community attribute during the best-path selection process, use the bgp bestpath cost-community ignore command in an appropriate configuration mode. To restore the system to its default condition, use the no form of this command.
bgp bestpath cost-community ignore
no bgp bestpath cost-community ignore
Syntax Description
This command has no arguments or keywords.
Defaults
The behavior of this command is enabled by default until the cost community attribute is manually configured.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure a router to not evaluate the cost community attribute during the best-path selection process:
RP/0/RP0/CPU0:router(config)# router bgp 500RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath cost-community ignoreRelated Commands
bgp bestpath med always
To allow the comparison of the Multi Exit Discriminator (MED) for paths from neighbors in different autonomous systems, use the bgp bestpath med always command in an appropriate configuration mode. To disable considering the MED attribute in comparing paths, use the no form of this command.
bgp bestpath med always
no bgp bestpath med always
Syntax Description
This command has no arguments or keywords.
Defaults
The software does not compare MEDs for paths from neighbors in different autonomous systems.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath med alwaysRelated Commands
bgp bestpath med confed
To enable Multi Exit Discriminator (MED) comparison among paths learned from confederation peers, use the bgp bestpath med confed command in an appropriate configuration mode. To disable the software from considering the MED attribute in comparing paths, use the no form of this command.
bgp bestpath med confed
no bgp bestpath med confed
Syntax Description
This command has no arguments or keywords.
Defaults
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.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
By default, the MED of the following paths is not compared with the MED of any other path:
•
•
•
•
Use the bgp bestpath med confed command to affect how the following types of paths are treated in the BGP best-path algorithm:
•
•
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:
•
•
•
If the bgp bestpath med confed command is enabled, the software selects path 1 as the best path because it:
•
•
The MED is not compared with path 3 because it has an external autonomous system number (that is, an AS_SEQUENCE) in the path. If the bgp bestpath med confed command is not enabled, then MED is not compared between any of these paths. Consequently, the software selects path 2 as the best path because it has the lowest IGP metric.
Task ID
Examples
The following command shows how to enable Border Gateway Protocol (BGP) software to compare MED values for paths learned from confederation peers:
RP/0/RP0/CPU0:router(config)# router bgp 210RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath med confedRelated Commands
bgp bestpath med missing-as-worst
To have the software consider a missing Multi Exit Discriminator (MED) attribute in a path as having a value of infinity, making the path without a MED value the least desirable path, use the bgp bestpath med missing-as-worst command in an appropriate configuration mode. To disable considering the MED attribute in comparing paths, use the no form of this command.
bgp bestpath med missing-as-worst
no bgp bestpath med missing-as-worst
Syntax Description
This command has no arguments or keywords.
Defaults
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.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 210RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath med missing-as-worstRelated Commands
bgp client-to-client reflection disable
To disable reflection of routes between route-reflection clients using a Border Gateway Protocol (BGP) route reflector, use the bgp client-to-client reflection disable command in address family configuration mode. To re-enable client-to-client reflection, use the no form of this command.
bgp client-to-client reflection disable
no bgp client-to-client reflection disable
Syntax Description
This command has no arguments or keywords.
Defaults
Client-to-client reflection is enabled.
Command Modes
Address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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:
RP/0/RP0/CPU0:router(config)# router bgp 65534RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# bgp client-to-client reflection disableRP/0/RP0/CPU0:router(config-bgp-af)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor-group rrclientsRP/0/RP0/CPU0:router(config-bgp-nbrgrp)# remote-as 65534RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-reflector-clientRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exitRP/0/RP0/CPU0:router(config-bgp-nbrgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.21 use neighbor-group rrclientsRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.22 use neighbor-group rrclientsRelated Commands
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.
bgp cluster-id cluster-id
no bgp cluster-id [cluster-id]
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.
Defaults
A cluster ID is not configured.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
If the cluster has more than one route reflector, use the bgp cluster-id command to configure the cluster ID.
Task ID
Examples
The following example shows how to configure the local router as one of the route reflectors serving the cluster. It is configured with the cluster ID to identify the cluster.
RP/0/RP0/CPU0:router(config)# router bgp 65534RP/0/RP0/CPU0:router(config-bgp)# bgp cluster-id 192.168.70.1RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.70.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65534RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-reflector-clientRelated Commands
Configures the router as a BGP route reflector and configures the specified neighbor as its client.
Displays entries in the BGP routing table.
bgp confederation identifier
To specify a Border Gateway Protocol (BGP) confederation identifier, use the bgp confederation identifier command in an appropriate configuration mode. To remove the confederation identifier, use the no form of this command.
bgp confederation identifier as-number
no bgp confederation identifier [as-number]
Syntax Description
as-number
Autonomous system (AS) number that internally includes multiple autonomous systems. Range for 2-byte numbers is 1 to 65535. Range for 4-byte numbers is 1.0 to 65535.65535.
Defaults
No confederation identifier is configured.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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.
RP/0/RP0/CPU0:router(config)# router bgp 4001RP/0/RP0/CPU0:router(config-bgp)# bgp confederation identifier 5RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4002RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4003RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4004RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4005RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4006RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4007RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.2.3.4RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 4002RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# exitRP/0/RP0/CPU0:router(config-bgp-nbr)# neighbor 172.20.16.6RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 4009Related Commands
bgp confederation peers
To configure the autonomous systems that belong to the confederation, use the bgp confederation peers command in an appropriate configuration mode. To remove the autonomous system from the confederation, use the no form of this command.
bgp confederation peers [as-number]
no bgp confederation peers [as-number]
Syntax Description
Defaults
No BGP peers are identified as belonging to the confederation.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 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.
Task ID
Examples
The following example shows that autonomous systems 1090 and 1093 belong to a single confederation:
RP/0/RP0/CPU0:router(config)# router bgp 1090RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 1093The following example shows that autonomous systems 1095, 1096, 1097, and 1098 belong to a single confederation:
RP/0/RP0/CPU0:router(config)# router bgp 1095RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peersRP/0/RP0/CPU0:router(config-bgp-confed-peers)# 1096RP/0/RP0/CPU0:router(config-bgp-confed-peers)# 1097RP/0/RP0/CPU0:router(config-bgp-confed-peers)# 1098Related Commands
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.
bgp dampening [half-life [reuse suppress max-suppress-time] | route-policy route-policy-name]
no bgp dampening [half-life [reuse suppress max-suppress-time] | route-policy route-policy-name]
Syntax Description
Defaults
Route dampening is disabled.
half-life: 15 minutes
reuse: 750
suppress: 2000
max-suppress-time: four times half-life valueCommand Modes
IPv4 address family configuration
IPv6 address family configuration
VPNv4 address family configuration
VRF IPv4 address family configuration
VPNv6 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 50RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# bgp dampening 30 1500 10000 120Related Commands
bgp default local-preference
To change the default local preference value, use the bgp default local-preference command in an appropriate configuration mode. To reset the local preference value to the default of 100, use the no form of this command.
bgp default local-preference value
no bgp default local-preference [value]
Syntax Description
Defaults
Enabled with a value of 100.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to raise the default local preference value from the default of 100 to 200:
RP/0/RP0/CPU0:router(config)# router bgp 200RP/0/RP0/CPU0:router(config-bgp)# bgp default local-preference 200bgp enforce-first-as disable
To disable the software from enforcing the first autonomous system path (known as the AS path) of a route received from an external Border Gateway Protocol (eBGP) peer to be the same as the configured remote autonomous system, use the bgp enforce-first-as disable command in an appropriate configuration mode. To re-enable enforcing the first AS path of a received route from an eBGP peer to be the same as the remote autonomous system, use the no form of this command.
bgp enforce-first-as disable
no bgp enforce-first-as disable
Syntax Description
This command has no arguments or keywords.
Defaults
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.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# bgp enforce-first-as disableRelated Commands
bgp fast-external-fallover disable
To disable immediately resetting the Border Gateway Protocol (BGP) sessions of any directly adjacent external peers if the link used to reach them goes down, use the bgp fast-external-fallover disable command in an appropriate configuration mode. To disable this function and perform an immediate reset of BGP sessions when a link between peers is lost, use the no form of this command.
bgp fast-external-fallover disable
no bgp fast-external-fallover disable
Syntax Description
Defaults
BGP sessions of any directly adjacent external peers are immediately reset if the link used to reach them goes down.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to disable the automatic resetting of BGP sessions:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# bgp fast-external-fallover disablebgp 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
Syntax Description
This command has no arguments or keywords.
Defaults
Graceful restart support is not enabled.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the bgp graceful-restart command to enable graceful restart functionality on the router, and also to advertise graceful restart to neighboring routers.
Note
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.
Task ID
Examples
The following example shows how to enable graceful restart:
RP/0/RP0/CPU0:router(config)# router bgp 3RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restartRelated Commands
bgp graceful-restart graceful-reset
To invoke a graceful restart when configuration changes force a peer reset, use the bgp graceful-restart graceful-reset command in an appropriate configuration mode. To disable this function, use the no form of this command.
bgp graceful-restart graceful-reset
no bgp graceful-restart graceful-reset
Syntax Description
This command has no arguments or keywords.
Defaults
Graceful restart is not invoked when a configuration change forces a peer reset.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
BGP graceful restart must be enabled using the bgp graceful-restart command before enabling graceful reset using the bgp graceful-restart graceful-reset command.
Task ID
Examples
The following example shows how to enable graceful reset:
RP/0/RP0/CPU0:router(config)# router bgp 3RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart graceful-resetRelated Commands
Enables a graceful restart.
Displays entries in the BGP routing table.
Displays information about BGP connections to neighbors.
Displays BGP process information.
bgp graceful-restart purge-time
To specify the maximum time before stale routes are purged from the routing information base (RIB) when the local BGP process restarts, use the bgp graceful-restart purge-time command in an appropriate configuration mode. To set the purge timer time to its default value, use the no form of this command.
bgp graceful-restart purge-time seconds
no bgp graceful-restart purge-time seconds
Syntax Description
Defaults
seconds: 600
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to change the BGP purge time to 800 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 3RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart purge-time 800Related Commands
Enables a graceful restart.
Displays entries in the BGP routing table.
Displays information about BGP connections to neighbors.
Displays BGP process information.
bgp graceful-restart restart-time
To specify a user-predicted local BGP process maximum restart time, which is advertised to neighbors during session establishment, use the bgp graceful-restart restart-time command in an appropriate configuration mode. To set this restart time to its default value, use the no form of this command.
bgp graceful-restart restart-time seconds
no bgp graceful-restart restart-time seconds
Syntax Description
Defaults
seconds: 120
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to change the BGP graceful restart time to 400 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 3RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart restart-time 400Related Commands
Enables a graceful restart.
Displays entries in the BGP routing table.
Displays information about BGP connections to neighbors.
Displays BGP process information.
bgp graceful-restart stalepath-time
To specify the maximum time to wait for an End-of-RIB message after a neighbor restarts, use the bgp graceful-restart stalepath-time command in an appropriate configuration mode. To set the stalepath timer time to its default value, use the no form of this command.
bgp graceful-restart stalepath-time seconds
no bgp graceful-restart stalepath-time seconds
Syntax Description
Defaults
seconds: 360
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to change the stalepath time to 750 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 3RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart stalepath-time 750Related Commands
Enables a graceful restart.
Displays entries in the BGP routing table.
Displays information about BGP connections to neighbors.
Displays BGP process information.
bgp log neighbor changes disable
To disable logging of Border Gateway Protocol (BGP) neighbor resets, use the bgp log neighbor changes disable command in an appropriate configuration mode. To re-enable logging of BGP neighbor resets, use the no form of this command.
bgp log neighbor changes disable
no bgp log neighbor changes disable
Syntax Description
This command has no arguments or keywords.
Defaults
BGP neighbor changes are logged.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 disabled 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.
Task ID
Examples
The following example shows how to prevent the logging of neighbor changes for BGP:
RP/0/RP0/CPU0:router(config)# router bgp 65530RP/0/RP0/CPU0:router(config-bgp)# bgp log neighbor change disableRelated Commands
bgp maximum neighbor
To control the maximum number of neighbors that can be configured on the router, use the bgp maximum neighbor command in an appropriate configuration mode. To set the neighbor limit to the default value, use the no form of this command.
bgp maximum neighbor limit
no maximum neighbor [limit]
Syntax Description
Defaults
Default limit is 4000
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Any attempt to configure the neighbor limit below 1 or above 1500 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.
Task ID
Examples
The following example shows how to change the default maximum neighbor limit and set it to 1200:
RP/0/RP0/CPU0:router(config)# router bgp 65530RP/0/RP0/CPU0:router(config-bgp)# bgp maximum neighbor 1200bgp 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
Syntax Description
This command has no arguments or keywords.
Defaults
By default, iBGP routes are not redistributed into IGPs.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
Task ID
Examples
The following example shows how to redistribute iBGP routes into OSPF:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# bgp redistribute-internalRP/0/RP0/CPU0:router(config-bgp)# exitRP/0/RP0/CPU0:router(config)# router ospf area1RP/0/RP0/CPU0:router(config-router)# redistribute bgp 1RP/0/RP0/CPU0:router(config-router)# endRP/0/RP0/CPU0:router# clear route *Related Commands
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.
bgp router-id ip-address
no bgp router-id [ip-address]
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.
Defaults
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.
Command Modes
Router configuration
VRF configurationCommand History
Release 3.4.0
No modification.
Release 3.5.0
No modification.
Release 3.6.0
No modification.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 Cisco IOX XR Routing Configuration Guide.
Task ID
Examples
The following example shows how to configure the local router with the router ID of 192.168.70.24:
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# bgp router-id 192.168.70.24Related Commands
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.
bgp scan-time seconds
no bgp scan-time [seconds]
Syntax Description
Defaults
The default scanning interval is 60 seconds.
Command Modes
Router configuration
IPv4 address family configuration
IPv6 address family configuration
VPNv4 address family configuration
VPNv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to set the scanning interval for IPv4 unicast to 20 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 64500RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# bgp scan-time 20Related Commands
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.
bgp update-delay seconds [always]
no bgp update-delay [seconds] [always]
Syntax Description
Defaults
120 seconds
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to set the maximum initial delay to 240 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 64530RP/0/RP0/CPU0:router(config-bgp)# bgp update-delay 240bgp write-limit
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.
bgp write-limit group-limit global-limit [desynchronize]
no bgp write-limit [group-limit global-limit] [desynchronize]
Syntax Description
Defaults
group-limit: 50,000
global-limit: 250,000
Desynchronization is off.Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 65000RP/0/RP0/CPU0:router(config-bgp)# bgp write-limit 9000 27000capability orf prefix
To advertise prefix list-based Outbound Route Filter (ORF) capability to the Border Gateway Protocol (BGP) peer, use the capability orf prefix command in an appropriate configuration mode. To remove the capability orf prefix command from the configuration file and restore the system to its default condition in which the software does not advertise the capability, use the no form of this command.
capability orf prefix {receive | send | both | none}
no capability orf prefix [receive | send | both | none]
Syntax Description
Defaults
The routing device does not receive or send route prefix filter lists.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
VRF neighbor IPv4 address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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
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.
Task ID
Examples
The following example shows how to configure the capability orf prefix command:
RP/0/RP0/CPU0:# configureRP/0/RP0/CPU0:(config)# route-policy orfqqRP/0/RP0/CPU0:(config-rpl)# if orf prefix in (10.0.0.0/8 ge 20) thenRP/0/RP0/CPU0:(config-rpl)# passRP/0/RP0/CPU0:(config-rpl)# endifRP/0/RP0/CPU0:(config-rpl)# if orf prefix in (1910::16 ge 120) thenRP/0/RP0/CPU0:(config-rpl)# passRP/0/RP0/CPU0:(config-rpl)# endifRP/0/RP0/CPU0:(config-rpl)# end-policyRP/0/RP0/CPU0:(config)# router bgp 65530RP/0/RP0/CPU0:(config-bgp)# neighbor 10.0.101.1RP/0/RP0/CPU0:(config-bgp-nbr)# remote-as 65534RP/0/RP0/CPU0:(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:(config-bgp-nbr-af)# route-policy pass-all outRP/0/RP0/CPU0:(config-bgp-nbr-af)# capability orf prefix bothRP/0/RP0/CPU0:(config-bgp-nbr-af)# orf route-policy orfqqRelated Commands
capability suppress 4-byte-as
To suppress 4-byte AS capability from being advertised to the BGP peer, use the capability suppress 4-byte-as command in the appropriate configuration mode. To remove the capability suppress 4-byte-as command from the configuration and restore the system to the default condition, in which the software advertises the capability, either use the no form of this command or the command with disable option.
capability suppress 4-byte-as [disable]
no capability suppress 4-byte-as
Syntax Description
disable
Restores the software to its default condition wherein the 4-byte AS capability is advertised to the peer.
Defaults
4-byte-as capability is advertised to the BGP peer.
Command Modes
Neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Release 3.4.1
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.5.0
No modification.
Release 3.6.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 or use disable to advertise the 4-byte AS capability again.
Caution
Task ID
Examples
The following example shows how to configure the capability suppress 4-byte-as command:
RP/0/RP0/CPU0:P1# show bgp nei 10.3.3.3 confneighbor 10.3.3.3remote-as 65000 [n:internal]description PE3 []update-source Loopback0 [n:internal]address-family ipv4 unicast [n:internal]RP/0/RP0/CPU0:P1# show bgp nei 10.3.3.3BGP neighbor is 10.3.3.3Remote AS 65000, local AS 65000, internal linkDescription: PE3Remote router ID 10.3.3.3BGP state = Established, up for 1w0dLast read 00:00:17, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and received4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedReceived 25962 messages, 0 notifications, 0 in queueSent 25968 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 0 secondsFor Address Family: IPv4 UnicastBGP neighbor version 1Update group: 0.3Route refresh request: received 0, sent 00 accepted prefixes, 0 are bestpathsPrefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was received during read-only modeConnections established 2; dropped 1Last reset 1w0d, due to BGP Notification sent: hold time expiredTime since last notification sent to neighbor: 1w0dError Code: hold time expiredNotification data sent: NoneRP/0/RP0/CPU0:P1# configRP/0/RP0/CPU0:P1(config)# router bgp 65000RP/0/RP0/CPU0:P1(config-bgp)# nei 10.3.3.3RP/0/RP0/CPU0:P1(config-bgp-nbr)# capability ?suppress Suppress advertising capability to the peerRP/0/RP0/CPU0:P1(config-bgp-nbr)# capability suppress ?4-byte-as 4-byte-as capabilityRP/0/RP0/CPU0:P1(config-bgp-nbr)# capability suppress 4-byte-as ?disable Prevent capability suppress 4-type-as being inherited from the parent<cr>RP/0/RP0/CPU0:P1(config-bgp-nbr)# capability suppress 4-byte-asRP/0/RP0/CPU0:P1(config-bgp-nbr)# commitRP/0/RP0/CPU0:Feb 18 10:58:49.344 : config[65724]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'cisco'. Use 'show configuration commit changes 1000000026' to view the changes.RP/0/RP0/CPU0:P1(config-bgp-nbr)# DRP/0/1/CPU0:Feb 18 10:58:50.623 : bgp[119]: %ROUTING-BGP-5-ADJCHANGE : neighbor 10.3.3.3 Down - Capabilty 4-byte-as configuration changedDRP/0/1/CPU0:Feb 18 10:59:17.394 : bgp[119]: %ROUTING-BGP-5-ADJCHANGE : neighbor 10.3.3.3 UpRP/0/RP0/CPU0:P1(config-bgp-nbr)# endRP/0/RP0/CPU0:Feb 18 10:59:29.196 : config[65724]: %MGBL-SYS-5-CONFIG_I : Configured from console by ciscoRP/0/RP0/CPU0:P1# show bgp nei 10.3.3.3BGP neighbor is 10.3.3.3Remote AS 65000, local AS 65000, internal linkDescription: PE3Remote router ID 10.3.3.3BGP state = Established, up for 00:00:16Last read 00:00:11, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and receivedAddress family IPv4 Unicast: advertised and receivedCapability 4-byte-as suppress is configuredReceived 25966 messages, 0 notifications, 0 in queueSent 25972 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 0 secondsFor Address Family: IPv4 UnicastBGP neighbor version 1Update group: 0.2Route refresh request: received 0, sent 00 accepted prefixes, 0 are bestpathsPrefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was received during read-only modeConnections established 3; dropped 2Last reset 00:00:43, due to Capabilty 4-byte-as configuration changedTime since last notification sent to neighbor: 1w0dError Code: hold time expiredNotification data sent: NoneWith the disable keyword:
RP/0/0/CPU0:csr2(config-bgp)# neighbor 10.0.101.1RP/0/0/CPU0:csr2(config-bgp-nbr)# capability suppress 4-byte-as disableRP/0/0/CPU0:csr2# show bgp neighbor 10.0.101.1 configneighbor 10.0.101.1remote-as 1 []address-family ipv4 unicast []RP/0/0/CPU0:csr2#RP/0/0/CPU0:csr2# show bgp neighbor 10.0.101.1BGP neighbor is 10.0.101.1Remote AS 1, local AS 100, external linkRemote router ID 0.0.0.0BGP state = IdleLast read 00:00:00, hold time is 180, keepalive interval is 60 secondsPrecedence: internetReceived 0 messages, 0 notifications, 0 in queueSent 0 messages, 0 notifications, 0 in queueMinimum time between advertisement runs is 30 secondsRP/0/0/CPU0:csr2#clear bgp
To reset a group of Border Gateway Protocol (BGP) neighbors, use the clear bgp command in EXEC mode.
clear bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} | vpnv6 unicast]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to hard reset neighbor 10.0.0.1:
RP/0/RP0/CPU0:router# clear bgp 10.0.0.1Related Commands
clear bgp current-mode
To switch from one BGP mode to another, use the clear bgp current-mode command in EXEC mode.
clear bgp current-mode
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Use the clear bgp current-mode command to switch from standalone to distributed mode, or from distributed to standalone mode. The show bgp process command indicates the current BGP mode.
Note
Task ID
Examples
The following example shows the show bgp process command output before and after switching from one BGP mode to another:
RP/0/RP0/CPU0:router# show bgp process
BGP Process InformationBGP is operating in STANDALONE modeAutonomous System: 3Router ID: 10.18.18.11Cluster ID: 10.18.18.11Fast external fallover enabledNeighbor logging is enabledEnforce first AS enabledDefault local preference: 100Default keepalive: 60Update delay: 120Generic scan interval: 60Address family: IPv4 UnicastDampening is not enabledClient reflection is enabledScan interval: 60Main Table Version: 3IGP notification: IGPs notifiedRIB has converged: version 0Node Process Nbrs Estb Rst Upd-Rcvd Upd-Sent Nfn-Rcv Nfn-Sntnode0_0_CPU0 Speaker 5 5 51 0 7 0 5RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 3RP/0/RP0/CPU0:router(config-bgp)# distributed speaker 1RP/0/RP0/CPU0:router(config-bgp)# distributed speaker 2RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.101.1RP/0/RP0/CPU0:router(config-bgp-nbr)# speaker-id 2RP/0/RP0/CPU0:router(config-bgp-nbr)# commitRP/0/RP0/CPU0:router# clear bgp current-modeRP/0/RP0/CPU0:router# show bgp processBGP Process InformationBGP is operating in DISTRIBUTED modeAutonomous System: 3Router ID: 10.18.18.11Cluster ID: 10.18.18.11Fast external fallover enabledNeighbor logging is enabledEnforce first AS enabledDefault local preference: 100Default keepalive: 60Update delay: 120Generic scan interval: 60Address family: IPv4 UnicastDampening is not enabledClient reflection is enabledScan interval: 60Main Table Version: 1IGP notification: IGPs not notifiedRIB has not converged: version 0Node Process Nbrs Estb Rst Upd-Rcvd Upd-Sent Nfn-Rcv Nfn-Sntnode0_0_CPU0 Speaker 1 4 1 52 0 0 0 4node0_0_CPU0 Speaker 2 1 0 9 0 0 0 1node0_0_CPU0 bRIB 1 0 0 0 0 0 0 0node0_0_CPU0 bRIB 2 0 0 0 0 0 0 0Related Commands
clear bgp dampening
To clear Border Gateway Protocol (BGP) route dampening information and unsuppress the suppressed routes, use the clear bgp dampening command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} vpnv6 unicast} dampening [ip-address/mask-length]
Syntax Description
Defaults
If no IP address is specified, dampening information for all routes is cleared.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear the route dampening information for all 172.20.0.0/16 IPv4 multicast paths:
RP/0/RP0/CPU0:router# clear bgp ipv4 multicast dampening 172.20.0.0/16Related Commands
Enables BGP route dampening or changes various BGP route dampening factors.
Displays BGP dampened routes.
clear bgp external
To clear all Border Gateway Protocol (BGP) external peers, use the clear bgp external command in EXEC mode.
clear bgp [ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} vpnv6 unicast] external [graceful]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Release 3.5.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Release 3.6.0
No modification.
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear all BGP external peers:
RP/0/RP0/CPU0:router# clear bgp externalclear bgp flap-statistics
To clear Border Gateway Protocol (BGP) flap counts for a specified group of routes, use the clear bgp flap-statistics command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} vpnv6 unicast} flap-statistics [regexp regexp | route-policy route-policy-name | network/mask-length | ip-address]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear the flap count for all routes (in all address families) originating in autonomous system 1:
RP/0/RP0/CPU0:router# clear bgp all all flap-statistics regexp _1$The following example shows how to clear the flap count for all IPv4 unicast routes received from neighbor 172.20.1.1:
RP/0/RP0/CPU0:router# clear bgp ipv4 unicast flap-statistics 172.20.1.1clear bgp nexthop performance-statistics
To reset the number of received notifications and the cumulative processing time for the Border Gateway Protocol (BGP) next-hop, use the clear bgp nexthop performance-statistics command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} vpnv6 unicast} nexthop performance-statistics
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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:
•
•
•
•
•
Task ID
Examples
The following example shows how to clear next-hop performance statistics:
RP/0/RP0/CPU0:router# clear bgp vrf vrf_A nexthop performance statisticsRelated Commands
clear bgp nexthop registration
To reregister a specified next-hop with the Routing Information Base (RIB), use the clear bgp nexthop registration command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} vpnv6 unicast} nexthop registration nexthop-address
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to reregister the next-hop with the RIB:
RP/0/RP0/CPU0:router# clear bgp nexthop registration 10.1.1.1Related Commands
clear bgp peer-drops
To clear the connection-dropped counter, use the clear bgp peer-drops command in EXEC mode.
clear bgp peer-drops {* | ip-address}
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear the connection-dropped counter for all BGP neighbors:
RP/0/RP0/CPU0:router# clear bgp peer-drops *Related Commands
clear bgp performance-statistics
To clear the performance statistics for all address families, use the clear bgp performance-statistics command.
clear bgp [vrf {vrf-name | all}] performance-statistics
Syntax Description
vrf
Specifies VPN routing and forwarding (VRF).
vrf-name
Name of a VRF.
all
For VRF, specifies all VRFs.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear the performance statistics for all address families:
RP/0/RP0/CPU0:router# clear bgp performance-statisticsclear bgp self-originated
To clear Border Gateway Protocol (BGP) routes that are self-originated, use the clear bgp self-originated command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} vpnv6 unicast} self-originated
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Self-originated routes are routes locally originated by the network command, redistribute command, or aggregate-address command.
Task ID
Examples
The following example shows how to clear self-originated IPv4 routes:
RP/0/RP0/CPU0:router# clear bgp ipv4 unicast self-originatedRelated Commands
clear bgp shutdown
To clear all Border Gateway Protocol (BGP) neighbors that shut down due to low memory, use the clear bgp shutdown command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} | vpnv6 unicast} shutdown
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to clear all shut-down BGP neighbors:
RP/0/RP0/CPU0:router# clear bgp shutdownRelated Commands
Displays entries in the BGP routing table.
Displays information about the TCP and BGP connections to neighbors.
clear bgp soft
To soft reset a group of Border Gateway Protocol (BGP) neighbors, use the clear bgp soft command in EXEC mode.
clear bgp {ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} {ipv4 {unicast | labeled-unicast} | ipv6 unicast} | vpnv6 unicast} {* | ip-address | as as-number | external} soft [in [prefix-filter] | out]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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:
Received route refresh capability from peer.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
Task ID
Examples
The following example shows how to trigger an inbound soft clear for IPv4 unicast routes received from neighbor 10.0.0.1:
RP/0/RP0/CPU0:router# clear bgp ipv4 unicast 10.0.0.1 soft inRelated Commands
default-information originate (BGP)
To allow origination of a default route to be redistributed into the Border Gateway Protocol (BGP) from another protocol, use the default-information originate command in an appropriate configuration mode. To disable this function, use the no form of this command.
default-information originate
no default-information originate
Syntax Description
This command has no arguments or keywords.
Defaults
BGP does not permit redistribution of a default route into BGP.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure BGP to redistribute the default route into BGP:
RP/0/RP0/CPU0:router(config)# router bgp 164RP/0/RP0/CPU0:router(config-bgp)# default-information originateRelated Commands
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.
Defaults
A metric is not sent.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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).
Task ID
Examples
The following example shows how to set the BGP default metric:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# default-metric 10default-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.
default-originate [disable | route-policy route-policy-name]
no default-originate [disable | route-policy route-policy-name]
Syntax Description
Defaults
The default route is not advertised to BGP neighbors.
Command Modes
IPv4 neighbor address family configuration
IPv6 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
IPv4 address family group configuration
IPv6 address family group configuration
VRF IPv4 neighbor address family configuration
VRF IPv6 neighbor address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to unconditionally advertise the route 0.0.0.0/0 to the neighbor 172.20.2.3:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.2.3RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 200RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# default-originateThe 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:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.2.3RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 200RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# default-originate route-policy default-default-policyRelated Commands
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]
Syntax Description
Defaults
No comment or description exists.
Command Modes
Neighbor group configuration
Neighbor configuration
Session group configuration
VRF neighbor configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure the description "Our best customer" on the neighbor 192.168.13.4:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 65000RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.13.4RP/0/RP0/CPU0:router(config-bgp-nbr)# description Our best customerdistance 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 no form of this command.
distance bgp external-distance internal-distance local-distance
no distance bgp [external-distance internal-distance local-distance ]
Syntax Description
Defaults
external-distance: 20
internal-distance: 200
local-distance: 200Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Note
An administrative distance is a rating of the trustworthiness of a routing information source. Numerically, an administrative distance is an integer from 1 to 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored.
Task ID
Examples
The following example shows that iBGP routes are preferable to locally generated routes, so the administrative distance values are set accordingly:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# distance bgp 20 20 200Related Commands
Defines the administrative distance assigned to routes discovered by the IS-IS protocol.
Defines OSPF route administrative distances based on route type.
distributed speaker
To enable a distributed speaker process, use the distributed speaker command in router configuration mode. To remove the distributed speaker process, use the no form of this command.
distributed speaker id
no distributed speaker id
Syntax Description
Defaults
Default is 0.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If BGP is currently running in standalone mode, you must enter the clear bgp current-mode command to switch from standalone or distributed mode.
Task ID
Examples
The following example shows how to enable distributed speaker process 3:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# distributed speaker 3Related Commands
dmz-link-bandwidth
To originate a demilitarized zone (DMZ) link bandwidth extended community for the link to an eBGP neighbor, use the dmz-link-bw command in an appropriate configuration mode. To cease origination of the DMZ link bandwidth extended community, use the no form of this command.
dmz-link-bandwidth [disable]
no dmz-link-bandwidth [disable]
Syntax Description
disable
(Optional) Prevents the dmz-link-bandwidth command from being inherited from a parent group.
Defaults
BGP does not originate the DMZ link bandwidth extended community.
Command Modes
Neighbor configuration
Neighbor group configuration
Session group configuration
VRF neighbor configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the dmz-link-bandwidth command to advertise the bandwidth of links that are used to exit an autonomous system.
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.
Task ID
Examples
The following example shows how to advertise the bandwidth of links to eBGP neighbors from router bgp 1:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 45.67.89.01RP/0/RP0/CPU0:router(config-bgp-nbr)# dmz-link-bandwidthRelated Commands
Creates a neighbor group and enters neighbor group configuration mode.
Creates a session group and enters session group configuration mode.
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
Defaults
No default behavior or values
Command Modes
Neighbor configuration
Neighbor session group configuration
Neighbor group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the dscp command to change the minimum and maximum packet thresholds for the DSCP value.
Table 2 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.
Task ID
Examples
The following example shows how to set the DSCP value to af32:
RP/0/RP0/CPU0:router(config)# router bgp 5RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100RP/0/RP0/CPU0:router(config-bgp-nbr)# dscp af32ebgp-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.
ebgp-multihop [ttl-value]
no ebgp-multihop [ttl-value]
Syntax Description
Defaults
Default TTL value is 255.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
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.
Task ID
Examples
The following example shows how to allow a BGP connection to neighbor 172.20.16.6 of up to 255 hops away:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.16.6RP/0/RP0/CPU0:router(config-bgp-nbr)# ebgp-multihopRelated Commands
Creates a neighbor group and enters neighbor group configuration mode.
Creates a session group and enters session group configuration mode.
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.
export route-policy policy-name
no export route-policy [policy-name]
Syntax Description
Defaults
No default behavior or values
Command Modes
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the export route-policy command to define the conditions that allow specified routes to be tagged with specified route-targets.
Task ID
Examples
The following example shows how to configure an export route policy:
RP/0/RP0/CPU0:router(config)# vrf vrf-1RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-vrf-af)# export route-policy policy-ARelated Commands
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.
export route-target [as-number:nn | ip-address:nn]
no export route-target [as-number:nn | ip-address:nn]
Syntax Description
Defaults
No default behavior or values
Command Modes
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to specify an export route-target:
RP/0/RP0/CPU0:router(config)# vrf vrf-1RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-vrf-af)# export route-target 500:1Related Commands
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.
import route-policy policy-name
no import route-policy [policy-name]
Syntax Description
Defaults
No default behavior or values
Command Modes
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to allow only policy-B to be imported to VRF:
RP/0/RP0/CPU0:router(config)# vrf vrf-1RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-vrf-af)# import route-policy policy-BRelated Commands
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.
import route-target [as-number:nn | ip-address:nn]
no import route-target [as-number:nn | ip-address:nn]
Syntax Description
Defaults
No default behavior or values
Command Modes
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to specify an import route-target:
RP/0/RP0/CPU0:router(config)# vrf vrf-1RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-vrf-af)# import route-target 500:99Related Commands
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 Descriptionr
name
Key chain name configured using the keychain command. The name must be a maximum of 32 alphanumeric characters.
Defaults
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.
Command Modes
Neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# keychain keychain_ARelated Commands
Overrides any inherited keychain configuration from a neighbor group or session group for BGP neighbors.
keychain-disable
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
Syntax Description
This command has no arguments or keywords.
Defaults
Configured key chains for neighbor and session groups are inherited.
Command Modes
Neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# session-group group1RP/0/RP0/CPU0:router(config-bgp-sngrp)# keychain keychain_ARP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# keychain-disableRelated Commands
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 [per-ce]
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.
Defaults
Per-prefix is the default label allocation mode.
Command Modes
VRF configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to set the label allocation mode to customer edge:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# vrf vrf-1RP/0/RP0/CPU0:router(config-bgp-vrf)# label-allocation-mode per-celocal-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.
local-as {as-number [no-prepend] | disable}
no local-as [as-number [no-prepend] | disable]
Syntax Description
Defaults
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.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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). 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.
Task ID
Examples
The following example shows BGP using autonomous system 30 for the purpose of peering with neighbor 172.20.1.1:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 300RP/0/RP0/CPU0:router(config-bgp-nbr)# local-as 30Related Commands
Creates a neighbor group and enters neighbor group configuration mode.
Creates a session group and enters session group configuration mode.
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.
maximum-paths {ebgp | ibgp | eibgp} maximum [unequal-cost]
no maximum-paths {ebgp | ibgp | eibgp} [maximum] [unequal-cost]
Syntax Description
Defaults
One path is installed in the routing table.
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the maximum-paths command to allow the BGP protocol to install multiple paths into the routing table for each prefix. 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, multiple paths are installed for internal peers that are equal cost based on the BGP best-path algorithm. 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. See Implementing BGP on Cisco IOS XR Software in the Cisco IOS XR Routing Configuration Guide for information on the BGP best-path algorithm.
Note
Task ID
Examples
The following example shows how to allow a maximum of four paths to a destination installed into the IPv4 unicast routing table:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# maximum-paths ebgp 4maximum-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.
maximum-prefix maximum [threshold] [warning-only]
no maximum-prefix [maximum [threshold] [warning-only]]
Syntax Description
Defaults
When this command is not specified, the following defaults apply:
IPv4 unicast: 524,288 prefixes
IPv4 multicast: 131,072 prefixes
IPv4 tunnel: 524, 288
IPv6 unicast: 131,072 prefixes
IPv6 multicast: 131,072 prefixes
VPNv4 unicast: 524, 288
VPNv6 unicast: 524, 288
The default threshold when a warning message is generated is 75 percent.Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
IPv6 neighbor address family configuration
VPNv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
IPv4 tunnel neighbor address family configuration
IPv4 tunnel neighbor group address family configuration
IPv4 tunnel address family group configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
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.
Task ID
Examples
The following example shows the maximum number of IP Version 4 (IPv4) unicast prefixes allowed from the neighbor at 192.168.40.24 set to 1000:
RP/0/RP0/CPU0:router(config-bgp)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# maximum-prefix 1000Related Commands
mpls activate (BGP)
To enable Multiprotocol Label Switching (MPLS) on an interface basis for ASBR and CSC configurations whenever a bgp confederation configuration is used, use the mpls activate command in bgp configuration mode. This is needed for InterAS (option B and C) and Carrier Supporting Carrier (CSC) configurations with confederations.
The normal InterAS and CSC configurations (without confederations) do not need to enable this.
To restore the system to its default condition, use the no form of this command.
mpls activate interface id
no mpls activate interface id
Syntax Description
Defaults
No default behavior or values
Command Modes
Router configuration
Neighbor configuration
IPv4 address family group configuration
VPNv4 address family group configurationCommand History
Release 3.6.0
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router
Release 3.7.0
No modification.
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The mpls 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.
Task ID
Examples
The following example shows how to activate MPLS for InterAS Option B (with confederations):
RP/0/RP0/CPU0:router(config)# router bgp 1bgp confederation peers2002!bgp confederation identifier 4589bgp router-id 3.3.3.3mpls activateinterface GigabitEthernet0/1/0/0!address-family ipv4 unicastredistribute connected!address-family vpnv4 unicastretain route-target all!neighbor 10.0.0.9remote-as 2002address-family ipv4 unicastroute-policy pass inroute-policy pass out!address-family vpnv4 unicastroute-policy pass inThe following example shows how to activate MPLS for CSC (with confederations):
router bgp 2002bgp confederation peers1!bgp confederation identifier 4589bgp router-id 4.4.4.4address-family ipv4 unicastallocate-label all!address-family vpnv4 unicastretain route-target all!vrf foord 1:1mpls activateinterface GigabitEthernet0/1/0/2!address-family ipv4 unicastredistribute connectedallocate-label all!neighbor 10.0.0.1remote-as 1address-family ipv4 unicast!address-family ipv4 labeled-unicastroute-policy pass inroute-policy pass out!!!!!RP/0/5/CPU0:Durango#show mpls forwardingLocal Outgoing Prefix Outgoing Next-hop BytesLabel Label or ID InterfaceSwitched------ ----------- ------------------ ------------ ---------------------------16000 Aggregate foo: Per-VRF Aggr[V] \foo 016001 Pop 10.0.0.0/16[V] Gi0/1/0/2 10.0.0.1 44RP/0/5/CPU0:Durango#show mpls interfacesInterface LDP Tunnel Enabled-------------------------- -------- -------- --------GigabitEthernet0/1/0/2 No No YesRelated Commands
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
Syntax Description
Defaults
Neighbor mode is not specified.
Command Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65000The 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:
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# address-family ipv6 unicastRP/0/RP0/CPU0:router(config-bgp-af)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 3000::1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2002RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv6 unicastRelated Commands
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
Syntax Description
Defaults
No neighbor group mode is specified.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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.
Note
Task ID
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.
RP/0/RP0/CPU0:router(config)# router bgp 65530RP/0/RP0/CPU0:router(config-bgp)# neighbor-group group1RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# remote-as 65535RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# advertisement-interval 2RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# send-community-ebgpRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exitRP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# next-hop-selfRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exitRP/0/RP0/CPU0:router(config-bgp-nbrgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# use neighbor-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2RP/0/RP0/CPU0:router(config-bgp-nbr)# use neighbor-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRelated Commands
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.
network {ip-address/prefix-length | ip-address mask} [route-policy route-policy-name]
no network {ip-address/prefix-length | ip-address mask} [route-policy route-policy-name]
Syntax Description
Defaults
No networks are specified.
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure the local router to originate the IPv4 unicast network 172.20.0.0/16:
RP/0/RP0/CPU0:router(config)# router bgp 120RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# network 172.20.0.0/16Related Commands
Specifies a backdoor route to a BGP border router that provides better information about the network.
Redistributes routes from one routing domain into another routing domain.
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 to no form of this command.
network {ip-address/prefix-length | ip-address mask} backdoor
no network {ip-address/prefix-length | ip-address mask} backdoor
Syntax Description
Defaults
No backdoor routes are installed.
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows IP Version 4 (IPv4) unicast network 192.168.40.0/24 configured as a backdoor network:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# network 192.168.40.0/24 backdoorRelated Commands
Specifies a local network that the BGP routing process should originate and advertise to its neighbors.
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 [disable]
no next-hop-self [disable]
Syntax Description
disable
(Optional) Allows a next-hop calculation override when this feature may be inherited from a neighbor group or address family group.
Defaults
When this command is not specified, the software calculates the next-hop for BGP updates accepted by the router.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
VPNv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# next-hop-selfThe 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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-selfRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# next-hop-self disableRelated Commands
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.
next-hop-unchanged [disable]
no next-hop-unchanged [disable]
Syntax Description
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.
Defaults
Overwriting of the next-hop is allowed.
Command Modes
VPNv4 address family group configuration
VPNv4 neighbor address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
Task ID
Examples
The following example shows how to disable the overwriting of next-hops before advertising to eBGP peers:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family vpnv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-unchanged disableRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRelated Commands
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.
nexthop route-policy route-policy-name
no nexthop route-policy route-policy-name
Syntax Description
Defaults
No default behavior or values
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VPNv4 address family configuration
VPNv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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:
•
•
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.
Task ID
Examples
The following example shows how to specify the route policy nexthop_A as the policy to use for filtering next-hops:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# nexthop route-policy nexthop_ARelated Commands
Defines a route policy and enters route-policy configuration mode.
Display statistical information about the BGP next-hops.
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.
nexthop trigger-delay {critical delay | non-critical delay}
no nexthop trigger-delay {critical delay | non-critical delay}
Syntax Description
Defaults
critical: 3000 msec
non-critical: 10000 msecCommand Modes
IPv4 address family configuration
IPv6 address family configuration
VPNv4 address family configuration
VPNv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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).
Task ID
Examples
The following example shows how to set the critical next-hop trigger delay to 3500 milliseconds:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# nexthop trigger-delay critical 3500orf
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.
orf route-policy route-policy-name
no orf route-policy route-policy-name
Syntax Description
Defaults
No ORF route policy is defined.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VRF IPv6 neighbor address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to configure outbound and inbound filtering criteria:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# orf route-policy policy_ARelated Commands
Applies a routing policy to updates advertised to or received from a BGP neighbor.
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.
password {clear | encrypted} password
no password [clear password | encrypted password]
Syntax Descriptionr
Defaults
When this command is not specified in the appropriate configuration mode, MD5 authentication is not enabled on a TCP connection between two BGP neighbors.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
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.
Task ID
Examples
The following example shows how to configure neighbor 172.20.1.1 to use MD5 authentication with the password password1:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# password clear password1Related Commands
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
Syntax Description
This command has no arguments or keywords.
Defaults
Configured passwords for neighbor and session groups are inherited.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# session-group group1RP/0/RP0/CPU0:router(config-bgp-sngrp)# password clear password1RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# password-disableRelated Commands
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
Defaults
No default behavior or values
Command Modes
Neighbor configuration
Neighbor session group configuration
Neighbor group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the precedence command to set the precedence value.
Task ID
Examples
The following example shows how to set the precedence to 2:
RP/0/RP0/CPU0:router(config)# router bgp 5RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100RP/0/RP0/CPU0:router(config-bgp-nbr)# precedence 2rd
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.
rd {as-number:nn | ip-address:nn | auto}
no rd [as-number:nn | ip-address:nn | auto]
Syntax Description
Defaults
No default behavior or values
Command Modes
VRF configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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:
•
•
•
•
•
Task ID
Examples
The following example shows how to automatically assign a unique route distinguisher to VRF instance vrf-1:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# vrf vrf-1RP/0/RP0/CPU0:router(config-bgp-vrf)# rd autoRelated Commands
Configures a fixed router ID for a BGP-speaking router.
Configures a VRF export route-target extended community.
Configures a VRF import route-target extended community.
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.
receive-buffer-size socket-size [bgp-size]
no receive-buffer-size [socket-size] [bgp-size]
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.
Defaults
socket-size: 32,768 bytes
bgp-size: 4,032 bytesCommand Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# receive-buffer-size 65536 8192Related Commands
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]
Enhanced Interior Gateway Routing Protocol (EIGRP)
redistribute eigrp process-id [match {external | internal}] [metric metric-value] [route-policy route-policy-name]
no redistribute eigrp process-id [match {external | internal}] [metric metric-value] [route-policy route-policy-name]
Intermediate System-to-Intermediate System (IS-IS)
redistribute isis process-id [level {1 | 1-inter-area | 2}] [metric metric-value] [route-policy route-policy-name]
no redistribute isis process-id [level {1 | 1-inter-area | 2}] [metric metric-value] [route-policy route-policy-name]
Open Shortest Path First (OSPF)
redistribute ospf process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]} [metric metric-value] [route-policy route-policy-name]
no redistribute ospf process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]} [metric metric-value] [route-policy route-policy-name]
OSPFv3
redistribute ospfv3 process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]} [metric metric-value] [route-policy route-policy-name]
no redistribute ospfv3 process-id [match {external [1 | 2] | internal | nssa-external [1 | 2]]} [metric metric-value] [route-policy route-policy-name]
Routing Information Protocol
redistribute rip [metric metric-value] [route-policy route-policy-name]
no redistribute rip [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
Defaults
Route redistribution is disabled.
For IS-IS, the default is to redistribute Level 1 and Level 2 routes.
For OSPF, the default is to redistribute internal, external, and NSSA external routes of Type 1 and Type 2.
For OSPFv3, 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)
VRF IPv4 address family configuration (connected, eigrp, ospf, rip, and static are supported)
VRF IPv6 address family configuration (connected, eigrp, and static are supported)Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
Task ID
Examples
The following example shows how to redistribute IP Version 4 (IPv4) unicast OSPF routes from OSPF instance 110 into BGP:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# redistribute ospf 110Related Commands
Specifies a local network that the BGP routing process should originate and advertise to its neighbors.
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 numbers is 1 to 65535. Range for 4-byte numbers is 1.0 to 65535.65535.
Defaults
No BGP neighbors exist.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2The 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/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group group2RP/0/RP0/CPU0:router(config-bgp-sngrp)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group2Related Commands
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.
remove-private-as [disable]
no remove-private-as [disable]
Syntax Description
disable
(Optional) Permits the feature to be disabled from a neighbor group or address family group instead of being inherited.
Defaults
When this command is not specified in the appropriate configuration mode, private autonomous system numbers are not removed from updates sent to external neighbors.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
VPNv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VRF IPv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
This feature is available for external BGP (eBGP) neighbors only.
When an update is passed to the external neighbor, the software drops any leading autonomous system sequence in the autonomous system path if the sequence contains only private autonomous system numbers and does not contain the autonomous system number of the neighbor.
If this command is used in a BGP confederation, the element following the confederation portion of the autonomous system path, if a sequence, is considered the leading sequence.
The private autonomous system values range from 64512 to 65535.
If this command is configured for a neighbor group or address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# remote-private-asThe 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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# remove-private-asRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr# remote-private-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# remove-private-as disableRelated Commands
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.
retain route-target {all | route-policy route-policy-name}
no retain route-target [all | route-policy route-policy-name]
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.
Defaults
The default is to accept all route targets.
Command Modes
VPNv4 address family configuration
VPNv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the retain route-target command to configure a route reflector (RR) to retain routes tagged with specific route targets (RT).
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.
Task ID
Examples
The following example shows how to configure RR to retain all routes with the route filter policy ft-policy-A:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# retain route-target route-filter ft-policy-ARelated Commands
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.
route-policy route-policy-name [parameter1, parameter2, . . . , parametern] {in | out}
no route-policy route-policy-name [parameter1, parameter2, . . . , parametern] {in | out}
Syntax Description
route-policy-name
Name of route policy. Up to 16 parameters can follow the route-policy-name, enclosed in brackets ([ ]).
in
Applies policy to inbound routes.
out
Applies policy to outbound routes.
Defaults
No policy is applied.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
VPNv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VRF IPv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Note
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-policy In-Ipv4 inRelated Commands
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 [disable]
no route-reflector-client [disable]
Syntax Description
disable
(Optional) Allows the configuration inherited from a neighbor group or address family group to be overridden.
Defaults
The neighbor is not treated as a route reflector client.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
VPNv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
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.
Task ID
Examples
The following example shows neighbor at 172.20.1.1 configured as a route reflector client for IP Version 4 (IPv4) unicast routes:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 140RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-reflector-clientThe 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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# route-reflector-clientRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 140RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-reflector-client disableRelated Commands
router bgp
To configure the Border Gateway Protocol (BGP) routing process, use the router bgp command in global configuration mode. To remove all BGP configurations and terminate the BGP routing process, use the no form of this command.
router bgp as-number
no router bgp [as-number]
Syntax Description
as-number
Number that identifies the autonomous system (AS) in which the router resides. Range for 2-byte numbers is 1 to 65535. Range for 4-byte numbers is 1.0 to 65535.65535.
Defaults
No BGP routing process is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following example shows how to configure a BGP process for autonomous system 120:
RP/0/RP0/CPU0:router(config)# router bgp 120send-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.
send-buffer-size socket-size [bgp-size]
no send-buffer-size [socket-size] [bgp-size]
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.
Defaults
socket-size: 10240 bytes
bgp-size: 4096 bytes
Use the socket send-buffer-size command to change the defaults.Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# send-buffer-size 8192 8192Related Commands
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 [disable]
no send-community-ebgp [disable]
Syntax Description
disable
(Optional) Allows configuration inherited from a neighbor group or address family group to be overridden.
Defaults
Community attributes are not sent to eBGP neighbors.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VRF IPv6 neighbor address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the send-community-ebgp command to control whether community attributes are sent to eBGP neighbors. It cannot be configured for iBGP neighbors. Communities are always sent to iBGP neighbors.
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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-community-ebgpThe 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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# send-community-ebgpRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-community-ebgp disableRelated Commands
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 [disable]
no send-extended-community-ebgp [disable]
Syntax Description
disable
(Optional) Allows configurations inherited from a neighbor group or address family group to be overridden.
Defaults
Extended community attributes are not sent to an eBGP neighbor.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VRF IPv6 neighbor address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the send-extended-community-ebgp command to control whether extended community attributes are sent to eBGP neighbors. It cannot be used for iBGP neighbors. Extended communities are always sent to iBGP 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.
Task ID
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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-extended-community-ebgpThe 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:
RP/0/RP0/CPU0:router(config)# router bgp 140RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# send-extended-community-ebgpRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-extended-community-ebgp disableRelated Commands
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
Syntax Description
Defaults
No session groups are created.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
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.
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group group1RP/0/RP0/CPU0:router(config-bgp-sngrp)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 2RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1The 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.
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group group1RP/0/RP0/CPU0:router(config-bgp-sngrp)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 2RP/0/RP0/CPU0:router(config-bgp-sngrp)# password password1RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# password-disablesession-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.
session-open-mode {active-only | both | passive-only}
no session-open-mode [active-only | both | passive-only]
Syntax Description
Defaults
The default is both.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Note
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 non default value (active-only or passive-only keyword) for this command.
Task ID
Examples
The following example shows how to enable a BGP session on router bgp 1:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 45.67.89.01RP/0/RP0/CPU0:router(config-bgp-nbr)# session-open-mode active-onlyshow 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 | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] [ip-address [{mask | /prefix-length} [longer-prefixes | unknown-attributes | bestpath-compare]]]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
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.
Task ID
Examples
The following is sample output from the show bgp command in EXEC mode:
RP/0/RP0/CPU0:router# show bgpBGP router identifier 172.20.1.1, local AS number 1820BGP generic scan interval 60 secsBGP table state: ActiveTable ID: 0xe0000000BGP main routing table version 3Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path* i10.3.0.0/16 172.20.22.1 0 100 0 1800 1239 ?*>i 172.20.16.1 0 100 0 1800 1239 ?* i10.6.0.0/16 172.20.22.1 0 100 0 1800 690 568 ?*>i 172.20.16.1 0 100 0 1800 690 568 ?* i10.7.0.0/16 172.20.22.1 0 100 0 1800 701 35 ?*>i 172.20.16.1 0 100 0 1800 701 35 ?* 192.168.40.24 0 1878 704 701 35 ?* i10.8.0.0/16 172.20.22.1 0 100 0 1800 690 560 ?*>i 172.20.16.1 0 100 0 1800 690 560 ?* 192.168.40.24 0 1878 704 701 560 ?* i10.13.0.0/16 172.20.22.1 0 100 0 1800 690 200 ?*>i 172.20.16.1 0 100 0 1800 690 200 ?* 192.168.40.24 0 1878 704 701 200 ?* i10.15.0.0/16 172.20.22.1 0 100 0 1800 174 ?*>i 172.20.16.1 0 100 0 1800 174 ?* i10.16.0.0/16 172.20.22.1 0 100 0 1800 701 i*>i 172.20.16.1 0 100 0 1800 701 i* 192.168.40.24 0 1878 704 701 iProcessed 8 prefixes, 8 pathsTable 3 describes the significant fields shown in the display.
The following is sample output from the show bgp command with the network specified:
RP/0/RP0/CPU0:router# show bgp 11.0.0.0/24BGP router table entry for 11.0.0.0/24Versions:Process bRIB/RIB SendTblVerSpeaker 2 2Paths: (3 available, best #1)Advertised to update-groups (with more than one peer):0.1Advertised to peers (in unique update groups):10.4.101.1Received by speaker 0Local0.0.0.0 from 0.0.0.0 (10.4.0.1)Origin IGP, metric 0, localpref 100, weight 32768, valid, local, bestReceived by speaker 02 3 410.4.101.1 from 10.4.101.1 (10.4.101.1)Origin IGP, localpref 100, valid, externalReceived by speaker 0Local10.4.101.2 from 10.4.101.2 (10.4.101.2)Origin IGP, localpref 100, valid, internal RP/0/0/CPU0:router#Table 4 describes the significant fields shown in the display.
Related Commands
show bgp advertised
To display advertisements for neighbors or a single neighbor, use the show bgp advertised command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] vpnv6 unicast [rd rd-address]] advertised [neighbor ip-address] [summary]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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
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.
Note
Task ID
Examples
The following is sample output from the show bgp advertised command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp advertised neighbor 10.0.101.4 summaryNetwork Next-hop From AS Path1.1.1.0/24 10.0.101.1 10.0.101.1 2 3 222 333 444 555 i1.1.2.0/24 10.0.101.1 10.0.101.1 3 4 5 6 7 i1.1.3.0/24 10.0.101.1 10.0.101.1 77 88 33 44 55 99 99 99 i1.1.4.0/24 10.0.101.1 10.0.101.1 2 5 6 7 8 i1.1.7.0/24 10.0.101.1 10.0.101.1 3 5 i1.1.8.0/24 10.0.101.1 10.0.101.1 77 88 99 99 99 iTable 5 describes the significant fields shown in the display.
The following is sample output from the show bgp advertised command for detailed advertisement information:
RP/0/RP0/CPU0:router# show bgp advertised neighbor 172.72.77.1172.16.0.0/24 is advertised to 172.72.77.1Path info:neighbor: Local neighbor router id: 172.74.84.1valid redistributed bestAttributes after inbound policy was applied:next-hop: 0.0.0.0MET ORG ASorigin: incomplete metric: 0aspath:10.52.0.0/16 is advertised to 172.72.77.1Path info:neighbor: Local Aggregate neighbor router id: 172.74.84.1valid aggregated bestAttributes after inbound policy was applied:next-hop: 0.0.0.0ORG AGG ATOMorigin: IGP aggregator: 172.74.84.1 (1)aspath:Table 6 describes the significant fields shown in the display.
Related Commands
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.
Applies a route policy to incoming and outgoing routes.
Filters routes using a prefix list.
Displays information about BGP advertisements under a proposed policy.
show bgp policy sent-advertisements
Previews advertisements to peers, including details of advertised attributes.
show bgp af-group
To display information about Border Gateway Protocol (BGP) configuration for address family groups, use the show bgp af-group command in EXEC mode.
show bgp af-group group-name {configuration [defaults] [nvgen] | inheritance | users}
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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.
Task ID
Examples
The following af-group configuration is used in the examples:
af-group group3 address-family ipv4 unicastremove-private-ASsoft-reconfiguration inbound!af-group group1 address-family ipv4 unicastuse af-group group2maximum-prefix 2500 75 warning-onlydefault-originatesoft-reconfiguration inbound disable!af-group group2 address-family ipv4 unicastuse af-group group3send-community-ebgpsend-extended-community-ebgpcapability orf prefix bothThe 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.
RP/0/RP0/CPU0:router# show bgp af-group group1 configurationaf-group group1 address-family ipv4 unicastcapability orf prefix both [a:group2]default-originate []maximum-prefix 2500 75 warning-only []remove-private-AS [a:group2 a:group3]send-community [a:group2]send-extended-community [a:group2The following is sample output from the show bgp af-group command with the users keyword:
RP/0/RP0/CPU0:router# show bgp af-group group2 usersIPv4 Unicast: a:group1The 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:
RP/0/RP0/CPU0:router# show bgp af-group group1 inheritanceIPv4 Unicast: a:group2 a:group3Table 7 describes the significant fields shown in the display.
Related Commands
Configures a BGP address family group.
Displays information about BGP neighbors, including configuration inherited from neighbor groups, session groups, and address family groups.
Displays information about configuration for neighbor groups.
use af-group
Configures an af-group to inherit the configuration of a specified af-group.
show bgp attribute-key
To display all existing attribute keys, use the show bgp attribute-key command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] vpnv6 unicast] attribute-key
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Task ID
Examples
The following is sample output from the show bgp attribute-key command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp all all attribute-keyAddress Family: IPv4 Unicast============================BGP router identifier 10.0.0.1, local AS number 1BGP generic scan interval 60 secsBGP main routing table version 109BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop AttrKey*> 1.1.0.0/16 0.0.0.0 0x00000002*> 10.0.0.0/16 0.0.0.0 0x00000002*> 12.21.0.0/16 0.0.0.0 0x00000002*> 194.3.192.1/32 10.0.101.1 0x00000009*> 194.3.192.2/32 10.0.101.1 0x00000009*> 194.3.192.3/32 10.0.101.1 0x00000009*> 194.3.192.4/32 10.0.101.1 0x00000009*> 194.3.192.5/32 10.0.101.1 0x00000009Processed 8 prefixes, 8 pathsAddress Family: IPv4 Multicast==============================BGP router identifier 10.0.0.1, local AS number 1BGP generic scan interval 60 secsBGP main routing table version 15BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop AttrKey*> 194.3.193.2/32 10.0.101.1 0x00000009*> 194.3.193.3/32 10.0.101.1 0x00000009Processed 2 prefixes, 2 pathsAddress Family: IPv6 Unicast============================BGP router identifier 10.0.0.1, local AS number 1BGP generic scan interval 60 secsBGP main routing table version 19BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop AttrKey*> 2222::1111/128 2222::2 0x00000009*> 2222::1112/128 2222::2 0x00000009Processed 2 prefixes, 2 pathsTable 8 describes the significant fields shown in the display.
Related Commands
show bgp cidr-only
To display routes with nonnatural network masks, also known as classless interdomain routing (CIDR) routes, use the show bgp cidr-only command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast}] cidr-only
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
Task ID
Examples
The following is sample output from the show bgp cidr-only command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp cidr-onlyBGP router identifier 172.20.1.1, local AS number 1820BGP main routing table version 2589Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path*> 192.0.0.0/8 192.168.72.24 0 1878 ?*> 192.168.0.0/16 192.168.72.30 0 108 ?Table 9 describes the significant fields shown in the display.
Related Commands
show bgp community
To display routes that have the specified Border Gateway Protocol (BGP) communities, use the show bgp community command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] community community-list [exact-match]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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 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.
Task ID
Examples
The following is sample output from the show bgp community command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp community 1820:1 exact-matchBGP router identifier 172.20.1.1, local AS number 1820BGP main routing table version 55Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path* 10.13.0.0/16 192.168.40.24 0 1878 704 701 200 ?* 10.16.0.0/16 192.168.40.24 0 1878 704 701 iTable 10 describes the significant fields shown in the display.
Related Commands
show bgp convergence
To display whether a specific address family has reached convergence, use the show bgp convergence command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast | vpnv6 unicast] convergence
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
•
•
•
While testing that all selected routes have been advertised to peers, the show bgp convergence command 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 the show bgp summary command.
Task ID
Examples
The following shows the result of using the show bgp convergence command for an address family that has converged:
RP/0/RP0/CPU0:router# show bgp convergenceConverged.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:
RP/0/RP0/CPU0:router# show bgp convergenceNot converged.Received routes may not be entered in RIB.One or more neighbors may need updating.Table 11 describes the significant fields shown in the display.
Related Commands
show bgp dampened-paths
To display Border Gateway Protocol (BGP) dampened routes, use the show bgp dampened-paths command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] dampened-paths
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
Task ID
Examples
The following is sample output from the show bgp dampened-paths command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp dampened-pathsBGP router identifier 10.2.0.1, local AS number 3BGP generic scan interval 60 secsBGP main routing table version 7Dampening enabledBGP scan interval 60 secsStatus codes:s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes:i - IGP, e - EGP, ? - incompleteNetwork From Reuse Path*d 10.0.0.0 10.0.101.35 00:01:20 35 iTable 12 describes the significant fields shown in the display.
Related Commands
show bgp flap-statistics
To display information about Border Gateway Protocol (BGP) paths that have flapped, use the show bgp flap-statistics command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv4 unicast] | vpnv6 unicast [rd rd-address]] flap-statistics [regexp regular-expression | route-policy route-policy-name | cidr-only | {ip-address [{mask | /prefix-length} [longer-prefixes]] [detail]}]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
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.
Task ID
Examples
The following is sample output from the show bgp flap-statistics command:
RP/0/RP0/CPU0:router# show bgp flap-statisticsBGP router identifier 172.20.1.1, local AS number 1820BGP main routing table version 26180Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork From Flaps Duration Reuse Path*d 10.0.0.0 172.20.16.177 4 00:13:31 00:18:10 100*d 10.10.0.0 172.20.16.177 4 00:02:45 00:28:20 100The following is sample output from the show bgp flap-statistics command with the detail keyword in EXEC mode:
RP/0/RP0/CPU0:router# show bgp flap-statistics 172.31.12.166 detailBGP router identifier 10.0.0.5, local AS number 1BGP main routing table version 738Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork From Flaps Duration Reuse Pathh 172.31.12.166 10.0.101.1 6 00:03:28 2 2000 3000Half life Suppress Reuse penalty Max. supp. time00:15:00 2000 750 01:00:00Table 13 describes the significant fields shown in the display.
Related Commands
show bgp inconsistent-as
To display Border Gateway Protocol (BGP) routes originated from more than one autonomous system, use the show bgp inconsistent-as command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] inconsistent-as
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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-as command 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.
Task ID
Examples
The following is sample output from the show bgp inconsistent-as command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp inconsistent-asBGP router identifier 172.20.1.1, local AS number 1820BGP main routing table version 1129BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path* 10.0.0.0 172.16.232.55 0 0 300 88 90 99 ?*> 172.16.232.52 2222 0 400 ?* 172.16.0.0 172.16.232.55 0 0 300 90 99 88 200 ?*> 172.16.232.52 2222 0 400 ?* 192.168.199.0 172.16.232.55 0 0 300 88 90 99 ?*> 172.16.232.52 2222 0 400 ?Table 14 describes the significant fields shown in the display.
Related Commands
show bgp labels
To display Border Gateway Protocol (BGP) routes and their incoming and outgoing labels, use the show bgp labels command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all} | ipv6 {unicast | labeled-unicast} | {vpnv4 unicast | vpnv6 unicast} [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast}] | ipv6 unicast] labels
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show bgp labels command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp vrf BAR ipv4 unicast labelsBGP 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 12Status codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Rcvd Label Local LabelRoute Distinguisher: 100:1 (default for vrf BAR)*> 20.1.1.1/32 10.0.101.1 16 nolabel*> 20.1.1.2/32 10.0.101.1 16 nolabel*> 20.1.1.3/32 10.0.101.1 16 nolabel*> 20.1.1.4/32 10.0.101.1 16 nolabel*> 20.1.1.5/32 10.0.101.1 16 nolabelProcessed 5 prefixes, 5 pathsTable 15 describes the significant fields shown in the display.
Related Commands
show bgp neighbor-group
To display information about the Border Gateway Protocol (BGP) configuration for neighbor groups, use the show bgp neighbor-group command in EXEC mode.
show bgp neighbor-group group-name {configuration [defaults] [nvgen] | inheritance | users}
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
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 configuration. Use the nvgen keyword to display configuration in the output form of show running-config command. Output in this form is suitable for cutting and pasting into a configuration session.
The show 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.
The show bgp neighbor-group group-name command displays the neighbors and neighbor groups that inherit configuration from the specified neighbor group.
Task ID
Examples
The examples use the following configuration:
af-group group3 address-family ipv4 unicastremove-private-ASsoft-reconfiguration inbound!af-group group2 address-family ipv4 unicastuse af-group group3send-community-ebgpsend-extended-community-ebgpcapability orf prefix both!session-group group3dmzlink-bw!neighbor-group group3use session-group group3timers 30 90!neighbor-group group1remote-as 1982use neighbor-group group2address-family ipv4 unicast!!neighbor-group group2use neighbor-group group3address-family ipv4 unicastuse af-group group2weight 100!The following is sample output from the show bgp neighbor-group command with the configuration keyword:
RP/0/RP0/CPU0:router# show bgp neighbor-group group1 configurationneighbor-group group1remote-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]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:
RP/0/RP0/CPU0:router# show bgp neighbor-group group2 usersSession: n:group1IPv4 Unicast: n:group1The 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:
RP/0/RP0/CPU0:router# show bgp neighbor-group group1 inheritanceSession: n:group2 n:group3 s:group3IPv4 Unicast: n:group2 a:group2 a:group3Table 16 describes the significant fields shown in the display.
Related Commands
show bgp neighbors
To display information about Border Gateway Protocol (BGP) connections to neighbors, use the show bgp neighbors command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast] neighbors [performance-statistics | missing-eor]
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast] neighbors ip-address [advertised-routes | dampened-routes | flap-statistics | performance-statistics | received {prefix-filter | routes} | routes]
show bgp neighbors ip-address [configuration [defaults] [nvgen] | inheritance]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
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.
Task ID
Examples
The following is sample output from the show bgp neighbors command:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1BGP neighbor is 10.0.101.1, remote AS 2, local AS 1, external linkDescription: routem neighborRemote router ID 10.0.101.1BGP state = Established, up for 00:00:56TCP open mode: passive onlyBFD enabled (session initializing)Last read 00:00:55, hold time is 180, keepalive interval is 60 secondsDMZ-link bandwidth is 1000 Mb/sNeighbor capabilities:Route refresh: advertised4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedAddress family IPv4 Multicast: advertised and receivedReceived 119 messages, 0 notifications, 0 in queueSent 119 messages, 22 notifications, 0 in queueMinimum time between advertisement runs is 60 secondsFor Address Family: IPv4 UnicastBGP neighbor version 137Update group: 1.3Community attribute sent to this neighborAF-dependant capabilities:Outbound Route Filter (ORF) type (128) Prefix-list:Send-mode: advertisedReceive-mode: advertisedRoute refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all5 accepted prefixes, 5 are bestpathsPrefix advertised 3, suppressed 0, withdrawn 0, maximum limit 1000000Threshold for warning message 75%For Address Family: IPv4 MulticastBGP neighbor version 23Update group: 1.2Route refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all2 accepted prefixes, 2 are bestpathsPrefix advertised 0, suppressed 0, withdrawn 0, maximum limit 131072Threshold for warning message 75%Connections established 9; dropped 8Last reset 00:02:10, due to User clear requested (CEASE notification sent - administrative reset)Time since last notification sent to neighbor: 00:02:10Error Code: administrative resetNotification data sent:NoneTable 17 describes the significant fields shown in the display.
The following is sample output from the show bgp neighbors command with the advertised-routes keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.75 advertised-routesNetwork Next-hop From10.10.0.0/8 10.0.101.1 10.0.101.110.11.0.0/8 10.0.101.3 10.0.101.310.12.0.0/8 10.0.101.5 10.0.101.5The following is sample output from the show bgp neighbors command with the routes keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 172.20.16.178 routesBGP router identifier 172.20.16.181, local AS number 1BGP main routing table version 27BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path*> 10.0.0.0 172.20.16.178 40 0 10 ?*> 10.22.0.0 172.20.16.178 40 0 10 ?Table 18 describes the significant fields shown in the display.
The following is sample output from the show bgp neighbors command with the dampened-routes keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1 dampened-routesBGP router identifier 10.0.0.5, local AS number 1BGP main routing table version 48Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork From Reuse Path*d 10.0.0.0 10.0.101.1 00:59:30 2 100 1000 i*d 11.0.0.0 10.0.101.1 00:59:30 2 100 1000 i*d 12.0.0.0 10.0.101.1 00:59:30 2 100 1000 i*d 13.0.0.0 10.0.101.1 00:59:30 2 100 1000 i*d 14.0.0.0 10.0.101.1 00:59:30 2 100 1000 iTable 19 describes the significant fields shown in the display.
The following is sample output from the show bgp neighbors command with the flap-statistics keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1 flap-statisticsBGP router identifier 10.0.0.5, local AS number 1BGP main routing table version 48Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork From Flaps Duration Reuse Pathh 10.1.0.0 10.0.101.1 5008 2d02h 2 5000 1000h 10.2.0.0 10.0.101.1 5008 2d02h 2 2000 3000h 10.2.0.0 10.0.101.1 5008 2d02h 2 9000 6000*d 10.0.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000h 10.0.0.0/16 10.0.101.1 5008 2d02h 2 100 102*d 10.11.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000*d 10.12.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000*d 10.13.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000*d 10.14.0.0 10.0.101.1 5008 2d02h 00:59:30 2 100 1000h 192.168.0.0/16 10.0.101.1 5008 2d02h 2 100 101Table 20 describes the significant fields shown in the display.
The following is sample output from the show bgp neighbors command with the performance-statistics keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.2 performance-statisticsBGP neighbor is 10.0.101.2, remote AS 1Read 3023 messages (58639 bytes) in 3019 calls (time spent: 1.312 secs)Read throttled 0 timesProcessed 3023 inbound messages (time spent: 0.198 secs)Wrote 58410 bytes in 6062 calls (time spent: 3.041 secs)Processing write list: wrote 0 messages in 0 calls (time spent: 0.000 secs)Processing write queue: wrote 3040 messages in 3040 calls (time spent: 0.055 secs)Received 3023 messages, 0 notifications, 0 in queueSent 3040 messages, 0 notifications, 0 in queueTable 21 describes the significant fields shown in the display.
The following is sample output from the show bgp neighbors command with the configuration keyword:
RP/0/RP0/CPU0:router# show bgp neighbors 10.0.101.1 configurationneighbor 10.0.101.1remote-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 []Table 22 describes the significant fields shown in the display.
Related Commands-
show bgp nexthops
To display statistical information about the Border Gateway Protocol (BGP) next-hops, use the show bgp nexthops command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast] nexthops [statistics] [speaker speaker-id]
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The show bgp nexthops command displays statistical information about next-hop notifications, the time spent processing the notifications, and details about each next-hop that has been registered with the Routing Information Base (RIB).
Use the vrf vrf-name keyword and argument to display only the next-hops present in the specified VPN routing and forwarding (VRF) instance.
The next-hop information is displayed for all active speaker processes in distributed mode. Each speaker displays a set of next-hops that belongs to the prefixes received by the speaker and next-hops that belong to best paths that were received by other speaker processes. Use the speaker speaker-id keyword and argument to display information for only the specified speaker process. The distributed mode must be defined using the distributed speaker command for the speaker keyword to be available.
Task ID
Examples
The following is sample output from the show bgp nexthops command with the VRF specified:
RP/0/RP0/CPU0:router# show bgp vrf all nexthopsVRF: red========Total Nexthop ProcessingTime Spent: 0.001 secsMaximum Nexthop ProcessingReceived: 00:00:38Bestpath Deleted: 0Bestpath Changed: 150Time Spent: 1.000 msecsLast Notification ProcessingReceived: 00:00:38Time Spent: 1.000 msecsIPv4 Unicast is activeNexthop Count: 13Critical Trigger Delay: 6msecNon-critical Trigger Delay: 8msecTotal Critical Notifications Received: 5Total Non-critical Notifications Received: 0Bestpaths Deleted After Last Walk: 0Bestpaths Changed After Last Walk: 100Status codes: R/UR Reachable/UnreachableC/NC Connected/Not-connectedL/NL Local/Non-localI Invalid (Policy Match Failed)Next-hop Status Metric Notf LastRIBEvent RefCount12.0.1.1 [R][C][NL] 0 0/0 00:04:18 (Reg) 012.0.0.1 [R][C][NL] 0 0/0 00:04:18 (Reg) 012.0.2.1 [R][C][NL] 0 0/0 00:04:17 (Reg) 0100.5.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 30100.4.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 30100.7.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 40100.6.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 40100.1.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 30100.3.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 30100.2.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 30100.9.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 40100.8.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 40100.10.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 40VRF: blue=========Total Nexthop ProcessingTime Spent: 0.003 secsMaximum Nexthop ProcessingReceived: 00:00:38Bestpath Deleted: 0Bestpath Changed: 100Time Spent: 3.000 msecsLast Notification ProcessingReceived: 00:00:38Time Spent: 3.000 msecsIPv4 Unicast is activeNexthop Count: 12Critical Trigger Delay: 6msecNon-critical Trigger Delay: 8msecTotal Critical Notifications Received: 5Total Non-critical Notifications Received: 0Bestpath Deleted After Last Walk: 0Bestpath Changed After Last Walk: 50Status codes: R/UR Reachable/UnreachableC/NC Connected/Not-connectedL/NL Local/Non-localI Invalid (Policy Match Failed)Next-hop Status Metric Notf LastRIBEvent RefCount12.0.4.1 [R][C][NL] 0 0/0 00:04:17 (Reg) 012.0.3.1 [R][C][NL] 0 0/0 00:04:17 (Reg) 0200.9.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 20200.8.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 20200.10.0.1 [R][C][NL] 0 0/0 00:04:12 (Reg) 20200.1.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 20200.3.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 20200.2.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 20200.5.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 20200.4.0.1 [UR] 4294967295 1/0 00:00:38 (Cri) 20200.7.0.1 [R][C][NL] 0 0/0 00:04:13 (Reg) 20200.6.0.1 [R][C][NL] 0 0/0 00:04:13 (Reg) 20Table 23 describes the significant fields shown in the display.
Related Commands
show bgp paths
To display all the Border Gateway Protocol (BGP) paths in the database, use the show bgp paths command in EXEC mode.
show bgp paths [detail] [debug] [regexp regular-expression]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show bgp paths command to display information about AS paths and the associated attributes with which the paths were received.
If no options are specified, all stored AS paths are displayed with the number of routes using each path.
Note
Use the regular-expression argument to limit the output to only those paths that match the specified regular expression. See Cisco IOS XR Getting Started Guide for information on regular expressions.
Use the detail keyword to display detailed information on the attributes stored with the AS path.
Task ID
Examples
The following is sample output from the show bgp paths command:
RP/0/RP0/CPU0:router# show bgp paths detailProc Attributes Refcount Metric PathSpk 0 ORG AS LOCAL 7 0 iSpk 0 ORG AS LOCAL COMM EXTCOMM 3 0 21 iSpk 0 MET ORG AS 3 55 2 iSpk 0 ORG AS 3 0 2 10 11 iSpk 0 ORG AS COMM 3 0 2 10 11 iSpk 0 MET ORG AS ATOM 3 2 2 3 4 ?Spk 0 MET ORG AS 3 1 2 3 4 eSpk 0 MET ORG AS 3 0 2 3 4 iTable 24 describes the significant fields shown in the display.
show bgp policy
To display information about Border Gateway Protocol (BGP) advertisements under a proposed policy, use the show bgp policy command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | mdt | labeled-unicast | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] policy [neighbor ip-address] [sent-advertisements | route-policy route-policy-name] [summary]
Syntax Description
Defaults
Advertisements for all neighbors are displayed if the neighbor ip-address keyword and argument are not specified. If no address family or subaddress family is specified, the default address family and subaddress family specified using the set default-afi and set default-safi commands are used.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
BGP contains a separate routing table for each configured address family and subaddress family combination. The address family and subaddress family options specify the routing table to be examined. If the all keyword is specified for the address family or subaddress family, each matching routing table is examined in turn.
Use the show bgp policy command to display routes that would be advertised to neighbors under a proposed policy. Unlike in the show bgp advertised command, the information displayed reflects any modifications made to the routes when executing the specified policy.
Use the neighbor keyword to limit the output to routes advertised to a particular neighbor. Use the sent-advertisements keyword to change the output in two ways:
•
•
Use the summary keyword to display abbreviated output.
Task ID
Examples
The following is sample output from the show bgp policy command with the summary keyword in EXEC mode:
RP/0/RP0/CPU0:router# show bgp policy summaryNetwork Next-hop From Advertised to172.16.1.0/24 10.0.101.1 10.0.101.1 10.0.101.210.0.101.3172.17.0.0/16 0.0.0.0 Local 10.0.101.110.0.101.210.0.101.3Table 25 describes the significant fields shown in the display.
The following is sample output from the show bgp policy command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp policy11.0.0.0/24 is advertised to 10.4.101.1Path info:neighbor: Local neighbor router id: 10.4.0.1valid local bestAttributes after inbound policy was applied:next-hop: 0.0.0.0MET ORG ASorigin: IGP metric: 0aspath:Attributes after outbound policy was applied:next-hop: 10.4.0.1MET ORG ASorigin: IGP metric: 0aspath: 111.0.0.0/24 is advertised to 10.4.101.2Path info:neighbor: Local neighbor router id: 10.4.0.1valid local bestAttributes after inbound policy was applied:next-hop: 0.0.0.0MET ORG ASorigin: IGP metric: 0aspath:Attributes after outbound policy was applied:next-hop: 10.4.0.1MET ORG ASorigin: IGP metric: 0aspath:11.0.0.0/24 is advertised to 10.4.101.3Path info:neighbor: Local neighbor router id: 10.4.0.1valid local bestAttributes after inbound policy was applied:next-hop: 0.0.0.0MET ORG ASorigin: IGP metric: 0aspath:Attributes after outbound policy was applied:next-hop: 10.4.0.1MET ORG ASorigin: IGP metric: 0aspath:12.0.0.0/24 is advertised to 10.4.101.2Path info:neighbor: 10.4.101.1 neighbor router id: 10.4.101.1valid external bestAttributes after inbound policy was applied:next-hop: 10.4.101.1ORG ASorigin: IGP neighbor as: 2aspath: 2 3 4Attributes after outbound policy was applied:next-hop: 10.4.101.1ORG ASorigin: IGP neighbor as: 2aspath:2 3 412.0.0.0/24 is advertised to 10.4.101.3Path info:neighbor: 10.4.101.1 neighbor router id: 10.4.101.1valid external bestAttributes after inbound policy was applied:next-hop: 10.4.101.1ORG ASorigin: IGP neighbor as: 2aspath: 2 3 4Attributes after outbound policy was applied:next-hop: 10.4.101.1ORG ASorigin: IGP neighbor as: 2aspath:2 3 4Table 26 describes the significant fields shown in the display.
Related Commands
show bgp process
To display Border Gateway Protocol (BGP) process information, use the show bgp process command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vpvn6 unicast] process [performance-statistics] [detail]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Use the show bgp process command to display status and summary information for the Border Gateway Protocol (BGP) process. The output shows various global and address family-specific BGP configurations. A summary of the number of neighbors, update messages, and notification messages sent and received by the process is also displayed.
Use the detail keyword to display detailed process information. The detailed process information shows the memory used by each of various internal structure types.
Use the performance-statistics keyword to display a summary or detail of work done by the BGP processes. The summary display shows the real time spent performing certain operations and the time stamps for state transitions during initial convergence.
Task ID
Examples
The following is sample output from the show bgp process command:
RP/0/RP0/CPU0:router# show bgp processBGP Process InformationBGP is operating in STANDALONE modeAutonomous System: 1Router ID: 10.0.0.5 (manually configured)Cluster ID: 10.0.0.5Fast external fallover enabledNeighbor logging is enabledEnforce first AS enabledDefault local preference: 100Default keepalive: 60Update delay: 120Generic scan interval: 60Address family: IPv4 UnicastDampening is enabledClient reflection is enabledScan interval: 60Main Table Version: 150IGP notification: IGPs notifiedNode Process Nbrs Estab Rst Upd-Rcvd Upd-Sent Nfn-Rcvd Nfn-Sentnode0_0_CPU0 Speaker 3 2 1 20 10 0 0Table 27 describes the significant fields shown in the display.
The following is sample output from the show bgp process command with the detail keyword:
RP/0/RP0/CPU0:router# show bgp all all process detailBGP Process InformationBGP is operating in STANDALONE modeAutonomous System: 1Router ID: 10.0.0.5 (manually configured)Cluster ID: 10.0.0.5Fast external fallover enabledNeighbor logging is enabledEnforce first AS enabledDefault local preference: 100Default keepalive: 60Update delay: 120Generic scan interval: 60BGP Speaker process: 0, location node0_0_0Neighbors: 3, established: 2Sent ReceivedUpdates: 3 15Notifications: 0 0Number Memory UsedAttributes: 12 1104AS Paths: 10 400Communities: 2 1080Extended communities: 1 40Route Reflector Entries: 0 0Route-map Cache Entries: 0 0Filter-list Cache Entries: 0 0Next-hop Cache Entries: 2 80Update messages queued: 0Address family: IPv4 UnicastDampening is enabledClient reflection is enabledMain Table Version: 12IGP notification: IGPs notifiedState: normal mode.BGP Table Version: 12Network Entries: 15, Soft Reconfig Entries: 0Dampened Paths: 0, History Paths: 9Allocated FreedPrefixes: 15 0Paths: 19 0Number Memory UsedPrefixes: 15 1230Paths: 19 760Table 28 describes the significant fields shown in the display.
The following is sample output from the show bgp process command with the performance-statistics keyword:
RP/0/RP0/CPU0:router# show bgp process performance-statisticsBGP Process InformationBGP is operating in STANDALONE modeAutonomous System: 1Router ID: 10.0.0.5 (manually configured)Cluster ID: 10.0.0.5Fast external fallover enabledNeighbor logging is enabledEnforce first AS enabledDefault local preference: 100Default keepalive: 60Update delay: 120Generic scan interval: 60Address family: IPv4 UnicastDampening is not enabledClient reflection is enabledScan interval: 60Main Table Version: 10IGP notification: IGPs notifiedRIB has converged: version 0Address family: IPv4 MulticastDampening is not enabledClient reflection is enabledScan interval: 60Main Table Version: 3RIB has converged: version 0Address family: IPv6 UnicastDampening is not enabledClient reflection is enabledScan interval: 60Main Table Version: 3RIB has converged: version 0Address family: IPv6 MulticastDampening is not enabledClient reflection is enabledScan interval: 60Main Table Version: 1RIB has converged: version 0Node Process Read Write Inboundnode0_0_CPU0 Speaker 0.09 0.03 0.04Address Family IPv4 Unicast:Process Conv Nbr Estab Bestpath RIB Inst Read/Write Last UpdSpeaker No 0 120 120 120 121Address Family IPv4 Multicast:Process Conv Nbr Estab Bestpath RIB Inst Read/Write Last UpdSpeaker Yes 0 120 120 120 121Address Family IPv4 Multicast converged in 121 seconds.Address Family IPv6 Unicast:Process Conv Nbr Estab Bestpath RIB Inst Read/Write Last UpdSpeaker Yes 0 120 120 120 121Address Family IPv6 Unicast converged in 121 seconds.Address Family IPv6 Multicast:Process Conv Nbr Estab Bestpath RIB Inst Read/Write Last UpdSpeaker No 0 120 120 120 ---Table 29 describes the significant fields shown in the display.
The following is sample output from the show bgp process command with the performance-statistics and detail keywords:
RP/0/RP0/CPU0:router# show bgp process performance-statistics detailBGP Speaker process: 0, Node: node0_0_CPU0Restart count: 2Neighbors: 3, established: 2Sent ReceivedUpdates: 20 20Notifications: 0 0Number Memory UsedAttributes: 2 184AS Paths: 2 48Communities: 0 0Extended communities: 0 0Route Reflector Entries: 0 0Route-map Cache Entries: 0 0Filter-list Cache Entries: 0 0Next-hop Cache Entries: 2 80Update messages queued: 0Read 14 messages (1142 bytes) in 12 calls (time spent: 0.024 secs)Read throttled 0 timesProcessed 14 inbound messages (time spent: 0.132 secs)Wrote 2186 bytes in 24 calls (time spent: 0.024 secs)Processing write list: wrote 18 messages in 4 calls (time spent: 0.000 secs)Processing write queue: wrote 10 messages in 20 calls (time spent: 0.000 secs)Socket setup (LPTS): 4 calls (time spent: 0.010 secs)Configuration: 1 requests (time spent: 0.002 secs)Operational data: 9 requests (time spent: 0.026 secs)State: normal mode.BGP Table Version: 150Network Entries: 149, Soft Reconfig Entries: 0Allocated FreedPrefixes: 149 0Paths: 200 0Number Memory UsedPrefixes: 149 12516Paths: 200 8000Updates generated: 149 prefixes in 8 messages from 2 calls (time spent: 0.046 secs)Scanner: 2 scanner runs (time spent: 0.008 secs)RIB update: 1 rib update runs, 149 prefixes installed (time spent: 0.024 secs)Process has converged for IPv4 Unicast.First neighbor established: 1082604050sEntered DO_BESTPATH mode: 1082604055sEntered DO_RIBUPD mode: 1082604055sEntered Normal mode: 1082604055sLatest UPDATE sent: 1082604056sTable 30 describes the significant fields shown in the display.
Related Commands
show bgp regexp
To display routes matching the autonomous system path regular expression, use the show bgp regexp command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast] regexp regular-expression
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
BGP contains a separate routing table for each configured address family and subaddress family combination. The address family and subaddress family options specify the routing table to be examined. If the all keyword is specified for the address family or subaddress family, each matching routing table is examined in turn.
Use the show bgp regexp command to display all routes in the specified BGP table whose autonomous system path is matched by the specified regular expression.
Note
Task ID
Examples
The following is sample output from the show bgp regexp command:
RP/0/RP0/CPU0:router# show bgp regexp "^3 "BGP router identifier 10.0.0.5, local AS number 1BGP main routing table version 64BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path*>i172.20.17.121 10.0.101.2 100 0 3 2000 3000 i*>i10.0.0.0 10.0.101.2 100 0 3 100 1000 i*>i172.5.23.0/24 10.0.101.2 100 0 3 4 60 4378 iTable 31 describes the significant fields shown in the display.
Related Commands
show bgp route-policy
To display Border Gateway Protocol (BGP) information about networks that match an outbound route policy, use the show bgp route-policy command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | l all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] route-policy route-policy-name
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
BGP contains a separate routing table for each address family and subaddress family combination that has been configured. The address family and subaddress family options specify the routing table to be examined. If the all keyword is specified for the address family or subaddress family, each matching routing table is examined.
A route policy must be configured to use this command. When the show bgp route-policy command is entered, routes in the specified BGP table are compared with the specified route policy, and all routes passed by the route policy are displayed.
If a pass clause is encountered while the route policy is being applied to the route and the route policy processing completes without hitting a drop clause, the route is displayed. The route is not displayed if a drop clause is encountered, if the route policy processing completes without hitting a pass clause, or if the specified route policy does not exist.
The information displayed does not reflect modifications the policy might make to the route. To display such modifications, use the show bgp policy command.
Task ID
Examples
The following is sample output from the show bgp route-policy command in EXEC mode:
RP/0/RP0/CPU0:router# show bgp route-policy p1BGP router identifier 172.20.1.1, local AS number 1820BGP main routing table version 729Dampening enabledBGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path* 10.13.0.0/16 192.168.40.24 0 1878 704 701 200 ?* 10.16.0.0/16 192.168.40.24 0 1878 704 701 iTable 32 describes the significant fields shown in the display.
Related Commands
show bgp session-group
To display information about the Border Gateway Protocol (BGP) configuration for session groups, use the show bgp session-group command in EXEC mode.
show bgp session-group group-name {configuration [defaults] [nvgen] | inheritance | users}
Syntax Description
Defaults
No default behavior or value
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show bgp session-group command with the group-name configuration argument and keyword to display the effective configuration of a session group, including any configuration inherited from other session groups through application of the use command. The source for each configured command is also displayed.
Use the defaults keyword to display the value of all configuration, including default configuration. Use the nvgen keyword to display configuration in the form of the show running-config command output. Output in this form is suitable for cutting and pasting into a configuration session.
Use the show bgp session-group command with the group-name inheritance argument and keyword to display the session groups from which the specified session group inherits configuration.
Use the show bgp session-group command with the group-name users argument and keyword to display the neighbors, neighbor groups, and session groups that inherit configuration from the specified session group.
Task ID
Examples
For the example shown here, the following configuration is used:
session-group group3advertisement-interval 5dmzlink-bw!session-group group1use session-group group2update-source Loopback0!session-group group2use session-group group3ebgp-multihop 2The following example shows the show bgp session-group command with the configuration keyword:
RP/0/RP0/CPU0:router# show bgp session-group group1 configurationsession-group group1advertisement-interval 5[s:group2 s:group3]ebgp-multihop 2 [s:group2]update-source Loopback0 []dmzlink-bw [s:group2 s:group3]The source of each command is shown to the right of the command. For example, update-source is configured directly on session group group1. The dmzlink-bw command is inherited from session group group2, which in turn inherits it from session group group3.
The following example shows the show bgp session-group command with the users keyword:
RP/0/RP0/CPU0:router# show bgp session-group group2 usersIPv4 Unicast:a:group1The following example shows the show bgp session-group command with the inheritance keyword.
RP/0/RP0/CPU0:router# show bgp session-group group1 inheritanceSession:s:group2 s:group3The command output shows that the session group group1 directly uses the group2 session group. The group2 session group uses the group3 session group.
Table 33 describes the significant fields shown in the display.
Related Commands
Configures a BGP session group.
Displays information about the BGP configuration for neighbor groups.
Displays information about BGP connections to neighbors.
show bgp summary
To display the status of all Border Gateway Protocol (BGP) connections, use the show bgp summary command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpvn6 unicast] summary
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Use the show bgp summary command to display a summary of the neighbors for which the specified address family and subaddress family are enabled. If the neighbor does not have the specified address family and subaddress family enabled, it is not included in the output of the show command. If the all keyword is specified for the address family or subaddress family, a summary for each combination of address family and subaddress family is displayed in turn.
The table versions shown in the output (RcvTblVer, bRIB/RIB, SendTblVer, and TblVer) are specific to the specified address family and subaddress family. All other information is global.
The table versions provide an indication of whether BGP is up to date with all work for the specified address family and subaddress family.
•
•
Task ID
Examples
The following is sample output from the show bgp summary command:
RP/0/RP0/CPU0:router# show bgp summaryBGP router identifier 10.0.0.0, local AS number 2BGP generic scan interval 60 secsBGP table state: ActiveTable ID: 0xe0000000BGP main routing table version 1BGP scan interval 60 secsBGP is operating in STANDALONE mode.Process RecvTblVer bRIB/RIB LabelVer ImportVer SendTblVerSpeaker 1 0 1 1 0Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd10.0.101.0 0 2 0 0 0 0 0 00:00:00 Idle10.0.101.1 0 2 0 0 0 0 0 00:00:00 IdleTable 34 describes the significant fields shown in the display.
Table 34 show bgp summary Field Descriptions
BGP router identifier
IP address of the router.
local AS number
Autonomous system number set by the router bgp command.
BGP generic scan interval
Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP table state
State of the BGP database.
Table ID
BGP database identifier.
BGP main routing table version
Last version of the BGP database that was injected into the main routing table.
Dampening enabled
Displayed if dampening has been enabled for the routes in this BGP routing table.
BGP scan interval
Interval (in seconds) between scans of the BGP table specified by the address family and subaddress family.
BGP is operating in
Specifies BGP is operating in standalone mode.
Process
BGP process.
RecvTblVer
Last version used in the BGP database for received routes.
bRIB/RIB
Last version of the local BGP database that was injected into the main routing table.
LabelVer
Label version used in the BGP database for label allocation.
ImportVer
Last version of the local BGP database for importing routes.
SendTblVer
Latest version of the local BGP database that is ready to be advertised to neighbors.
Some configured eBGP neighbors do not have any policy
Some external neighbors exist that do not have both an inbound and outbound policy configured for every address family, using the route-policy (BGP) command. In this case, no prefixes are accepted and advertised to those neighbors.
Neighbor
IP address of a neighbor.
Spr
Speaker process that is responsible for the neighbor. Always 0.
AS
Autonomous system.
MsgRcvd
Number of BGP messages received from a neighbor.
MsgSent
Number of BGP messages sent to a neighbor.
TblVer
Last version of the BGP database that was sent to a neighbor.
InQ
Number of messages from a neighbor waiting to be processed.
OutQ
Number of messages waiting to be sent to a neighbor.
Up/Down
Length of time in (hh:mm:ss) that the BGP session has been in Established state, or the time since the session left Established state, if it is not established.
St/PfxRcd
If the BGP session is not established, the current state of the session. If the session is established, the number of prefixes the router has received from the neighbor.
If the number of prefixes received exceeds the maximum allowed (as set by the maximum-prefix command), "(PfxRcd)" appears.
If the connection has been shut down using the shutdown command, "(Admin)" appears.
If the neighbor is external and it does not have an inbound and outbound policy configured for every address family, an exclamation mark (!) is inserted at the end of the state when using the route-policy (BGP) command.
If the connection has been shut down due to out of memory (OOM), "(OOM)" appears.
Related Commands
show bgp truncated-communities
To display routes in the Border Gateway Protocol (BGP) routing table for which inbound policy or aggregation has exceeded the maximum number of communities that may be attached, use the show bgp truncated-communities command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast [rd rd-address] | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast [rd rd-address]] truncated-communities
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
BGP contains a separate routing table for each address family and subaddress family combination that has been configured. The address family and subaddress family options specify the routing table to be examined. If the all keyword is specified for the address family or subaddress family, each matching routing table is examined.
Use the show bgp truncated-communities command to display those routes in the specified BGP routing table in which the buffers used to store communities or extended communities have overflowed. An overflow occurs if an attempt is made to associate more communities or extended communities with the route than fits in a BGP update message. This can happen due to modification of communities or extended communities during aggregration or when inbound policy is applied.
Task ID
Examples
The following is sample output from the show bgp truncated-communities command:
RP/0/RP0/CPU0:router# show bgp truncated-communitiesBGP router identifier 172.20.1.1, local AS number 1820BGP main routing table version 3042BGP scan interval 60 secsStatus codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next-hop Metric LocPrf Weight Path* 10.13.0.0/16 192.168.40.24 0 1878 704 701 200 ?*> 10.16.0.0/16 192.168.40.24 0 1878 704 701 iTable 35 describes the significant fields shown in the display.
Related Commands
show bgp update-group
To display Border Gateway Protocol (BGP) information for update groups, use the show bgp update-group command in EXEC mode.
show bgp [ipv4 {unicast | multicast | labeled-unicast | all | tunnel | mdt} | ipv6 {unicast | multicast | all | labeled-unicast} | all {unicast | multicast | all | labeled-unicast | mdt | tunnel} | vpnv4 unicast | vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] | vpnv6 unicast] update-group [neighbor ip-address | process-id.index [summary | performance-statistics]]
Syntax Description
Defaults
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.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Every BGP neighbor is automatically assigned to an update group for each address family that is enabled on the neighbor. Neighbors that have similar outbound policy, such that they are sent the same updates, are placed in the same update group.
Use the show bgp update-group command to display the update groups and a list of the neighbors that belong to the update group.
Use the show bgp update-group neighbor command to display details about the update group to which a neighbor belongs for the specified address family.
Use the summary keyword to display a summary of the neighbors belonging to the specified update group. The display format is the same as for the show bgp summary command.
Use the performance-statistics keyword to display information about the number of prefixes processed and the time taken to generate updates for the specified update group.
Note
Task ID
Examples
The following is sample output from the show bgp update-group command:
RP/0/RP0/CPU0:router# show bgp update-groupUpdate group for IPv4 Unicast, index 0.1:Attributes:InternalCommon adminSend communitiesSend extended communitiesMinimum advertisement interval: 300Update group desynchronized: 0Sub-groups merged: 0Messages formatted: 0, replicated: 0Neighbors not in any sub-group:10.0.101.1Table 36 describes the significant fields shown in the display.
The following is sample output from the show bgp update-group command with the ipv4, unicast, and summary keywords and the process id.index argument:
RP/0/RP0/CPU0:router# show bgp ipv4 unicast update-group 0.1 summaryBGP router identifier 10.140.140.1, local AS number 1.1BGP generic scan interval 60 secsBGP table state: ActiveTable ID: 0xe0000000BGP main routing table version 1BGP scan interval 60 secsBGP is operating in STANDALONE mode.Process RecvTblVer bRIB/RIB LabelVer ImportVer SendTblVerSpeaker 1 0 1 1 0Neighbor Spr AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd172.25.11.8 0 1 0 0 0 0 0 00:00:00 IdleTable 37 describes the significant fields shown in the display.
Table 37 show bgp ipv4 unicast update-group Field Descriptions
BGP router identifier
IP address of the router.
local AS number
Autonomous system number set by the router bgp command.
BGP generic scan interval
Interval (in seconds) between scans of the BGP table by a generic scanner.
BGP table state
State of the BGP database.
Table ID
BGP database identifier.
BGP main routing table version
Last version of the BGP database that was injected into the main routing table.
Dampening enabled
Displayed if dampening has been enabled for the routes in this BGP routing table.
BGP scan interval
Interval (in seconds) between scans of the BGP table specified by the address family and subaddress family.
BGP is operating in
BGP is operating in standalone mode.
Process
BGP process.
RecvTblVer
Last version used in the BGP database for received routes.
bRIB/RIB
Last version of the local BGP database that was injected into the main routing table.
LabelVer
Label version used in the BGP database for label allocation.
ImportVer
Last version of the local BGP database for importing routes.
SendTblVer
Latest version of the local BGP database that is ready to be advertised to neighbors.
Some configured eBGP neighbors do not have any policy
Some external neighbors that exist do not have both an inbound and outbound policy configured for every address family, using the route-policy (BGP) command. In this case, no prefixes are accepted or advertised to those neighbors.
Neighbor
IP address of a neighbor.
Spr
Speaker process that is responsible for the neighbor. Always 0.
AS
Autonomous system.
MsgRcvd
Number of BGP messages received from a neighbor.
MsgSent
Number of BGP messages sent to a neighbor.
TblVer
Last version of the BGP database that was sent to a neighbor.
InQ
Number of messages from a neighbor waiting to be processed.
OutQ
Number of messages waiting to be sent to a neighbor.
Up/Down
Length of time (in hh:mm:s) that the BGP session has been in Established state, or the time since the session left Established state, if it is not established.
St/PfxRcd
If the BGP session is not established, the current state of the session. If the session is established, the number of prefixes the router has received from the neighbor.
If the number of prefixes received exceeds the maximum allowed (as set by the maximum-prefix command), "(PfxRcd)" appears.
If the connection has been shut down using the shutdown command, "(Admin)" appears.
If the neighbor is external and it does not have an inbound and outbound policy configured for every address family, an exclamation mark (!) is inserted at the end of the state when using the route-policy (BGP) command.
Related Commands
show bgp vrf imported-routes
To display Border Gateway Protocol (BGP) information for routes imported into specified VPN routing and forwarding (VRF) instances, use the show bgp vrf imported-routes command in EXEC mode.
show bgp vrf {vrf-name | all} [ipv4 {unicast | labeled-unicast} | ipv6 unicast] imported-routes [vrf source-vrf-name] [neighbor neighbor-address]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show bgp vrf imported-routes command to display all paths imported into a specified VRF from the default VRF. Use the neighbor neighbor-address keyword and argument to display all imported paths and which paths were learned from the specified neighbor. Use the vrf source-vrf-name keyword and argument to display all imported routes that belong to the specified source VRF. The neighbor neighbor-address and vrf source-vrf-name cannot coexist.
Task ID
Examples
The following is sample output from the show bgp vrf imported-routes command:
RP/0/RP0/CPU0:router# show bgp vrf vrf-1 ipv6 unicast imported-routesBGP VRF one, state: Active BGPBGP Route Distinguisher: 100:222VRF ID: 0x60000001BGP router identifier 10.2.0.1, local AS number 100BGP table state: ActiveTable ID: 0xe0800001BGP main routing table version 41534Status codes: s suppressed, d damped, h history, * valid, > besti - internal, S staleOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Neighbor Route Distinguisher Source VRF*>i1234:1052::/32 10.1.0.1 100:111 default*>i2008:1:1:1::/112 10.1.0.1 100:111 default*>i2008:111:1:1::1/12810.1.0.1 100:111 defaultProcessed 3 prefixes, 3 pathsTable 38 describes the significant fields shown in the display.
Table 38 show bgp vrf imported-routes Field Descriptions
BGP VRF
VRF name.
state
State of the VRF.
BGP Route Distinguisher:
Unique identifier for the BGP routing instance.
VRF Id
VRF identifier.
BGP router identifier
IP address of the router.
local AS number
Autonomous system number set by the router bgp command.
BGP table state
State of the BGP database.
Table ID
Table identifier.
BGP main routing table version
Last version of the BGP database that was injected into the main routing table.
Network
Network address.
Neighbor
IP address of a neighbor.
Route Distinguisher
Unique identifier for the routing instance.
Source VRF
Source VRF for the imported route.
show protocols (BGP)
To display information about the Border Gateway Protocol (BGP) instances running on the router, use the show protocols command in EXEC mode and specify either the bgp or all keyword.
show protocols [ipv4 | ipv6 | afi-all] [all | protocol]
Syntax Description
Defaults
Default is IPv4.
Command Modes
EXEC
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show protocols command to get information about the protocols running on the router and to quickly determine which protocols are active. The command is designed to summarize the important characteristics of the running protocol, and command output varies depending on the specific protocol selected. For BGP, the command output lists the protocol ID, peers with elapsed time since last reset, and miscellaneous information, such as external and internal local distances and sourced routes.
Task ID
Examples
The following example shows the display for the show protocols command using the bgp keyword:
RP/0/RP0/CPU0:router# show protocols bgpRouting Protocol "BGP 40"Address Family IPv4 Unicast:Distance: external 20 internal 200 local 200Sourced Networks:10.100.0.0/16 backdoor10.100.1.0/2410.100.2.0/24Routing Information Sources:Neighbor State/Last update received10.5.0.2 Idle10.9.0.3 IdleTable 39 describes the significant fields shown in the display.
shutdown (BGP)
To disable a neighbor without removing its configuration, use the shutdown command in an appropriate configuration mode. To re-enable the neighbor and reestablish a Border Gateway Protocol (BGP) session, use the no form of this command.
shutdown [disable]
no shutdown [disable]
Syntax Description
disable
(Optional) Overrides the value of a shutdown command inherited from a neighbor group or session group.
Defaults
Neighbors are not shutdown.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the shutdown command to terminate any active session for the specified neighbor and remove all associated routing information. Use of the shutdown command with a neighbor group or session group may suddenly terminate a large number of BGP neighbor sessions because all neighbors using the neighbor group or session group may be affected.
Use the show bgp summary command to display a summary of BGP neighbors. Neighbors that are idle due to the shutdown command are displayed with the "Idle (Admin)" state.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
Examples
The following example shows that any active session for neighbor 192.168.40.24 is disabled:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# shutdownRP/0/RP0/CPU0:router(config-bgp-nbr)# exitIn the following example, the session remains active for neighbor 192.168.40.24 because the inherited shutdown command has been overridden:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group group1RP/0/RP0/CPU0:router(config-bgp-sngrp)# shutdownRP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1RP/0/RP0/CPU0:router(config-bgp-nbr)# shutdown disableRP/0/RP0/CPU0:router(config-bgp-nbr)# exitRelated Commands
site-of-origin (BGP)
To attach a site-of-origin extended community attribute to each route received from the specified peer, use the site-of-origin command in VRF neighbor address family configuration mode. To restore the system to its default condition, use the no form of this command.
site-of-origin [as-number:nn | ip-address:nn]
no site-of-origin [as-number:nn | ip-address:nn]
Syntax Description
as-number:nn
Autonomous system (AS) number.
•
•
ip-address:nn
IP address.
•
•
Defaults
No default behavior or values
Command Modes
VRF neighbor address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When routes are advertised to the peer, routes whose extended communities list contain the site of origin (SoO) are filtered out and not advertised to the peer. Site-of-origin uniquely identifies the site from which the provide edge (PE) router learned routes, thus filtering based on the extended community helps prevent transient routing loops from occurring in complex and mixed network topologies.
Task ID
Examples
The following example shows how to configure SoO filtering:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# vrf vrf_ARP/0/RP0/CPU0:router(config-bgp-vrf)# neighbor 192.168.70.24RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# remote-as 10RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-vrf-nbr-af)# site-of-origin 10.0.01:20socket receive-buffer-size
To set the size of the receive buffers for all Border Gateway Protocol (BGP) neighbors, use the socket receive-buffer-size command in an appropriate configuration mode. To set the size of the receive buffers to the default size, use the no form of this command.
socket receive-buffer-size socket-size [bgp-size]
no socket receive-buffer-size [socket-size] [bgp-size]
Syntax Description
socket-size
Size (in bytes) of the receive-side socket buffers. Range is 512 to 131072.
bgp-size
(Optional) Size (in bytes) of the receive buffers in BGP. Range is 512 to 131072.
Defaults
socket-size: 32,768 bytes
bgp-size: 4,032 bytesCommand Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the socket receive-buffer-size command to increase the buffer size when receiving updates from a neighbor. Using larger buffers can improve convergence time because the software can process more packets simultaneously. However, allocating larger buffers uses more memory on your router.
Note
Use the receive-buffer-size command on individual neighbors to change the values set by the socket receive-buffer-size command.
Task ID
Examples
The following example shows how to set the receive buffer sizes for all neighbors to 65,536 bytes for the socket buffer and 8192 bytes for the BGP buffer:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# socket receive-buffer-size 65536 8192Related Commands
Sets the size of the receive buffers for a BGP neighbor.
Sets the size of the send buffers for all BGP neighbors.
socket send-buffer-size
To set the size of the send buffers for all Border Gateway Protocol (BGP) neighbors, use the socket send-buffer-size command in an appropriate configuration mode. To set the size of the send buffers to the default size, use the no form of this command.
socket send-buffer-size socket-size [bgp-size]
no socket send-buffer-size [socket-size] [bgp-size]
Syntax Description
socket-size
Size (in bytes) of the send-side socket buffers. Range is 4096 to 131072.
bgp-size
(Optional) Size (in bytes) of the send buffers in BGP. Range is 4096 to 131072.
Defaults
socket-size: 10240 bytes
bgp-size: 4096 bytesCommand Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the socket send-buffer-size command to increase the buffer size when sending updates to neighbors. Using larger buffers can improve convergence time because the software can process more packets simultaneously. However, allocating larger buffers uses more memory on your router.
Note
Use the send-buffer-size command on individual neighbors to change the values set by the socket send-buffer-size command.
Task ID
Examples
The following example shows how to set the send buffer sizes for all neighbors to 8192 bytes for the socket buffer and the BGP buffer:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# socket send-buffer-size 8192 8192Related Commands
Sets the size of the send buffers for a BGP neighbor.
Sets the size of the receive buffers for all BGP neighbors.
soft-reconfiguration inbound
To configure the software to store updates received from a neighbor, use the soft-reconfiguration inbound command in an appropriate configuration mode. To disable storing received updates, use the no form of this command.
soft-reconfiguration inbound [always | disable]
no soft-reconfiguration inbound [always | disable]
Syntax Description
Defaults
Soft reconfiguration is not enabled.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
VPNv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VRF IPv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
To filter or modify some of the updates received from a neighbor, you configure an inbound policy using the route-policy (BGP) command. Configuring soft reconfiguration inbound causes the software to store the original unmodified route beside a route that is modified or filtered. This allows a "soft clear" to be performed after the inbound policy is changed. To perform a soft clear, use the clear bgp soft command with the in keyword specified. The unmodified routes are then passed through the new policy and installed in the BGP table.
Note
Note
If the neighbor supports the route refresh capability, then the original routes are not stored because they can be retrieved from the neighbor through a route refresh request. However, if the always keyword is specified, the original routes are stored even when the neighbor supports the route refresh capability.
If the soft-reconfiguration inbound command is not configured and the neighbor does not support the route refresh capability, then an inbound soft clear is not possible. In that case, the only way to rerun the inbound policy is to use the clear bgp ip-address command to reset the neighbor BGP session.
Note
Note
If you configure this command for a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
Examples
The following example shows inbound soft reconfiguration enabled for IP Version 4 (IPv4) unicast routes received from neighbor 10.108.1.1. The software stores all routes received in their unmodified form so that when an inbound soft clear is performed later, the stored information can then be used to generate a new set of modified routes.
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.108.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# soft-reconfiguration inboundRP/0/RP0/CPU0:router(config-bgp-nbr-af)# exitThe following example shows inbound soft reconfiguration disabled for neighbor 10.108.1.1, preventing this feature from being automatically inherited by address family group group1:
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# soft-reconfiguration inboundRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.108.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# soft-reconfiguration inbound disableRP/0/RP0/CPU0:router(config-bgp-nbr-af)# exitRelated Commands
speaker-id
To allocate a speaker process to a neighbor, use the speaker-id command in the appropriate configuration mode. To remove the speaker process from a neighbor, use the no form of this command.
speaker-id id
no speaker-id [id]
Syntax Description
Defaults
Default is 0.
Command Modes
Neighbor configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to allocate speaker process 3 to neighbor 192.168.40.24:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# speaker-id 3Related Commands
table-policy
To apply a routing policy to routes being installed into the routing table, use the table-policy command in an appropriate configuration mode. To disable applying a routing policy when installing routes into the routing table, use the no form of this command.
table-policy policy-name
no table-policy [policy-name]
Syntax Description
Defaults
No policy is applied when routes are installed into the routing table.
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Note
Use the table-policy command to modify route attributes as the routes are installed into the routing table by Border Gateway Protocol (BGP). Commonly, it is used to set the traffic index attribute.
Task ID
Examples
The following example shows how to apply the set-traffic-index policy to IPv4 unicast routes being installed into the routing table:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# table-policy set-traffic-indexRelated Commands
timers (BGP)
To set the timers for a specific Border Gateway Protocol (BGP) neighbor, use the timers command in an appropriate configuration mode. To set the timers to the default values, use the no form of this command.
timers keepalive hold-time
no timers [keepalive hold-time]
Syntax Description
Defaults
keepalive: 60 seconds
hold-time: 180 seconds
Use the timers bgp command to override the default values.Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The timers actually used in connection with the neighbor may not be the same as those configured with this command. The actual timers are negotiated with the neighbor when establishing the session. The negotiated hold time is the minimum of the configured time and the hold time received from the neighbor. If the negotiated hold time is 0, keepalives are disabled.
The configured value for the keepalive must not exceed one-third of the negotiated hold time. If it does, a value of one-third of the negotiated hold time is used.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
Examples
The following example shows how to change the keepalive timer to 70 seconds and the hold-time timer to 210 seconds for the BGP peer 192.168.40.24:
RP/0/RP0/CPU0:router(config)# router bgp 109RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# timers 70 210RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRelated Commands
timers bgp
To change the default timer values for Border Gateway Protocol (BGP) neighbors, use the timers bgp command in an appropriate configuration mode. To set the default timers to the default values, use the no form of this command.
timers bgp keepalive hold-time
no timers bgp [keepalive hold-time]
Syntax Description
Defaults
keepalive: 60 seconds
hold-time: 180 secondsCommand Modes
Router configuration
VRF configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the timers bgp command to adjust the default timer times used by all BGP neighbors. The values can be overridden on particular neighbors using the timers command in the neighbor configuration mode.
The timers actually used in connection with the neighbor may not be the same as those configured with this command. The actual timers are negotiated with the neighbor when establishing the session. The negotiated hold time is the minimum of the configured time and the hold time received from the neighbor. If the negotiated hold time is 0, keepalives are disabled.
The configured value for the keepalive must not exceed one-third of the negotiated hold time. If it does, a value of one-third of the negotiated hold time is used.
Task ID
Examples
The following example shows how to configure a default keepalive time of 30 seconds and a default hold time of 90 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# timers bgp 30 90Related Commands
ttl-security
To configure a router to check the time-to-live (TTL) field in incoming IP packets for the specified external Border Gateway Protocol (eBGP) peer, use the ttl-security command in an appropriate configuration mode. To disable TTL verification, use the no form of this command.
ttl-security [disable]
no ttl-security [disable]
Syntax Description
disable
(Optional) Prevents the ttl-security command from being inherited from a session group or neighbor group.
Defaults
TTL verification is not enabled for eBGP peers.
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the ttl-security command to enable a lightweight security mechanism to protect eBGP peering sessions from CPU utilization-based and other resource exhaustion-based attacks. These types of attacks are typically brute-force Denial of Service (DoS) attacks that attempt to disable the network by flooding devices in the network with IP packets that contain forged source and destination IP addresses in the packet headers.
This command leverages existing behavior in IP packets. For a given IP packet, the TTL count of the packet always is equal to or less than the TTL count when the packet originated, a behavior that is considered impossible to circumvent. Therefore, a packet received with a TTL count equal to the maximum TTL value of 255 can be sent only by a directly adjacent peer. When the ttl-security command is configured for an eBGP neighbor that is directly adjacent, the router accepts only IP packets with a TTL count that is equal to the maximum TTL value.
The ttl-security command secures the eBGP session in the incoming direction only. In the outbound direction, it causes packets to be sent only with the maximum TTL value so that the BGP neighbor can also verify the TTL value of incoming packets. When this command is enabled, BGP establishes or maintains a session only if the TTL value in the IP packet header is equal to the maximum TTL value. If the value is less than the maximum TTL value, the packet is discarded and an Internet Control Message Protocol (ICMP) message is not generated. This behavior is designed because a response to a forged packet is not necessary.
Note
The following restrictions apply to the configuration of this command:
•
•
•
If you configure this command 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.
Note
Task ID
Examples
The following example shows how to enable TTL security for eBGP neighbor 192.168.223.7:
RP/0/RP0/CPU0:router(config)# router bgp 65534RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.223.7RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65507RP/0/RP0/CPU0:router(config-bgp-nbr)# ttl-securityThe following example shows how to enable TTL security for multiple eBGP neighbors using a session group:
RP/0/RP0/CPU0:router(config)# router bgp 65534RP/0/RP0/CPU0:router(config-bgp)# session-group ebgp-nbrsRP/0/RP0/CPU0:router(config-bgp-sngrp)# ttl-securityRP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.223.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65501RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group ebgp-nbrsRP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.223.2RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65502RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group ebgp-nbrsRP/0/RP0/CPU0:router(config-bgp-nbr)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.223.3RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65503RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group ebgp-nbrsRP/0/RP0/CPU0:router(config-bgp-nbr)# exitRelated Commands
update-source
To allow internal Border Gateway Protocol (iBGP) sessions to use the primary IP address from a particular interface as the local address when forming an iBGP session with a neighbor, use the update-source command in an appropriate configuration mode. To set the chosen local IP address to the nearest interface to the neighbor, use the no form of this command.
update-source interface-type interface-number
no update-source [interface-type interface-number]
Syntax Description
Defaults
Best local address
Command Modes
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The update-source command is commonly used with the loopback interface feature for iBGP sessions. The loopback interface is defined, and the interface address is used as the endpoint for a BGP session through the update-source command. This mechanism allows a BGP session to remain up even if the outbound interface goes down, provided there is another route to the neighbor.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
Examples
The following example shows how to configure this router to use the IP address from the Loopback0 interface when trying to open a session with neighbor 172.20.16.6:
RP/0/RP0/CPU0:router(config)# router bgp 110RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.16.6RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 110RP/0/RP0/CPU0:router(config-bgp-nbr)# update-source Loopback0Related Commands
Creates a neighbor group and enters neighbor group configuration mode.
Creates a session group and enters session group configuration mode.
use
To inherit configuration from a neighbor group, session group, or address family group, use the use command in an appropriate configuration mode. To discontinue inheritance from a group, use the no form of this command.
use {af-group group-name | neighbor-group group-name | session-group group-name}
no use {af-group [group-name] | neighbor-group [group-name] | session-group [group-name]}
Syntax Description
Defaults
Inheritance of group characteristics does not occur.
Command Modes
For use af-group version:
Address family group configuration
Neighbor address family configuration
Neighbor group address family configurationFor use neighbor-group version:
Neighbor group configuration
Neighbor configuration
VRF neighbor configurationFor use session-group version:
Neighbor group configuration
Neighbor configuration
VRF neighbor configuration
Session-group configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The use command configures inheritance of configuration from an address family group, neighbor group, or session group, which means that any configuration for the group also takes effect for the user of the group.
The configuration inherited depends on the type of group that is specified. The group types are described in the following sections:
Address Family Group
An address family group can specify a configuration for only a single address family. The address family specified when the address family group was defined (through the af-group command) must match the address family from which the group is used.
Neighbor Group
A neighbor group (like a neighbor) can have address family-independent configuration and address family-specific configuration. All of these configurations could be inherited.
Session Group
A session group can have only address family-independent configuration and thus only address family-independent configuration is inherited from it.
The following rules govern inheritance to resolve possible conflicting configuration:
1.
2.
3.
–
–
Typically, all configuration for a neighbor group is inherited, but some characteristics may be masked by a session group or address family group. For an example of this configuration, see the "Examples" section.
If the neighbor is using both a session group and a neighbor group and a specific command is configured for the neighbor group but not for the session group, then the configuration for the neighbor group does not take effect. The session group "hides" all address family-independent configuration on the neighbor group and prevents it from being inherited. Similarly, the use of an address family group hides any address family-specific configuration that may otherwise be inherited from a neighbor group for that address family.
In addition to neighbors using groups, it is possible to build a hierarchy by having groups use other groups. The following hierarchical groups are permitted:
•
•
•
•
Note
Task ID
Examples
The following example shows how to define a session group session1 and configure neighbor 172.168.40.24 to use session1. As a result, the session1 configuration takes effect on the neighbor also.
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group session1RP/0/RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 40RP/0/RP0/CPU0:router(config-bgp-sngrp)# timers 30 90RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group session1RP/0/RP0/CPU0:router(config-bgp-nbr)# exitThe following example is similar to the previous example, but in this case the timers command on the session group does not take effect on the neighbor because it is overridden by a timers command directly configured for the neighbor.
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group session1RP/0/RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 40RP/0/RP0/CPU0:router(config-bgp-sngrp)# timers 30 90RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group session1RP/0/RP0/CPU0:router(config-bgp-nbr)# timers 60 180RP/0/RP0/CPU0:router(config-bgp-nbr)# exitThe following example shows an address family group, family1, for IPv4 multicast and a neighbor group, neighbor1, that have IPv4 unicast and IPv4 multicast enabled. In this case, the neighbor inherits IPv4 unicast (and address family-independent) configuration from the neighbor group, but inherits IPv4 multicast configuration from the address family group. In this example, the neighbor group also has a remote autonomous system configured, so there is no need to configure a remote autonomous system for the neighbor because it inherits the remote autonomous system from the neighbor group:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# af-group family1 address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# route-policy mcast-in inRP/0/RP0/CPU0:router(config-bgp-afgrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor-group neighbor1RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# remote-as 2RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 inRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 outRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exitRP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 inRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-policy policy1 outRP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# use neighbor-group neighbor1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group family1RP/0/RP0/CPU0:router(config-bgp-nbr-af)# exitIn the previous example, the neighbor uses the policy1 route policy for inbound and outbound IPv4 unicast routes, but uses the mcast-in route policy for inbound IPv4 multicast routes and no policy for outbound IPv4 multicast routes.
The following example shows a neighbor inheriting configuration from a session group that likewise inherits configuration from another session group. The configuration from both session groups take effect on the neighbor:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# session-group session1RP/0/RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 40RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# session-group session2RP/0/RP0/CPU0:router(config-bgp-sngrp)# use session-group session1RP/0/RP0/CPU0:router(config-bgp-sngrp)# update-source Loopback0RP/0/RP0/CPU0:router(config-bgp-sngrp)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 172.168.40.24RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group session2RP/0/RP0/CPU0:router(config-bgp-nbr)# exitRelated Commands
vrf (BGP)
To configure a VPN routing and forwarding (VRF) instance and enter VRF configuration mode, use the vrf command in router configuration mode. To remove the VRF instance from the configuration file and restore the system to its default condition, use the no form of this command.
vrf vrf-name
no vrf vrf-name
Syntax Description
Defaults
No default behavior or values
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the vrf command to configure a VRF instance. A VRF instance is a collection of VPN routing and forwarding tables maintained at the provider edge (PE) router.
Task ID
Examples
The following example shows how to configure a VRF instance and enter VRF configuration mode:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# vrf vrf-1RP/0/RP0/CPU0:router(config-bgp-vrf)#weight
To assign a weight to routes received from a neighbor, use the weight command in an appropriate configuration mode. To remove the weight command from the configuration file and restore the system to its default condition in which the software assigns the default weight to routes, use the no form of this command.
weight weight-value
no weight [weight-value]
Syntax Description
Defaults
Routes learned through another Border Gateway Protocol (BGP) peer have a default weight of 0 and routes sourced by the local router have a default weight of 32768.
Command Modes
IPv4 address family group configuration
IPv6 address family group configuration
VPNv4 address family group configuration
IPv4 neighbor address family configuration
VPNv4 neighbor address family configuration
VRF IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
VPNv4 neighbor group address family configuration
VPNv6 address family group configuration
VPNv6 neighbor address family configuration
VRF IPv6 neighbor address family configuration
VPNv6 neighbor group address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The weight of a route is a Cisco-specific attribute. It is used in the best-path selection process (as the strongest tie-breaker). See the Implementing BGP on Cisco IOS XR Software module of Cisco IOS XR Routing Configuration Guide for information on best path. If there are two BGP routes with the same network layer reachability information (NLRI), the route with the higher weight is always chosen no matter what the value of other BGP attributes. Weight only has significance on the local router. Weight is assigned locally to the router, is a value that only makes sense to the specific router, is not propagated or carried through any route updates, and never is sent between BGP peers (even within the same AS).
Note
The weight assigned to individual routes can be further manipulated in the inbound route policy of a neighbor using the set weight command. The set weight command sets the weight directly. If you have particular neighbors that you want to prefer for most of your outbound traffic, you can assign a higher weight to all routes learned from that neighbor.
The weight assigned to individual routes may be modified by using an inbound routing policy.
Note
If this command configures a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
Examples
The following example shows how to assign a weight of 50 to all IP Version 4 (IPv4) unicast routes learned through 172.20.16.6:
RP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.16.6RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)# weight 50RP/0/RP0/CPU0:router(config-bgp-nbr-af)# exitRelated Commands
