This chapter describes the commands used to configure and monitor Border Gateway Protocol (BGP) on Cisco NCS 5000 Series Routers using Cisco IOS XR software. The commands in this module configure IP Version 4 (IPv4), IP Version 6 (IPv6), Virtual Private Network Version 4 (VPNv4) routing sessions.
For detailed information about BGP concepts, configuration tasks, and examples, see the Implementing BGP chapter in the BGP Configuration Guide for Cisco NCS 5000 Series Routers.
![]() Note | Currently, only default VRF is supported. VPNv4, VPNv6 and VPN routing and forwarding (VRF) address families will be supported in a future release. |
To enable handling of self-originated VPN routes containing ACCEPT_OWN community attribute, use the accept-own command in neighbor VPNv4 or VPNv6 address family configuration mode. To disable this functionality, either use the no form of this command or use the command with inheritance-disable keyword.
accept-own [inheritance-disable]
no accept-own
inheritance-disable |
Disables handling of self-originated VPN routes containing ACCEPT_OWN community attribute and prevents inheritance of Accept Own from a parent configuration. |
Disabled
Neighbor address family VPNv4
Neighbor address family VPNv6
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to enable handling of accept-own community:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)#address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)#accept-own
To install a backup path into the forwarding table and provide prefix independent convergence (PIC) in case of a PE-CE link failure, use the additional-paths install backup command in an appropriate address family configuration mode. To prevent installing the backup path, use the no form of this command. To disable prefix independent convergence, use the disable keyword.
![]() Note | This feature is not supported. |
additional-paths install backup [ disable ]
no additional-paths install backup
disable |
Disables installing backup path into the forwarding table. |
None
VRF IPv4 address family configuration
VRF IPv6 address family configuration
VPNv4 address family configuration
VPNv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable installing a backup path into the forwarding table in VPNv4 address family mode:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)#additional-paths install backup
To configure receive capability of multiple paths for a prefix to the capable peers, use the additional-paths receive command in address-family configuration mode. To disable receive capability, use the no form of this command. To disable add-path receive capability for all neighbors belonging to a particular VRF address-family, use the disable option.
additional-paths receive [disable]
no additional-paths receive
disable |
|
This command has no keywords or arguments.
None
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the additional-paths receive command to allow add-path receive capability to be negotiated for a specified address family. When the additional-paths receive command is configured, the receive capability is automatically enabled for all internal BGP neighbors for a specified address family. When this command is either not configured or explicitly disabled, none of the neighbors are allowed to negotiate receive capability for the address family.
After enabling the receive capability, the session needs to be reset for the configuration to take into effect.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to enable additional paths receive capability under VPNv4 unicast address family:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:routerconfig)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# additional-paths receive
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config-bgp)#vrf vrf1 RP/0/RP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-vrf-af)#additional-paths receive disable
additional-paths selection { route-policy route-policy-name | disable }
no additional-paths selection route-policy route-policy-name
route-policy route-policy-name |
Specifies the name of a route policy used for additional paths selection. |
disable |
Disables add-path selection for a particular VRF address-family. |
None
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
To configure additional paths selection mode for some or all prefixes, use the additional-paths selection command by specifying a route-policy.
Use the additional-path selection command with an appropriate route-policy to calculate backup paths and to enable Prefix Independent Convergence (PIC) functionality. Refer BGP Prefix Independent Convergence Unipath Primary/Backup section in BGP Configuration Guide for Cisco NCS 5000 Series Routers for details on the PIC functionality.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to enable selection of additional paths:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# additional-paths selection route-policy ap1
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config-bgp)#vrf vrf1 RP/0/RP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-vrf-af)#additional-paths selection disable
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config-bgp)#vrf vrf2 RP/0/RP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-vrf-af)#additional-paths selection route-policy ap2
To configure send capability of multiple paths for a prefix to the capable peers, use the additional-paths send command in address-family configuration mode. To disable the send capability, use the no form of this command.
additional-paths send [disable]
no additional-paths send
disable |
|
None
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the additional-paths send command to allow add-path send capability to be negotiated for a specified address family. When the additional-paths send command is configured, the send capability is automatically enabled for all internal BGP neighbors for the specified address family. When the command is either not configured or explicitly disabled, none of the neighbors are allowed to negotiate send capability for the address family.
After enabling the send capability, the session needs to be reset for the configuration to take into effect.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to enable additional paths send capability under VPNv4 4 unicast address family:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:routerconfig)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# additional-paths send
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config-bgp)#vrf vrf1 RP/0/RP0/CPU0:router(config-bgp-vrf)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-vrf-af)#additional-paths send disable
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 } | ipv6 { unicast } }
no address-family
ipv4 unicast |
Specifies IP Version 4 (IPv4) unicast address prefixes. |
ipv6 unicast |
Specifies IP Version 6 (IPv6) unicast address prefixes. |
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.
Router configuration
Neighbor configuration
Neighbor group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 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.
Address Family |
Supported in Router Submode |
Supported in Neighbor Submode |
Comments |
---|---|---|---|
ipv4 unicast |
yes |
yes |
— |
ipv6 unicast |
yes |
yes |
— |
Task ID |
Operations |
---|---|
bgp |
read, write |
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# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)#
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-af)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)#
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 12 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 tunnel RP/0/RP0/CPU0:router(config-bgp-af)#
The following example shows how to place the router in global address family link-state configuration mode:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family link-state link-state RP/0/RP0/CPU0:router(config-bgp-af)#
The following example shows how to exchange link-state information with a BGP neighbor:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family link-state link-state RP/0/RP0/CPU0:router(config-bgp-nbr-af)#
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 flowspec RP/0/RP0/CPU0:router(config-bgp-af)#
To advertise the best–external path to the iBGP and route-reflector peers, when a locally selected bestpath is from an internal peer, use the advertise best-external command in an appropriate address family configuration mode. To prevent advertising the best–external path, use the no form of this command. To disable advertising the best–external path, use the disable keyword.
advertise best-external [disable]
no advertise best-external
disable |
Disables best–external configuration for the VRF. |
None
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable advertising the best–external path VPNv4 unicast address family mode:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# advertise best-external
To identify the peers to whom the permanent paths must be advertised, use the advertise permanent-network command in the neighbor address family configuration mode. To stop advertising the permanent p, use the no form of this command. The permanent paths will always be advertised to peers having advertise permanent-network configuration, even if a different best-path is available. The permanent path is not advertised to peers that are not configured to receive permanent path.
The permanent path supports only prefixes in IPv4 unicast and IPv6 unicast address-families under the default Virtual Routing and Forwarding (VRF).
advertise permanent-network
no advertise permanent-network
This command has no arguments or keywords.
Neighbor address-family configuration.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
This example shows how to advertise permanent path:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 4713 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# advertise permanent-network
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]
seconds |
Minimum interval between sending BGP routing updates (in seconds). Range is 0 to 600. |
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 seconds
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 5 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100 RP/0/RP0/CPU0:router(config-bgp-nbr)# advertisement-interval 10
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 XR Config mode. To remove an address family group, use the no form of this command.
af-group af-group-name address-family
no af-group
af-group-name |
Address family group name. |
address-family |
Enters address family configuration mode. |
ipv4 unicast |
Specifies IP Version 4 (IPv4) unicast address prefixes. |
ipv6 unicast |
Specifies IP Version 6 (IPv6) unicast address prefixes. |
No BGP address family group is configured.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 100 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-self
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 |
Aggregate address. |
/mask-length |
Aggregate address mask length. |
as-set |
(Optional) Generates autonomous system set path information and community information from contributing paths. |
as-confed-set |
(Optional) Generates autonomous system confederation set path information from contributing paths. |
summary-only |
(Optional) Filters all more-specific routes from updates. |
route-policy route-policy-name |
(Optional) Specifies the name of a route policy used to set the attributes of the aggregate route. |
When you do not specify this command, no aggregate entry is created in the BGP routing table.
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# aggregate-address 10.0.0.0/8 as-set
To enable sending and receiving of accumulated interior gateway protocol (AiGP) attribute per eBGP neighbor, use the aigpcommand in appropriate configuration mode. To disable this functionality, either use the disable keyword or use the no form of this command.
aigp [ disable ]
no aigp
disable |
Disables sending or receiving AiGP attribute. |
Send or recive of AiGP attribute is disabled for eBGP neighbors
IPv4 address family configuration
IPv6 address family configuration
Neighbor address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
The following example shows how to enable AiGP send and receive capability under neighbor address family (IPv4 unicast):
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# aigp
To send Accumulated Interior Gateway Protocol (AiGP) value in cost community, use the aigp send-cost-community command in appropriate configuration mode. To disable sending AiGP value in cost community, either use the no form of this command or the disable keyword.
aigp send-cost-community { cost-id | disable } poi { igp-cost | pre-bestpath } [ transitive ]
no aigp send-cost-community
cost-comm-id |
Specifies the Cost community ID. The range is 0 to 255. |
poi | Point of insertion for bestpath calculation. |
igp-cost | Configures that cost community be used after iGP distance to next hop. |
pre-bestpath | Configures cost community as first step in best path calculation. |
transitive |
(Optional) Enables transitive cost community |
disable |
Disables sending AiGP value in cost community. |
Sending AiGP value in cost community is disabled
Neighbor address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Cost community point of insertion can be configured either to be pre-bestpath or after igp cost. The transitive keyword is not required for iBGP sessions. However, the transitive keyword is required for eBGP sessions to convert AiGP metric into cost-community and advertise to the eBGP neighbors.
Task ID | Operation |
---|---|
bgp |
read, write |
The following example shows how to enable sending AiGP value in cost community ID 254 under neighbor address family (IPv4 unicast):
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# aigp send-cost-community 254
To allocate Multiprotocol Label Switching (MPLS) labels for specific IPv4 unicast or IPv6 unicast or VPN routing and forwarding (VRF) IPv4 unicast routes so that the BGP router can send labels with BGP routes to a neighboring router configured for labeled- or VPN routing and forwarding (VRF) IPv6 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.
![]() Note | This feature is not supported. |
allocate-label { route-policy route-policy-name | all }
no allocate-label { route-policy route-policy-name | all }
all |
Allocates labels for all prefixes |
route-policy route-policy-name |
Uses a route policy to select prefixes for label allocation. |
No default behavior or values
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the allocate-label command with a route policy to trigger BGP to allocate labels for all or a filtered set of global IPv4 routes (as dictated by the route policy). The command enables autonomous system border routers (ASBRs) that have labeled IPv4 unicast sessions to exchange Multiprotocol Label Switching (MPLS) labels with the IPv4 routes to the other autonomous system (AS) in Layer 3 Virtual Private Network (L3VPN) inter-AS deployments.
![]() Note | The allocate-label all command is functionally equivalent to the allocate-label route-policy route-policy-name command when the route policy is a pass-all policy. |
See MPLS Configuration Guide for Cisco NCS 5000 Series Routers for information on using the allocate-label command for L3VPN inter-AS deployments and carrier-supporting-carrier IPv4 BGP label distribution.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable allocating labels for IPv4 routes:
RP/0/RP0/CPU0:router(config)# router bgp 6 RP/0/RP0/CPU0:router(config-bgp)# address family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# allocate-label route-policy policy_A
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]
as-occurrence-number |
(Optional) Number of times a PE ASN is allowed. Range is 1 to 10. |
No default behavior or values
Address family group configuration
Neighbor address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Hub and spoke VPN networks require looping back of routing information to the hub PE through the hub customer edge (CE). See MPLS Configuration Guide for Cisco NCS 5000 Series Routers for information on hub and spoke VPN networks. This looping back, in addition to the presence of the PE ASN, causes the looped-back information to be dropped by the hub PE.
The allowas-in command prevents the looped-back information from being dropped by replacing the neighbor autonomous system number (ASN) with the PE ASN in the AS path. This allows the VPN customer to see a specified number of occurrences of the PE ASN in the AS path.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to allow five occurrences of the PE ASN:
RP/0/RP0/CPU0:router(config)# router bgp 6 RP/0/RP0/CPU0:router(config-bgp)# af-group group_1 address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# allowas-in 5
To configure the router's Autonomous system number (ASN) notation to asdot format, use the as-format command in XR Config mode. To restore the system to its default condition, use the no form of this command.
as-format asdot
no
asdot |
Specifies the Autonomous system number (ASN) notation to asdot format. |
The default value, if the as-format command is not configured, is asplain.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure the ASN notation to the asdot format:
RP/0/RP0/CPU0:router(config)# as-format asdot
To configure a provider edge (PE) router to override the autonomous system number (ASN) of a site with the ASN of a provider, use the as-override command which works for both VRF and non-VRF neighbor address family configuration mode. To restore the system to its default condition, use the no form of this command.
as-override [inheritance-disable]
no as-override [inheritance-disable]
inheritance-disable |
(Optional) Prevents the as-override command from being inherited from a parent group. |
Automatic override of the ASN is disabled.
VRF and non-VRF neighbor address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure an ASN override:
RP/0/RP0/CPU0:router(config)# router bgp 6 RP/0/RP0/CPU0:router(config-bgp)# vrf vrf_A RP/0/RP0/CPU0:router(config-bgp-vrf)# neighbor 192.168.70.24 RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# remote-as 10 RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-vrf-nbr-af)# as-override
To disable AS PATH loop checking for outbound updates, use the as-path-loopcheck out disable command in an appropriate address family configuration mode. To re-enable the default AS PATH loop checking, use the no form of this command.
as-path-loopcheck out disable
no as-path-loopcheck out disable
This command has no keywords or arguments.
AS PATH loop checking for outbound updates is enabled if there is only one neighbor and disabled if there are multiple neighbors in the update group.
IPv4 address family
IPv6 address family
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Configure the as-path-loopcheck out disable command to disable the default behavior of PE router not announcing BGP routes to the CE router if the routes contain an AS number matching the AS number of the receiving CE router.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to configure as-path-loopcheck out disable under IPv6 unicast address family:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#address-family ipv6 unicast RP/0/RP0/CPU0:router(config-bgp-af)#as-path-loopcheck out disable
To configure attribute-filter group command mode, use the attribute-filter group command in an appropriate configuration mode. To disable attribute-filter group command mode, use the no form of this command.
attribute-filter group group-name
no attribute-filter group group-name
group-name |
Specifies the name of the attribute-filter group. |
Attribute-filter group command mode is disabled.
Router configuration
Neighbor configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the attribute-filter group command in neighbor configuration mode to configure a specific attribute filter group for a BGP neighbor.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to configure the attribute-filter group command mode:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#attribute-filter group ag_discard_med RP/0/RP0/CPU0:router(config-bgp-attrfg)#
This example shows how to configure the attribute filter group for a BGP neighbor:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.0.1.101 RP/0/RP0/CPU0:router(config-bgp-nbr)#remote-as 6461 RP/0/RP0/CPU0:router(config-bgp-nbr)#update in filtering RP/0/RP0/CPU0:router(config-nbr-upd-filter)#attribute-filter group ag_discard_med
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
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. |
No default per neighbor parameters are set.
Neighbor address family independent configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
If the minimum interval is changed using the bfd minimum-intervalcommand, the new parameter updates all affected BFD sessions under the command mode in which the minimum interval was changed.
If the multiplier is changed using the bfd multiplier command, the new parameter is used to update only the BFD sessions associated with the affected neighbor gets affected.
The assumption is that when BFD fast-detect is enabled under neighbor address family independent configuration, the values for the multiplier and minimum-interval values are always derived from the per-neighbor values if they are configured; otherwise, they are to be taken from the global BGP configuration mode. In the event that this has not been explicitly stated, then these values are taken to be the default values. Also, the bfd arguments can be configured under neighbor-group and session-group and the inheritance adheres to the standard way of BGP configuration inheritance.
Accordingly, there are four cases in which bfd-fast detect is enabled.
This is shown in table below where the BFD value is either multiplier or minimum-interval. Local indicates per NBR value, global is the BGP global value.
BFD value (global) |
BFD value (local) |
Result |
---|---|---|
Yes |
Yes |
BFD value (local) |
Yes |
No |
BFD value (global) |
No |
Yes |
BFD value (local) |
No |
No |
BFD value (default) |
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
This command has no keywords or arguments.
When you do not specify this command, loop checking is performed only for external peers.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure an autonomous system path for loop checking iBGP peers:
RP/0/RP0/CPU0:router(config)# router bgp 6 RP/0/RP0/CPU0:router(config-bgp)# bgp as-path-loopcheck
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
This command has no keywords or arguments.
BGP attribute download is not enabled.
IPv4 unicast address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 bgp B 100.0.1.0/24 [200/0] via 10.0.101.1, 00:00:37 B 100.0.2.0/24 [200/0] via 10.0.101.1, 00:00:37 B 100.0.3.0/24 [200/0] via 10.0.101.1, 00:00:37 B 100.0.4.0/24 [200/0] via 10.0.101.1, 00:00:37 B 100.0.5.0/24 [200/0] via 10.0.101.1, 00:00:37 RP/0/RP0/CPU0:router(config)# router bgp 50 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# bgp attribute-download ! ! ! RP/0/RP0/CPU0:router# show route bgp B 100.0.1.0/24 [200/0] via 10.0.101.1, 00:00:01 Attribute ID 0x2 B 100.0.2.0/24 [200/0] via 10.0.101.1, 00:00:01 Attribute ID 0x2 B 100.0.3.0/24 [200/0] via 10.0.101.1, 00:00:01 Attribute ID 0x2 B 100.0.4.0/24 [200/0] via 10.0.101.1, 00:00:01 Attribute ID 0x2 B 100.0.5.0/24 [200/0] via 10.0.101.1, 00:00:01 Attribute ID 0x2
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
This command has no keywords or arguments.
Automatic soft reset of peers is enabled.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
If the inbound policy changes, it is not always possible to perform a soft reset. This is the case if the neighbor does not support route refresh and soft-reconfiguration inbound is not configured for the neighbor. In such instances, a message is logged in the system log indicating that a manual hard reset is needed.
Task ID |
Operations |
---|---|
bgp |
read, write |
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 6 RP/0/RP0/CPU0:router(config-bgp)# bgp auto-policy-soft-reset disable
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
This command has no keywords or arguments.
The autonomous system path length is used (not ignored) when a best path is selected.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 65000 RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath as-path ignore
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
This command has no keywords or arguments.
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.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 500 RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath compare-routerid
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
This command has no keywords or arguments.
The behavior of this command is enabled by default until the cost community attribute is manually configured.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 500 RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath cost-community ignore
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
This command has no keywords or arguments.
The software does not compare MEDs for paths from neighbors in different autonomous systems.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 100 RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath med always
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
This command has no keywords or arguments.
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.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 210 RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath med confed
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
This command has no keywords or arguments.
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.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
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 210 RP/0/RP0/CPU0:router(config-bgp)# bgp bestpath med missing-as-worst
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 [cluster-id cluster-id] disable
no bgp client-to-client reflection [cluster-id cluster-id] disable
cluster-id cluster-id |
(Optional) Cluster ID for which intra-cluster route reflection is to be disabled; maximum of 4 bytes. Cluster ID can be entered either as an IP address or value. Range is 1 to 4294967295. |
This command has no keywords or arguments.
Client-to-client reflection is enabled.
Address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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.
By default, the clients of a route reflector that are part of the same cluster 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. If the cluster-id is not specified, then this command disables intra-cluster route reflection for all clusters.
In this example, the three neighbors are fully meshed, so client-to-client reflection is disabled:
RP/0/RP0/CPU0:router(config)# router bgp 65534 RP/0/RP0/CPU0:router(config-bgp)# bgp cluster-id 2 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# bgp client-to-client reflection cluster-id 2 disable RP/0/RP0/CPU0:router(config-bgp-af)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor-group rrclients RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# remote-as 65534 RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# bgp cluster-id 2 RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-reflector-client RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exit RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.21 use neighbor-group rrclients RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.22 use neighbor-group rrclients RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.23 use neighbor-group rrclients
In this example, the three neighbors are fully meshed, so client-to-client reflection is disabled:
RP/0/RP0/CPU0:router(config)# router bgp 65534 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# bgp client-to-client reflection disable RP/0/RP0/CPU0:router(config-bgp-af)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor-group rrclients RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# remote-as 65534 RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# route-reflector-client RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exit RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.21 use neighbor-group rrclients RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.253.22 use neighbor-group rrclients
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]
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. |
A cluster ID is not configured.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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.
A single route reflector can also support multiple clusters. Each cluster is identified by a unique cluster-id. The cluster-id configured by the bgp cluster-id command is taken as the default. If bgp cluster-id is not configured, the router ID for the default VRF identifies the default cluster. A neighbor can be associated with one cluster only, and the corresponding cluster-id is configured in neighbor configuration mode. If the cluster-id is not configured for a neighbor and the neighbor is a route reflector client, then the neighbor is assigned to the default cluster.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure the local router as one of the route reflectors serving the cluster. Neighbor 192.168.70.24 is assigned to the default cluster with cluster-id 1.
RP/0/RP0/CPU0:router(config)# router bgp 65534 RP/0/RP0/CPU0:router(config-bgp)# bgp cluster-id 1 RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.70.24 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65534 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-reflector-client
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]
as-number |
Autonomous system (AS) number that internally includes multiple autonomous systems. |
No confederation identifier is configured.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 4001 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation identifier 5 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4002 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4003 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4004 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4005 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4006 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 4007 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 4002 RP/0/RP0/CPU0:router(config-bgp-nbr)# exit RP/0/RP0/CPU0:router(config-bgp)# exit RP/0/RP0/CPU0:router(config-bgp-nbr)# neighbor 172.20.16.6 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 4009
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]
as-number |
Autonomous system (AS) numbers for Border Gateway Protocol (BGP) peers that belong to the confederation. |
No BGP peers are identified as belonging to the confederation.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 1090 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers 1093
The following example shows that autonomous systems 1095, 1096, 1097, and 1098 belong to a single confederation:
RP/0/RP0/CPU0:router(config)# router bgp 1095 RP/0/RP0/CPU0:router(config-bgp)# bgp confederation peers RP/0/RP0/CPU0:router(config-bgp-confed-peers)# 1096 RP/0/RP0/CPU0:router(config-bgp-confed-peers)# 1097 RP/0/RP0/CPU0:router(config-bgp-confed-peers)# 1098
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 ]
half-life |
(Optional) Time (in minutes) after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period (which is 15 minutes by default). Penalty reduction happens every 5 seconds. Range of the half-life period is from 1 to 45 minutes. |
reuse |
(Optional) Value for route reuse if the flapping route penalty decreases and falls below the reuse value. When this happens, the route is unsuppressed. The process of unsuppressing routes occurs at 10-second increments. Range is 1 to 20000. |
suppress |
(Optional) Maximum penalty value. Suppress a route when its penalty exceeds the value specified. When this happens, the route is suppressed. Range is 1 to 20000. |
max-suppress-time |
(Optional) Maximum time (in minutes) a route can be suppressed. Range is 1 to 255. If the half-life value is allowed to default, the maximum suppress time defaults to 60 minutes. |
route-policy route-policy-name |
(Optional) Specifies the route policy to use to set dampening parameters. |
Route dampening is disabled.
half-life : 15 minutes
reuse : 750
suppress : 2000
max-suppress-time : four times half-life value
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 50 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# bgp dampening 30 1500 10000 120
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]
value |
Local preference value. Range is 0 to 4294967295. Higher values are preferable. |
Enabled with a value of 100.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 200 RP/0/RP0/CPU0:router(config-bgp)# bgp default local-preference 200
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
This command has no keywords or arguments.
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.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 100 RP/0/RP0/CPU0:router(config-bgp)# bgp enforce-first-as 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
disable |
Disables BGP fast external failover. |
BGP sessions of any directly adjacent external peers are immediately reset if the link used to reach them goes down.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to disable the automatic resetting of BGP sessions:
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# bgp fast-external-fallover disable
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
This command has no keywords or arguments.
Graceful restart support is not enabled.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the bgp graceful-restart command to enable graceful restart functionality on the router, and also to advertise graceful restart to neighboring routers.
![]() Note | The bgp graceful-restart command with no options must be used to enable graceful restart before using the bgp graceful-restart purge-time , bgp graceful-restart restart-time , bgp graceful-restart stalepath-time , or bgp graceful-restart graceful-reset commands. |
When graceful restart is enabled, the BGP graceful restart capability is negotiated with neighbors in the BGP OPEN message when the session is established. If the neighbor also advertises support for graceful restart, then graceful restart is activated for that neighbor session. If the neighbor does not advertise support for graceful restart, then graceful restart is not activated for that neighbor session even though it is enabled locally.
If you enter the bgp graceful-restart command after some BGP sessions are established, you must restart those sessions before graceful restart takes effect. Use the clear bgp command to restart sessions.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable graceful restart:
RP/0/RP0/CPU0:router(config)#router bgp 3 RP/0/RP0/CPU0:router(config-bgp)#bgp graceful-restart
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
This command has no keywords or arguments.
Graceful restart is not invoked when a configuration change forces a peer reset.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable graceful reset:
RP/0/RP0/CPU0:router(config)#router bgp 3 RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart graceful-reset
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
seconds |
Maximum time before stale routes are purged. Time in seconds. Range is 0 to 6000. |
seconds : 600
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to change the BGP purge time to 800 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 3 RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart purge-time 800
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
seconds |
Maximum time advertised to neighbors. Time in seconds. Range is 1 to 4095. |
seconds : 120
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to change the BGP graceful restart time to 400 seconds:
RP/0/RP0/CPU0:router(config)#router bgp 3 RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart restart-time 400
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
seconds |
Maximum wait time. Time in seconds. Range is 1 to 4095. |
seconds : 360
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to change the stalepath time to 750 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 3 RP/0/RP0/CPU0:router(config-bgp)# bgp graceful-restart stalepath-time 750
To enable delay for Border Gateway Protocol (BGP) batch import processing, use the bgp import-delay command in an appropriate configuration mode. To disable delay in batch import processing, use the no form of this command.
bgp import-delay seconds milliseconds
no bgp import-delay
seconds |
Specifies batch import processing delay in seconds. Range is 0 to 10 seconds. |
milliseconds |
Specifies batch import processing delay in milliseconds. Range is 0 to 999 seconds. |
No delay is configured.
Address-family VPNv4 Unicast
Address-family VPNv6 Unicast
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set delay in batch import processing as two seconds and zero milliseconds:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)#bgp import-delay 2 0
To enable delay for Border Gateway Protocol (BGP) batch label processing, use the bgp label-delay command in an appropriate configuration mode. To disable delay in batch import processing, use the no form of this command.
bgp label-delay seconds milliseconds
no bgp label-delay
seconds |
Specifies batch label processing delay in seconds. Range is 0 to 10 seconds. |
milliseconds |
Specifies batch label processing delay in milliseconds. Range is 0 to 999 seconds. |
No delay is configured.
Address-family IPv4 Unicast
Address-family IPv6 Unicast
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set delay in batch import processing as two seconds and zero milliseconds:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)#bgp label-delay 2 0
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
This command has no keywords or arguments.
BGP neighbor changes are logged.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Logging of BGP neighbor status changes (up or down) and resets is used for troubleshooting network connectivity problems and measuring network stability. Unexpected neighbor resets might indicate high error rates or high packet loss in the network, and should be investigated.
Status change message logging does not substantially affect performance, unlike, for example, enabling per-BGP update debugging. If the UNIX syslog facility is enabled, messages are sent by the software to the UNIX host running the syslog daemon so that the messages can be stored and archived on disk. If the UNIX syslog facility is not enabled, the status change messages are kept in the internal buffer of the router, and are not stored to disk.
The neighbor status change messages are not tracked if the bgp log neighbor changes disable command is disabled, except for the last reset reason, which is always available as output of the show bgp neighbors command.
Up and down messages for BGP neighbors are logged by the software by default. Use the bgp log neighbor changes disable command to stop logging BGP neighbor changes.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to prevent the logging of neighbor changes for BGP:
RP/0/RP0/CPU0:router(config)# router bgp 65530 RP/0/RP0/CPU0:router(config-bgp)# bgp log neighbor changes disable
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]
limit |
Maximum number of neighbors. Range is 1 to 15000. |
Default limit is 4000
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Any attempt to configure the neighbor limit below 1 or above 15000 fails. Similarly, attempting to configure the limit below the number of neighbors currently configured fails. For example, if there are 3250 neighbors configured, you cannot set the limit below 3250.
Task ID |
Operations |
---|---|
bgp |
write |
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 65530 RP/0/RP0/CPU0:router(config-bgp)# bgp maximum neighbor 1200
To ignore as-path onwards while computing multipath, use the bgp multipath as-path command in XR Config mode.
bgp multipath as-path ignore onwards
ignore |
Ignores as-path related check for multipath selection. |
onwards |
Ignores everything as-path onwards for multipath selection. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
This example shows how to ignore as-path while computing multipath.
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# bgp multipath as-path ignore onwards
To match packets based on an incoming source, destination IP address or action (such as redirect, drop, PBTS) and redirect it to a specific VRF, use the bgp policy propagation input flow-tag command in the interface configuration mode.
bgp policy propagation input flow-tag { destination | source}
bgp policy propagation input flow-tag |
Enables flow-tag policy propagation on the specified interfaces. |
destination |
The packets are matched based on an incoming destination IP address and redirected to a specific VRF. |
source |
The packets are matched based on an incoming source IP address and redirect it to a specific VRF. |
None
Router configuration
Interface configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use this command to apply the flow-tag to a specified interface. The packets are matched based on an incoming source, destination IP address or action (such as redirect, drop, PBTS) and redirected to a specific VRF.
![]() Note | You will not be able to enable both QPPB and flow tag feature simultaneously on an interface. |
Task ID | Operation |
---|---|
bgp |
read, write |
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
This command has no keywords or arguments.
By default, iBGP routes are not redistributed into IGPs.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use of the bgp redistribute-internal command requires the clear route * command to be issued to reinstall all BGP routes into the IP routing table.
![]() Note | Redistributing iBGP routes into IGPs may cause routing loops to form within an autonomous system. Use this command with caution. |
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)#router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# bgp redistribute-internal RP/0/RP0/CPU0:router(config-bgp)# exit RP/0/RP0/CPU0:router(config)# router ospf area1 RP/0/RP0/CPU0:router(config-router)# redistribute bgp 1 RP/0/RP0/CPU0:router(config-router)# end RP/0/RP0/CPU0:router# clear route *
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 ]
ip-address |
IP Version 4 (IPv4) address to use as the router ID. Normally, this should be an IPv4 address assigned to the router. |
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.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
If you do not use the bgp router-id command to configure a router ID, an IP address is not configured on any loopback interface, and no global router ID is configured, BGP neighbors remain down.
For more details on router IDs, see the BGP Configuration Guide for Cisco NCS 5000 Series Routers
Task ID |
Operations |
---|---|
bgp |
read, write |
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 100 RP/0/RP0/CPU0:router(config-bgp)#bgp router-id 192.168.70.24
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
seconds |
Scanning interval (in seconds) of BGP routing information. Range is 5 to 3600 seconds. |
The default scanning interval is 60 seconds.
Router configuration
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to set the scanning interval for IPv4 unicast to 20 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 64500 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# bgp scan-time 20
This example shows how to set the scanning interval to 20 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 64500 RP/0/RP0/CPU0:router(config-bgp-af)# bgp scan-time 20
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]
nobgp update-delay [ seconds ] [ always ]
seconds |
Delay in seconds for the router to send the first updates. Range is 0 to 3600. |
always |
(Optional) Specifies that the router always wait for the update delay time, even if all neighbors have finished sending their initial updates sooner. |
120 seconds
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to set the maximum initial delay to 240 seconds:
RP/0/RP0/CPU0:router(config)#router bgp 64530 RP/0/RP0/CPU0:router(config-bgp)# bgp update-delay 240
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]
group-limit |
Per-update group limit on the number of update messages the software queues. Range is 500 to 100000000. Group limit cannot be greater than the global limit. |
global-limit |
Global limit on the number of update messages the software queues. Range is 500 to 100000000. |
desynchronize |
(Optional) Enables desynchronization. |
group-limit : 50,000
global-limit : 250,000
Desynchronizationis off.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 65000 RP/0/RP0/CPU0:router(config-bgp)#bgp write-limit 9000 27000
To enable Border Gateway Protocol (BGP) Monitoring Protocol (BMP) logging for a neighbor, use the bmp-activate server command in neighbor configuration mode. To disable BMP logging for a neighbor, use the no form of this command.
bmp-activate server server-id
server server-id |
Enables monitoring by the BMP server specified by the server-id variable. You can configure multiple bmp-activate commands under same neighbor with different server IDs to enable monitoring by multiple BMP servers. |
No default behavior or values
Neighbor configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read |
The following example shows how to activate BMP on a neighbor with IP address 1.1.1.1, which is monitored by BMP server with server ID as 4:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 1.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# bmp-activate server 4
To configure Border Gateway Protocol (BGP) Monitoring Protocol (BMP) server and to enter BMP server configuration mode, use the bmp server command in XR Config mode. To remove a particular BMP server configuration, use no form of this command.
bmp server { server-id | | all }
server-id |
Specifies BMP server ID. Server ID range is 1 to 8. |
||
all |
Specifies all BMP servers. |
||
description LINE |
Specifies BMP server description. Description can be up to 250 alphanumeric characters. |
||
dscp |
Sets IP DiffServ CodePoint (DSCP). The DSCP value can be a number from 0 to 63, or it can be one of the following keywords: default , ef , af11 , af12 , af13 , af21 , af22 , af23 , af31 , af32 , af33 , af41 , af42 , af43 , cs1 , cs2 , cs3 , cs4 , cs5 , cs6 , or cs7 . |
||
host host-name |
Specifies the hostname of BMP server. The hostname of the BMP server can be specified in IP address format (standard dot-decimal notation for IPv4 or colon-hexadecimal notation for IPv6) format or the string name which can be resolved into an IP address by the router. |
||
initial-delay delay-time |
Sets the delay, in seconds, before initial connect request is sent to a BMP server. The delay that you can set ranges from 1 to 3600 seconds. The default is 7 seconds. |
||
initial-refresh {delay | skip} |
Delay to initiate route refresh requests to BMP enabled neighbors. Configures the initial refresh options to handle refresh requests sent by the router to its BMP-enabled neighbors. Sets the delay, in seconds, before an initial refresh request is sent by the router to its BMP-enabled neighbors. The delay range is 1 to 3600 seconds with a default of 1 second. The default is not to skip refresh requests. Configures the router to skip sending any refresh requests to its BMP-enabled neighbors. |
||
precedence |
Sets the precedence values in the IP header. The precedence value can be a number from 0 to 7, or it can be one of the following keywords: critical —Set packets with critical precedence (5) flash — Set packets with flash precedence (3) flash-override —Set packets with flash override precedence (4) immediate —Set packets with immediate precedence (2) internet —Set packets with internetwork control precedence (6) network —Set packets with network control precedence (7) priority —Set packets with priority precedence (1) routine —Set packets with routine precedence (0) The default is internet (6) . |
||
shutdown |
Shuts down the TCP connection to BMP server. |
||
stats-reporting-period |
Specifies statistics reporting period, in seconds, to BMP servers. The reporting period that you can set ranges from 1 to 3600 seconds. The default is 0. |
||
update-source type interface-path-id |
Specifies the source (physical or virtual interface) to reach the BMP server.
For more information about the syntax for the router, use the question mark ( ? ) online help function. |
||
vrf vrf-name |
Specifies VPN routing and forwarding (VRF) instance. |
For default values refer Syntax Description table.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read |
This example shows how to configure initial refresh delay of 30 seconds for BGP neighbors on BMP server with server ID as 4:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# bmp server 4 initial-refresh delay 30
This example shows how to configure hostname of BMP server as 192.168.10.1:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# bmp server 8 host 192.168.10.1 port 56
This example shows how to configure tenGigE at location 0/0/0/1 as source interface to reach BMP server:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# bmp server 5 update-source tenGigE 0/0/0/1
To advertise capability of receiving additional paths to the peer, use the capability additional-paths receive command in neighbor or neighbor-group or session-group configuration mode. To disable the capability of receiving additional paths, use the no form of this command.
capability additional-paths receive [disable]
no capability additional-paths receive
disable |
Disables advertising capability of receiving additional paths. |
Capability is disabled.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the capability additional-paths receive command to selectively enable or disable additional paths receive capability negotiation for a particular neighbor or neighbor-group or session-group. Configuring additional-paths receive command in global address-family mode is a pre-requisite for negotiating additional paths receive capability with the peer.
If you enter the capability additional-paths receive command after some BGP sessions are established, you must restart those sessions for the new configuration to take effect. Use the clear bgp command to restart sessions.
Task ID | Operation |
---|---|
bgp |
read, write |
The following example shows how to advertise capability of receiving additional paths:
RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)#capability additional-paths receive
To advertise capability of sending additional paths to the peer, use the capability additional-paths send command in neighbor or neighbor-group or session-group configuration mode. To disable the capability of sending additional paths, use the no form of this command.
capability additional paths send [ disable ]
no capability additional paths send
disable |
Disables advertise additional paths send capability |
Capability is disabled.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the capability additional paths send command to selectively enable or disable additional paths send capability negotiation for a particular neighbor or neighbor-group or session-group. Configuring the additional-paths send command in global address-family mode is a pre-requisite for negotiating additional paths send capability with the peer.
You must restart the BGP sessions for the new configuration to take effect. Use the clear bgp command to restart sessions.
Task ID | Operation |
---|---|
bgp |
read, write |
The following example shows how to advertise capability of sending additional paths to the peer:
RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)# capability additional-paths send
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 ]
receive |
Sets the capability to receive the ORF from a specified neighbor. |
send |
Sets the capability to send the ORF to a specified neighbor. |
both |
Sets the capability to receive and send the ORF from or to a specified neighbor. |
none |
Sets the capability to no for ORF receive or send from or to a specified neighbor. |
The routing device does not receive or send route prefix filter lists.
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
The advertisement of the prefix list ORF capability by a BGP speaker indicates whether the speaker can send prefix lists to the specified neighbor and whether it accepts prefix lists from the neighbor. The speaker sends a prefix list if it indicated the ability to send them, and if the neighbor indicated it was willing to accept them. Similarly, the neighbor sends a prefix list to the speaker if it indicated the ability to send them and the speaker indicated the willingness to accept them.
![]() Note | The capability orf and prefix list filter specified by orf route-policy must be explicitly configured. |
If the neighbor sends a prefix list and the speaker accepts it, the speaker applies the received prefix list, plus any locally configured outbound filters, to limit its outbound routing updates to the neighbor. Increased filtering prevents unwanted routing updates between neighbors and reduces resource requirements for routing update generation and processing.
Use the capability orf prefix command to set whether to advertise send and receive capabilities to the specified neighbor.
![]() Note | Sending a receive capability can adversely affect performance, because updates sent to that neighbor cannot be replicated for any other neighbors. |
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure the capability orf prefix command:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# route-policy orfqq RP/0/RP0/CPU0:router:(config-rpl)# if orf prefix in (10.0.0.0/8 ge 20) then RP/0/RP0/CPU0:router(config-rpl)# pass RP/0/RP0/CPU0:router(config-rpl)# endif RP/0/RP0/CPU0:router(config-rpl)# if orf prefix in (1910::16 ge 120) then RP/0/RP0/CPU0:router(config-rpl)# pass RP/0/RP0/CPU0:router(config-rpl)# endif RP/0/RP0/CPU0:router(config-rpl)# end-policy RP/0/RP0/CPU0:router(config)# router bgp 65530 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.101.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65534 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-policy pass-all out RP/0/RP0/CPU0:router(config-bgp-nbr-af)# capability orf prefix both RP/0/RP0/CPU0:router(config-bgp-nbr-af)# orf route-policy orfqq
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, use the no form of this command.
capability suppress 4-byte-as [ inheritance-disable ]
no capability suppress 4-byte-as
inheritance-disable |
Prevents capability suppress 4-type-as being inherited from the parent. |
4-byte-as capability is advertised to the BGP peer.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
By default, the software advertises the 4-byte AS capability to BGP peers. To override this default behavior, use the capability suppress 4-byte-as command under the command modes listed in the ''Command Modes'' section. If configured under the neighbor group or session group, all neighbors using the group inherit the configuration. Use the no option to remove the command.
![]() Caution | The BGP session resets automatically, if the 4-byte AS capability of an existing BGP session is changed by configuring capability suppress 4-byte-as or capability suppress 4-byte-as inheritance-disable . |
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure the capability suppress 4-byte-as command:
RP/0/RP0/CPU0:router# show bgp nei 10.3.3.3 conf neighbor 10.3.3.3 remote-as 65000 [n:internal] description PE3 [] update-source Loopback0 [n:internal] address-family ipv4 unicast [n:internal] RP/0/RP0/CPU0:router#show bgp nei 10.3.3.3 BGP neighbor is 10.3.3.3 Remote AS 65000, local AS 65000, internal link Description: PE3 Remote router ID 10.3.3.3 BGP state = Established, up for 1w0d Last read 00:00:17, hold time is 180, keepalive interval is 60 seconds Precedence: internet Neighbor capabilities: Route refresh: advertised and received 4-byte AS: advertised and received Address family IPv4 Unicast: advertised and received Received 25962 messages, 0 notifications, 0 in queue Sent 25968 messages, 1 notifications, 0 in queue Minimum time between advertisement runs is 0 seconds For Address Family: IPv4 Unicast BGP neighbor version 1 Update group: 0.3 Route refresh request: received 0, sent 0 0 accepted prefixes, 0 are bestpaths Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288 Threshold for warning message 75% An EoR was received during read-only mode Connections established 2; dropped 1 Last reset 1w0d, due to BGP Notification sent: hold time expired Time since last notification sent to neighbor: 1w0d Error Code: hold time expired Notification data sent: None RP/0/RP0/CPU0:router(config)#router bgp 65000 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.3.3.3 RP/0/RP0/CPU0:router(config-bgp-nbr)#capability suppress 4-byte-as RP/0/RP0/CPU0:router(config-bgp-nbr)#commit RP/0/RP0/CPU0:router(config-bgp-nbr)#end RP/0/RP0/CPU0:router# show bgp nei 10.3.3.3 BGP neighbor is 10.3.3.3 Remote AS 65000, local AS 65000, internal link Description: PE3 Remote router ID 10.3.3.3 BGP state = Established, up for 00:00:16 Last read 00:00:11, hold time is 180, keepalive interval is 60 seconds Precedence: internet Neighbor capabilities: Route refresh: advertised and received Address family IPv4 Unicast: advertised and received Capability 4-byte-as suppress is configured Received 25966 messages, 0 notifications, 0 in queue Sent 25972 messages, 1 notifications, 0 in queue Minimum time between advertisement runs is 0 seconds For Address Family: IPv4 Unicast BGP neighbor version 1 Update group: 0.2 Route refresh request: received 0, sent 0 0 accepted prefixes, 0 are bestpaths Prefix advertised 0, suppressed 0, withdrawn 0, maximum limit 524288 Threshold for warning message 75% An EoR was received during read-only mode Connections established 3; dropped 2 Last reset 00:00:43, due to Capabilty 4-byte-as configuration changed Time since last notification sent to neighbor: 1w0d Error Code: hold time expired Notification data sent: None
With the inheritance-disable keyword:
RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.101.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# capability suppress 4-byte-as inheritance-disable RP/0/RP0/CPU0:router# show bgp neighbor 10.0.101.1 config neighbor 10.0.101.1 remote-as 1 [] address-family ipv4 unicast [] RP/0/RP0/CPU0:router# show bgp neighbor 10.0.101.1 BGP neighbor is 10.0.101.1 Remote AS 1, local AS 100, external link Remote router ID 0.0.0.0 BGP state = Idle Last read 00:00:00, hold time is 180, keepalive interval is 60 seconds Precedence: internet Received 0 messages, 0 notifications, 0 in queue Sent 0 messages, 0 notifications, 0 in queue Minimum time between advertisement runs is 30 seconds
To reset a group of Border Gateway Protocol (BGP) neighbors, use the clear bgp command in XR EXEC mode.
clear bgp [ ipv4 { unicast } | ipv6 { unicast | multicast } ]
ipv4 |
(Optional) Specifies IP Version 4 address prefixes. |
unicast |
(Optional) Specifies unicast address prefixes. |
mdt |
(Optional) Specifies IPv4 multicast distribution tree (MDT) address prefixes. |
ipv6 |
(Optional) Specifies IP Version 6 address prefixes. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router# clear bgp 10.0.0.1
To clear Border Gateway Protocol (BGP) route dampening information and unsuppress the suppressed routes, use the clear bgp dampening command in XR EXEC mode.
clear bgp dampening
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
ip-address |
(Optional) IP address of the network about which to clear dampening information. |
/mask-length |
(Optional) Network mask applied to the IP address. |
If no IP address is specified, dampening information for all routes is cleared.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
clear bgp ipv4 unicast dampening prefix x.x.x./y
Task ID |
Operations |
---|---|
bgp |
execute |
The following example shows how to clear the route dampening information for all 172.20.0.0/16 IPv4 unicast paths:
RP/0/RP0/CPU0:router# clear bgp ipv4 unicast dampening 172.20.0.0/16
To clear all Border Gateway Protocol (BGP) external peers, use the clear bgp external command in XR EXEC mode.
clear bgp external
ipv4 |
(Optional) Specifies IP Version 4 address prefixes. |
unicast |
(Optional) Specifies unicast address prefixes. |
ipv6 |
(Optional) Specifies IP Version 6 address prefixes. |
graceful |
(Optional) Clears all external peers with a hard reset and a graceful restart. This option is available when an address family is not specified. |
No default behavior or value
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router# clear bgp external
To clear Border Gateway Protocol (BGP) flap counts for a specified group of routes, use the clear bgp flap-statistics command in XR EXEC mode.
clear bgp flap-statistics
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
network |
(Optional) Network for which flap counts are to be cleared. |
/mask-length |
(Optional) Network mask of the network for which flap counts are to be cleared. |
ip-address |
(Optional) Neighbor address. Clears only flap statistics for routes received from this neighbor. |
No default behavior or value
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router#clear bgp all all flap-statistics regexp _1$
RP/0/RP0/CPU0:router# clear bgp ipv4 unicast flap-statistics 172.20.1.1
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 XR EXEC mode.
clear bgp nexthop performance-statistics
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
mdt |
Specifies IPv4 multicast distribution tree (MDT) address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
ipv4 { unicast | labeled-unicast } |
For VRF, specifies IPv4 unicast or labeled-unicast address families. |
ipv6 unicast |
For VRF, specifies IPv6 unicast address families. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router# clear bgp vrf vrf_A nexthop performance statistics
To reregister a specified next hop with the Routing Information Base (RIB), use the clear bgp nexthop registration command in XR EXEC mode.
clear bgp nexthop registration nexthop-address nexthop-address
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
ipv4 { unicast | labeled-unicast } |
For VRF, specifies IPv4 unicast or labeled-unicast address families. |
ipv6 unicast |
For VRF, specifies IPv6 unicast address families. |
nexthop-address |
Address of the next hop. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router# clear bgp nexthop registration 10.1.1.1
To clear the connection-dropped counter, use the clear bgp peer-drops command in XR EXEC mode.
clear bgp peer-drops { * | ip-address }
* |
Specifies all BGP neighbors. |
ip-address |
IP address of a specific network neighbor. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router# clear bgp peer-drops *
To clear the performance statistics for all address families, use the clear bgp performance-statistics command.
clear bgp performance-statistics
vrf |
Specifies VPN routing and forwarding (VRF). |
vrf-name |
Name of a VRF. |
all |
For VRF, specifies all VRFs. |
This command has no keywords or arguments.
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
execute |
RP/0/RP0/CPU0:router# clear bgp performance-statistics
To clear Border Gateway Protocol (BGP) routes that are self-originated, use the clear bgp self-originated command in XR EXEC mode.
clear bgp { ipv4 { unicast | } | | ipv6 { unicast | } } self-originated
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
all |
For VRF, specifies all VRFs. |
ipv4 { unicast | labeled-unicast } |
For VRF, specifies IPv4 unicast or labeled-unicast address families. |
ipv6 unicast |
For VRF, specifies IPv6 unicast address families. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Self-originated routes are routes locally originated by the network command, redistribute command, or aggregate-address command.
Task ID |
Operations |
---|---|
bgp |
execute |
The following example shows how to clear self-originated IPv4 routes:
RP/0/RP0/CPU0:router# clear bgp ipv4 unicast self-originated
To clear all Border Gateway Protocol (BGP) neighbors that shut down due to low memory, use the clear bgp shutdown command in XR EXEC mode.
clear bgp { ipv4 { unicast | } | ipv6 { unicast } }
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
ipv4 { unicast | labeled-unicast } |
For VRF, specifies IPv4 unicast or labeled-unicast address families. |
ipv6 unicast |
For VRF, specifies IPv6 unicast address families. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
execute |
The following example shows how to clear all shut-down BGP neighbors:
RP/0/RP0/CPU0:router# clear bgp shutdown
To soft reset a group of Border Gateway Protocol (BGP) neighbors, use the clear bgp soft command in XR EXEC mode.
clear bgp { ipv4 { unicast | } | ipv6 | | all { unicast } } soft
ipv4 |
Specifies IP Version 4 address prefixes. |
unicast |
Specifies unicast address prefixes. |
ipv6 |
Specifies IP Version 6 address prefixes. |
ipv4 { unicast | labeled-unicast } |
For VRF, specifies IPv4 unicast or labeled-unicast address families. |
ipv6 unicast |
For VRF, specifies IPv6 unicast address families. |
vpnv6 unicast |
Specifies VPNv6 unicast address families. |
No default behavior or value
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 | By default, if the configuration for an inbound or outbound route policy is changed, BGP performs an automatic soft reset. Use the bgp auto-policy-soft-reset disable command to disable this behavior. |
Task ID |
Operations |
---|---|
bgp |
execute |
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 in
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
This command has no arguments or keywords.
BGP does not permit redistribution of a default route into BGP.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure BGP to redistribute the default route into BGP:
RP/0/RP0/CPU0:router(config)#router bgp 164 RP/0/RP0/CPU0:router(config-bgp)# default-information originate
To disable the Martian check on the IPv4 and IPv6 prefixes, use the default-martian-check disable command in the address-family configuration mode. To enable the Martian check on the IPv4 and IPv6 prefixes, use the no form of this command.
default-martian-check disable
no default-martian-check disable
This command has no keywords or arguments.
None
IPv4 address family configuration mode.
IPv6 address family configuration mode.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
This example shows how to disable Martian check for an IPv4 address prefix.
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-af)# default-martian-check disable
This example shows how to disable Martian check for an IPv6 address prefix.
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv6 multicast RP/0/RP0/CPU0:router(config-bgp-af)# default-martian-check disable
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 ]
value |
Default metric value appropriate for the specified routing protocol. Range is 1 to 4294967295. |
A metric is not set.
Router configuration
VRF configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to set the BGP default metric:
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# default-metric 10
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 [ inheritance-disable | route-policy route-policy-name ]
no default-originate [ inheritance-disable | route-policy route-policy-name ]
inheritance-disable |
(Optional) Prevents the default-originate command characteristics from being inherited from a parent group. |
route-policy route-policy-name |
(Optional) Specifies the name of a route policy. The route policy allows route 0.0.0.0 to be injected conditionally. IPv6 address family is supported. |
The default route is not advertised to BGP neighbors.
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
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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.
In the L2VPN EVPN address-family group configuration mode, you can configure either default-originate or default-originate inheritance-disable commands.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.2.3 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 200 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# default-originate
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.2.3 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 200 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# default-originate route-policy default-default-policy
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 ]
text |
Meaningful description or comment. Maximum of 80 characters. |
No comment or description exists.
Neighbor group configuration
Neighbor configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure the description “Our best customer” on the neighbor 192.168.13.4:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)#router bgp 65000 RP/0/RP0/CPU0:router(config-bgp)#neighbor 192.168.13.4 RP/0/RP0/CPU0:router(config-bgp-nbr)#description Our best customer
To allow the use of external, internal, and local administrative distances that could be used to prefer one class of routes over another, use the distance bgp command in an appropriate configuration mode. To disable the use of administrative distances, use the nono form of this command.
distance bgp external-distance internal-distance local-distance
no distance bgp [ external-distance internal-distance local-distance ]
external-distance |
Administrative distance for Border Gateway Protocol (BGP) external routes. External routes are routes for which the best path is learned from a neighbor external to the autonomous system. Range is 1 to 255. Routes with a distance of 255 are not installed in the routing table. |
internal-distance |
Administrative distance for BGP internal routes. Internal routes are those routes that are learned from another BGP entity within the same autonomous system. Range is 1 to 255. Routes with a distance of 255 are not installed in the routing table. |
local-distance |
Administrative distance for BGP local routes. The local-distance argument applies to locally generated aggregate routes (such as the routes generated by the aggregate-address command) and backdoor routes installed in the routing table. Range is 1 to 255. Routes with a distance of 255 are not installed in the routing table. |
external-distance : 20
internal-distance : 200
local-distance : 200
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 | Changing the administrative distance of BGP internal routes is considered risky and is not recommended. One problem that can arise is the accumulation of routing table inconsistencies, which can interfere with routing. |
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 |
Operations |
---|---|
bgp |
read, write |
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 109 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)#distance bgp 20 20 200
To distribute ISIS link-state data using BGP LS, use the distribute bgp-ls command in XR Config mode. To stop link-state distribution, use the no form of this command.
distribute bgp-ls [instance-id value] [level { 1 | 2 } ] [throttle time]
no distribute bgp-ls
instance-id value |
(Optional) Specifies the instance identifier defined by the router isis command. Range is from 1 to 65535. If the instance-id is not configured, the system assigned instance-id for the ISIS process will be used. |
level 1 | 2 |
(Optional) Displays IS-IS link-state database for Level 1 or Level 2 independently. |
throttle |
(Optional) Specifies throttle update, in seconds. Range is from 5 to 20 seconds. |
None
Release |
Modification |
---|---|
Release 6.1.1 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
isis |
read, write |
This example shows how to distribute ISIS link-state information using BGP LS:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router isis foo RP/0/RP0/CPU0:router(config-isis)# distribute bgp-ls instance-id 32 level 2 throttle 5
To distribute OSPFv2 and OSPFv3 link-state data using BGP LS, use the distribute bgp-ls command in XR Config mode. To stop link-state distribution, use the no form of this command.
distribute bgp-ls [instance-id value] [throttle time]
no distribute bgp-ls
instance-id value |
(Optional) Specifies the instance identifier defined by the router ospf command. Range is from 1 to 65535. If the instance-id is not configured, the system assigned instance-id for the OSPF process is used. |
throttle |
(Optional) Specifies throttle time between successive link-state advertisement (LSA) updates. Range is from 0 to 3600. |
BGP distribution is disabled.
Release |
Modification |
---|---|
Release 6.1.1 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
ospf |
read, write |
This example shows how to distribute OSPF link-state information using BGP LS:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router ospf 100 RP/0/RP0/CPU0:router(config-ospf)# distribute bgp-ls instance-id 32 throttle 10
To configure globally unique identifier ASN for IGP domain, use the domain-distinguisher command in address-family link-state configuration mode. To remove unique identifier, use the no form of this command.
domain-distinguisher unique-id
no domain-distinguisher
unique-id |
Specifies four-octet unique identifier ASN. Range is from 1 to 4294967295. |
None
Address-family link-state configuration.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
This example shows how to configure a unique identifier ASN:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family link-state link-state RP/0/RP0/CPU0:router(config-bgp-af)# domain-distinguisher 1234
To originate a demilitarized zone (DMZ) link bandwidth extended community for the link to an eBGP neighbor, use the dmz-link-bandwidth command in an Neighbor configuration mode. To stop origination of the DMZ link bandwidth extended community, use the no form of this command.
dmz-link-bandwidth [ inheritance-disable ]
no dmz-link-bandwidth
inheritance-disable |
(Optional) Prevents the dmz-link-bandwidth command from being inherited from a parent group. |
BGP does not originate the DMZ link bandwidth extended community.
Neighbor configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the dmz-link-bandwidth command to advertise the bandwidth of links that are used to exit an autonomous system.
Task ID |
Operations |
---|---|
bgp |
read, write |
This example shows how to advertise the bandwidth of links to eBGP neighbors from router bgp 1:
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.67.89.01 RP/0/RP0/CPU0:router(config-bgp-nbr)#dmz-link-bandwidth
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 ]
value |
Value of the DSCP. The DSCP value can be a number from 0 to 63, or it can be one of the following keywords: default , ef , af11 , af12 , af13 , af21 , af22 , af23 , af31 , af32 , af33 , af41 , af42 , af43 , cs1 , cs2 , cs3 , cs4 , cs5 , cs6 , or cs7 . |
No default behavior or values
Neighbor configuration
Neighbor session group configuration
Neighbor group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the dscp command to change the minimum and maximum packet thresholds for the DSCP value.
Table 1 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.
DSCP (Precedence) |
Minimum Threshold |
Maximum Threshold |
Mark Probability |
---|---|---|---|
af11 |
32 |
40 |
1/10 |
af12 |
28 |
40 |
1/10 |
af13 |
24 |
40 |
1/10 |
af21 |
32 |
40 |
1/10 |
af22 |
28 |
40 |
1/10 |
af23 |
24 |
40 |
1/10 |
af31 |
32 |
40 |
1/10 |
af32 |
28 |
40 |
1/10 |
af33 |
24 |
40 |
1/10 |
af41 |
32 |
40 |
1/10 |
af42 |
28 |
40 |
1/10 |
af43 |
24 |
40 |
1/10 |
cs1 |
22 |
40 |
1/10 |
cs1 |
24 |
40 |
1/10 |
cs3 |
26 |
40 |
1/10 |
cs4 |
28 |
40 |
1/10 |
cs5 |
30 |
40 |
1/10 |
cs6 |
32 |
40 |
1/10 |
cs7 |
34 |
40 |
1/10 |
ef |
36 |
40 |
1/10 |
default |
20 |
40 |
1/10 |
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to set the DSCP value to af32:
RP/0/RP0/CPU0:router(config)# router bgp 5 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#remote-as 100 RP/0/RP0/CPU0:router(config-bgp-nbr)# dscp af32
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 ] [ mpls ]
no ebgp-multihop [ ttl-value ] [ mpls ]
ttl-value |
(Optional) Time-to-live (TTL) value. Range is 1 to 255 hops. |
mpls |
(Optional) Disables BGP label rewrite. |
Default TTL value is 255.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the ebgp-multihop command to enable multihop peerings with external BGP neighbors. The BGP protocol states that external neighbors must be directly connected (one hop away). The software enforces this by default; however, the ebgp-multihop command can be used to override this behavior.
Use of the mpls option in the ebgp-multihop command prevents BGP from enabling MPLS on the peering interface and also prevents allocation of Implicit-NULL rewrite labels for nexthop addresses learned from the peer. This is useful in some scenarios in which MPLS forwarding labels to the nexthops have already been learned via BGP labeled-unicast or LDP.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
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 109 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.16.6 RP/0/RP0/CPU0:router(config-bgp-nbr)# ebgp-multihop
To enable the router to receive the demilitarized zone (DMZ) link bandwidth extended community from an eBGP neighbor, use the ebgp-recv-extcommunity-dmz command in the neighbor configuration mode, neighbor group or session group configuration mode. To prevent the router from receiving DMZ link bandwidth extended community from an eBGP neighbor, use the no form of this command.
ebgp-recv-extcommunity-dmz
no ebgp-recv-extcommunity-dmz
This command has no arguments or keywords.
The router does not receive the link bandwidth community.
Neighbor configuration
Neighbor Group configuration
Session Group configuration
Release |
Modification |
---|---|
Release 6.1.2 |
This command was introduced. |
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to receive the link bandwidth community attributes from an eBGP neighbor:
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.67.89.01 RP/0/RP0/CPU0:router(config-bgp-nbr)#ebgp-recv-extcommunity-dmz
To enable the router to advertise demilitarized zone (DMZ) link bandwidth extended community to an eBGP neighbor, use the ebgp-send-extcommunity-dmz command in the neighbor configuration mode, neighbor group or session group configuration mode. To prevent the router from advertising DMZ link bandwidth extended community to an eBGP neighbor, use the no form of this command.
ebgp-send-extcommunity-dmz
no ebgp-send-extcommunity-dmz { cumulative | inheritance-disabled }
cumulative |
(Optional) Sends cumulative demilitarized zone (DMZ) link bandwidth extended community of all multipaths to the eBGP neighbour. |
inheritance-disabled |
(Optional) Prevents the inheritance of the ebgp-send-extcommunity-dmz command from the parent. |
The router does not advertise the link bandwidth community.
Neighbor configuration
Neighbor Group configuration
Session Group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to advertise the link bandwidth community to an eBGP neighbor:
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#ebgp-send-extcommunity-dmz
The following example shows how to advertise cumulative community DMZ link bandwidth of all multipaths to an eBGP neighbour:
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#ebgp-send-extcommunity-dmz cumulative
The following example shows how to advertise cumulative community DMZ link bandwidth of all multipaths to an eBGP neighbour:
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#ebgp-send-extcommunity-dmz cumulative inheritance-disabled
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 ]
policy-name |
Name of the configured route policy. |
No default behavior or values
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the export route-policy command to define the conditions that allow specified routes to be tagged with specified route-targets.
Task ID |
Operations |
---|---|
bgp |
read, write |
ip-services |
read, write |
The following example shows how to configure an export route policy:
RP/0/RP0/CPU0:router(config)# vrf vrf-1 RP/0/RP0/CPU0:router(config-vrf)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-vrf-af)# export route-policy policy-A
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 ]
as-number:nn |
(Optional) as-number —Autonomous system (AS) number of the route-target extended community. |
ip-address:nn |
(Optional) IP address of the route-target extended community. |
No default behavior or values
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
ip-services |
read, write |
The following example shows how to specify an export route-target:
RP/0/RP0/CPU0:router(config)# vrf vrf-1 RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-vrf-af)# export route-target 500:1
To allow an outbound route policy for an internal BGP (iBGP) peer to modify all BGP route attributes, only when an iBGP route is sent to another iBGP peer (only on route-reflectors), use the ibgp policy out enforce-modifications command in XR Config mode. To disable this feature, use the no form of this command.
ibgp policy out enforce-modifications
no ibgp policy out enforce-modifications
This command has no arguments or keywords.
ibgp policy out enforce-modifications is disabled.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the ibgp policy out enforce-modifications command to set and modify BGP route attributes for updates to iBGP peers.
If the ibgp policy out enforce-modifications command is configured under router BGP configuration, then all the changes made by the outbound policy for an iBGP peer will be present in an update message sent to the peer.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to set the ibgp policy out enforce-modifications:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 6500 RP/0/RP0/CPU0:router(config-bgp)# ibgp policy out enforce-modifications
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 ]
policy-name |
Name of the configured route policy. |
No default behavior or values
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
ip-services |
read, write |
RP/0/RP0/CPU0:router(config)# vrf vrf-1 RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-vrf-af)# import route-policy policy-B
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 ]
as-number:nn |
(Optional) Autonomous system (AS) number of the route-target extended community. |
ip-address:nn |
(Optional) IP address of the route-target extended community. |
No default behavior or values
Global VRF IPv4 address family configuration
Global VRF IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
ip-services |
read, write |
The following example shows how to specify an import route-target:
RP/0/RP0/CPU0:router(config)#vrf vrf-1 RP/0/RP0/CPU0:router(config-vrf)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-vrf-af)# import route-target 500:99
To enable the software to bypass the directly connected next hop check for single-hop eBGP peering, use the ignore-connected-check command in an appropriate configuration mode. To re-enable the directly connected next hop check, use the no form of this command.
ignore-connected-check [ inheritance-disable ]
no ignore-connected-check
inheritance-disable |
Prevents the ignore-connected-check command from being inherited from the parent. |
Ability to bypass the directly connected next hop check is disabled.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable ignore-connected check configuration for neighbor 10.2.3.4:
RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.2.3.4 RP/0/RP0/CPU0:router(config-bgp-nbr)# ignore-connected-check
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 ]
name |
Key chain name configured using the keychain command. The name must be a maximum of 32 alphanumeric characters. |
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.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Specify a key chain to enable key chain authentication between two BGP peers. Use the keychain command to implement hitless key rollover for authentication.
![]() Note | BGP only supports HMAC-MD5 and HMAC-SHA1-12 cryptographic algorithms. |
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# keychain keychain_A
![]() Note | Effective with Release 3.9.0, the keychain-disable command was replaced by the keychain inheritance-disable command. See the keychain inheritance-disable command for more information. |
To override any inherited key chain configuration from a neighbor group or session group for Border Gateway Protocol (BGP) neighbors, use the keychain-disable command in an appropriate configuration mode. To disable overriding any inherited key chain command, use the no form of this command.
keychain-disable
no keychain-disable
This command has no arguments or keywords.
Configured key chains for neighbor and session groups are inherited.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 140 RP/0/RP0/CPU0:router(config-bgp)# session-group group1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# keychain keychain_A RP/0/RP0/CPU0:router(config-bgp-sngrp)# exit RP/0/RP0/CPU0:router(config-bgp)#neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2 RP/0/RP0/CPU0:router(config-bgp-nbr)#use session-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# 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 inheritance-disable command in an appropriate configuration mode. To disable overriding any inherited key chain command, use the no form of this command.
keychain inheritance-disable
no keychain inheritance-disable
This command has no arguments or keywords.
Configured key chains for neighbor and session groups are inherited.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
If you specify a key chain on a neighbor group or session group, all users of the group inherit the key chain. Specifying a different keychain command specifically on a neighbor that uses the group overrides the inherited value. Specifying keychain inheritance-disable on a neighbor that uses the group disables key chain authentication for the neighbor.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)#router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# session-group group1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# keychain keychain_A RP/0/RP0/CPU0:router(config-bgp-sngrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2 RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# keychain inheritance-disable
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 [ replace-as [dual-as] ] ] | inheritance-disable }
no local-as [ as-number [ no-prepend [ replace-as [dual-as] ] ] | inheritance-disable ]
as-number |
Valid autonomous system number. Range for 2-byte Autonomous system numbers (ASNs) is 1 to 65535. Range for 4-byte Autonomous system numbers (ASNs) in asplain format is 1 to 4294967295. Range for 4-byte Autonomous system numbers (ASNs) is asdot format is 1.0 to 65535.65535. Cannot be the autonomous system number to which the neighbor belongs. |
no-prepend |
(Optional) Specifies that local autonomous system values are not prepended to announcements from the neighbor. |
replace-as |
(Optional) Specifies that prepend only local autonomous system values to announcements to the neighbor. |
dual-as |
(Optional) Dual-AS mode. |
inheritance-disable |
Prevents local AS from being inherited from the parent. |
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.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
You can specify the autonomous system number the local BGP uses to peer with each neighbor. The autonomous system number specified with this command cannot be the local BGP autonomous system number (specified with the router bgp command) or the autonomous system number of the neighbor (specified with the remote-as command). However, from Release 5.2.2, the autonomous system number for local-as and remote-as can be the same, which makes the resulting neighbor peering being treated as iBGP. This command cannot be specified for internal neighbors or for external neighbors in an autonomous system that is part of a confederation.
If this command is configured for a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 300 RP/0/RP0/CPU0:router(config-bgp-nbr)# local-as 30
To identify specific flow-tag values as match criteria in a class-map, use the match flow-tag command in class-map configuration mode. To remove a specific flow tag value from the matching criteria for a class-map, use the no form of this command.
match flow-tag { flow-tag number }
no match flow-tag { flow-tag number }
flow-tag number |
A flow-tag number. Range is from 1 to 63. |
No match criteria is specified.
Class-map configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
class-map |
read, write |
This example uses theshow route command to display the flow-tag for a given route.
RP/0/0/CPU0:ios-xr# RP/0/0/CPU0:ios-xr#show route 4.4.4.0/24 detail Thu Nov 14 15:32:21.010 PST Routing entry for 4.4.4.0/24 Known via "bgp 200", distance 20, metric 0 Tag 300, type external Installed Nov 14 09:36:55.066 for 05:55:26 Routing Descriptor Blocks 3.3.3.3, from 3.3.3.3, BGP external Route metric is 0 Label: None Tunnel ID: None Extended communities count: 0 NHID:0x0(Ref:0) Route version is 0x1 (1) No local label IP Precedence: Not Set QoS Group ID: Not Set Flow-tag: 220 Route Priority: RIB_PRIORITY_RECURSIVE (12) SVD Type RIB_SVD_TYPE_LOCAL Download Priority 4, Download Version 7 No advertising protos. RP/0/0/CPU0:ios-xr#
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 ]
ebgp |
Specifies external BGP multipath peers. |
ibgp |
Specifies internal BGP multipath peers. |
eibgp |
Specifies internal and external BGP multipath peers. eiBGP allows simultaneous use of internal and external paths. |
maximum |
Maximum number of parallel routes that BGP installs in the routing table. Range is 2 to 8 |
unequal-cost |
(Optional) Allows iBGP multipaths to have different BGP next-hop Interior Gateway Protocol (IGP) metrics. This option is available when the ibgp keyword is used. |
One path is installed in the routing table.
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 in the BGP Configuration Guide for Cisco NCS 5000 Series Routers for information on the BGP best-path algorithm.
![]() Note | The maximum-paths command with the eibgp keyword cannot be configured if the ibgp or ebgp keywords have been configured, because the eibgp keyword is a superset of the ibgp or ebgp keywords. |
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# maximum-paths ebgp 4
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 ] [ discard-extra-paths ] [ warning-only ] [ restart time-interval ]
no maximum-prefix maximum [ threshold ] [ discard-extra-paths ] [ warning-only ] [ restart time-interval ]
maximum |
|
||
discard-extra-paths |
(Optional) Drops all the excess prefixes received from the neighbor when the prefixes exceed the configured maximum value. |
||
threshold |
(Optional) Integer specifying at what percentage of the maximum argument value the software starts to generate a warning message. Range is from1 to 100. |
||
warning-only |
(Optional) Instructs the software to only generate a log message when the maximum argument value is exceeded, and not to terminate the peering. |
||
restart time-interval |
(Optional) Sets the time interval (in minutes) after which peering session should be reestablished. Configure restart time interval in minutes. Range is from 1 to 65535. |
When this command is not specified, the following defaults apply:
The default threshold, when a warning message is generated, is 75 percent.
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv6 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the maximum-prefix command to configure a maximum number of prefixes that a BGP router is allowed to receive from a neighbor. It adds another mechanism (besides routing policy) to control prefixes received from a peer.
When the number of received prefixes exceeds the maximum number configured, the software terminates the peering, by default, after sending a cease notification to the neighbor. However, if the warning-only keyword is configured, the software writes only a log message, but continues peering with the sender. If the peer is terminated, the peer stays down until the clear bgp command is issued or the restart time-interval option is used.
This command takes effect immediately if configured on an established neighbor, unless the number of prefixes received from the neighbor already exceeds the configured limits.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#neighbor 192.168.40.25 RP/0/RP0/CPU0:router(config-bgp-nbr)#remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)#address-family ipv6 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)#maximum-prefix 5000 80 restart 20
RP/0/RP0/CPU0:router(config-bgp)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# neighbor 192.168.40.24 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# maximum-prefix 1000
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 10 RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.0.0.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)#maximum-prefix 5000 discard-extra-paths
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
interface id |
Name of the interface. |
No default behavior or values
Router configuration
Neighbor configuration
IPv4 address family group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Thempls activate command enables MPLS on the interface specified and also adds the implicit null rewrite corresponding to the peer associated with the interface. The interface specified must be the one corresponding to the inter-AS ASBR or CSC peer.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to activate MPLS for CSC (with confederations):
router bgp 2002 bgp confederation peers 1 ! bgp confederation identifier 4589 bgp router-id 4.4.4.4 address-family ipv4 unicast allocate-label all ! address-family vpnv4 unicast retain route-target all ! vrf foo rd 1:1 mpls activate interface GigabitEthernet0/1/0/2 ! address-family ipv4 unicast redistribute connected allocate-label all ! neighbor 10.0.0.1 remote-as 1 address-family ipv4 unicast ! address-family ipv4 labeled-unicast route-policy pass in route-policy pass out ! ! ! ! RP/0/RP0/CPU0:router#show mpls forwarding Local Outgoing Prefix Outgoing Next Hop Bytes Label Label or ID Interface Switched ------ ----------- ------------------ ------------ --------------- ------------ 16000 Aggregate foo: Per-VRF Aggr[V] \ foo 0 16001 Pop 10.0.0.0/16[V] Gi0/1/0/2 10.0.0.1 44 RP/0/RP0/CPU0:router#show mpls interfaces Interface LDP Tunnel Enabled -------------------------- -------- -------- -------- GigabitEthernet0/1/0/2 No No Yes
To enable BGP instance to connect to PIM/PIM6, use the mvpn command in XR Config mode. To disable BGP instance -PIM/PIM6 connection, use the no form of this command.
mvpn
no mvpn
This command has no keywords or arguments.
PIM/PIM connection is disabled.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to configure mvpn and enable PIM/PIM6 connection:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#mvpn
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
ip-address |
IPv4 or IPv6 IP address of the BGP-speaking neighbor. |
Neighbor mode is not specified.
Router configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
From router configuration mode, you can use this command to enter neighbor configuration mode.
From neighbor configuration mode, you can enter address family configuration for the neighbor by using the address-family command, which allows you to configure routing sessions for IP Version 4 and IP Version 6 address prefixes.
The neighbor command does not cause the neighbor to be configured and does not result in a peering to be established with the neighbor. To create the neighbor, you configure a remote autonomous system number by entering the remote-as command, or the neighbor can inherit a remote autonomous system from a neighbor group or session group if the use command is applied.
![]() Note | A neighbor must have must a remote autonomous system number, and an IP address and address family must be enabled on the neighbor. |
Unlike IPv4, IPv6 must be enabled before any IPv6 neighbors can be defined. Enable IPv6 in router configuration mode using the address-family command.
![]() Note | Configuration for the neighbor cannot occur (peering is not established) until the neighbor is given a remote as-number and neighbor address. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.168.40.24 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 65000
RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv6 unicast RP/0/RP0/CPU0:router(config-bgp-af)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 3000::1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2002 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv6 unicast
To create a neighbor group and enter neighbor group configuration mode, use the neighbor-group command in XR Config 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
name |
Neighbor group name. |
No neighbor group mode is specified.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
The neighbor-group command puts the router in neighbor group configuration mode and creates a neighbor group.
A neighbor group helps you apply the same configuration to one or more neighbors. After a neighbor group is configured, each neighbor can inherit the configuration through the use command. If a neighbor is configured to use a neighbor group, the neighbor, by default, inherits the entire configuration of the neighbor group, which includes the address family-independent and address family-specific configurations. The inherited configuration can be overridden if you directly configure commands for the neighbor or if you configure session groups or address family groups with the use command.
From neighbor group configuration mode, you can configure address family-independent parameters for the neighbor group. To enter address family-specific configuration for the neighbor group, use the address-family command when in the neighbor group configuration mode.
![]() Note | If an address family is configured for a neighbor group, neighbors that use the neighbor group attempt to exchange routes in that address family. |
The no form of this command ordinarily causes all configuration for the neighbor group to be removed. If using the no form would result in a neighbor losing its remote autonomous system number, the configuration is rejected. In this scenario, the neighbor configuration must be either removed or configured with a remote autonomous system number before the neighbor group configuration can be removed.
![]() Note | Neighbor groups should not be configured with a mixture of IPv4 and IPv6 address families, because such a neighbor group is not usable by any neighbor. Note that within the Cisco IOS XR system configuration architecture, it is possible to create such a neighbor group; however, any attempt to use it is rejected. |
Task ID |
Operations |
---|---|
bgp |
read, write |
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 65530 RP/0/RP0/CPU0:router(config-bgp)# neighbor-group group1 RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# remote-as 65535 RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# advertisement-interval 2 RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# send-community-ebgp RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exit RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# next-hop-self RP/0/RP0/CPU0:router(config-bgp-nbrgrp-af)# exit RP/0/RP0/CPU0:router(config-bgp-nbrgrp)# exit RP/0/RP0/CPU0:router(config-bgp)#neighbor 10.0.0.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# use neighbor-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2 RP/0/RP0/CPU0:router(config-bgp-nbr)# use neighbor-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# exit
To preserve the iBGP-CE (customer edge) attributes inside the VPN attribute set (ATTR-SET) and send it across to the core, use the neighbor internal-vpn-client command in the VRF neighbor configuration mode. To disable the command, use the no form of this command.
neighbor ip-address internal-vpn-client
no neighbor ip-address internal-vpn-client
neighbor ip-address |
IP address of the neighboring device. |
internal-vpn-client |
Stacks the iBGP-CE neighbor path in the VPN attribute set. |
None
VRF neighbor configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
The neighbor ip-address internal-vpn-client command enables PE devices to make the entire VPN cloud act as an internal VPN client to the CE devices connected internally. This command is used so that existing internal BGP VRF lite scenarios are not affected. You need not configure autonomous system override for CE devices after enabling this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure L3VPN iBGP PE-CE:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# vrf blue neighbor 10.10.10.1 RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# internal-vpn-client
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 ]
ip- address |
Network that BGP advertises. |
/ prefix-length |
Length of the IP address prefix. A decimal value that indicates how many of the high-order contiguous bits of the address compose the prefix (the network portion of the address). A slash (/) must precede the decimal value. |
ip-address mask |
Network mask applied to the ip-address argument. |
route-policy route-policy-name |
(Optional) Specifies a route policy to use to modify the attributes of the network. |
No networks are specified.
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)#router bgp 120 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# network 172.20.0.0/16
To set the administrative distance on an external Border Gateway Protocol (eBGP) route to that of a locally sourced BGP route, causing it to be less preferred than an Interior Gateway Protocol (IGP) route, use the network backdoor command in an appropriate configuration mode. To disable setting the administrative distance to the value for locally sourced BGP routes, use the no form of this command.
network { ip-address/prefix-length | | ip-address mask } backdoor
no network { ip-address/prefix-length | | ip-address mask } backdoor
ip-address |
Network that provides a backdoor route. |
/ prefix-length |
Length of the IP address prefix. A decimal value that indicates how many of the high-order contiguous bits of the address compose the prefix (the network portion of the address). A slash (/) must precede the decimal value. |
mask |
Network mask applied to the ip-address argument. |
No backdoor routes are installed.
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# network 192.168.40.0/24 backdoor
To disable next-hop calculation and insert your own address in the next-hop field of Border Gateway Protocol (BGP) updates, use the next-hop-self command in an appropriate configuration mode. To enable next-hop calculation, use the no form of this command.
next-hop-self [ inheritance-disable ]
no next-hop-self [ inheritance-disable ]
inheritance-disable |
(Optional) Allows a next-hop calculation override when this feature may be inherited from a neighbor group or address family group. |
When this command is not specified, the software calculates the next hop for BGP updates accepted by the router.
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Use the next-hop-self command to set the BGP next-hop attribute of routes being advertised over a peering session to the local source address of the session.
This command is useful in nonmeshed networks in which BGP neighbors may not have direct access to all other neighbors on the same IP subnet.
If this command is configured for a neighbor group or address family group, a neighbor using the group inherits the configuration. Configuring the command specifically for a neighbor overrides any inherited value.
Configuring the next-hop-self command under IPv4 labeled-unicast, IPv6 labeled-unicast, or VRF labeled-unicast address family configuration mode enables next-hop-self for labeled prefixes advertised to an iBGP peer.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# next-hop-self
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-self RP/0/RP0/CPU0:router(config-bgp-afgrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr-af)# next-hop-self inheritance-disable
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 [ inheritance-disable ]
no next-hop-unchanged [ inheritance-disable | multipath ]
inheritance-disable |
(Optional) Allows overwriting of the next hop before advertising to eBGP peers when this feature may be inherited from a neighbor group or address family group. |
multipath |
(Optional) Disables overwriting of next-hop calculation for multipath prefixes. |
Overwriting of the next hop is allowed.
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the next-hop-unchanged command to propagate the next hop unchanged for multihop eBGP peering sessions. This command should not be configured on a route reflector, and the next-hop-self command should not be used to modify the next-hop attribute for a route reflector when this feature is enabled for a route reflector client.
![]() Note | Incorrectly setting BGP attributes for a route reflector can cause inconsistent routing, routing loops, or a loss of connectivity. Setting BGP attributes for a route reflector should be attempted only by an experienced network operator. |
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-unchanged disable RP/0/RP0/CPU0:router(config-bgp-afgrp)# exit
RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-unchanged multipath RP/0/RP0/CPU0:router(config-bgp-afgrp)# exit
To set minimum prefix-length for nexthop resolution, use the nexthop resolution prefix-length minimum command in an appropriate configuration mode. To disable the minimum prefix-length for nexthop resolution, use the no form of this command.
nexthop resolution prefix-length minimum prefix-length-value
no nexthop resolution prefix-length minimum prefix-length-value
prefix-length-value |
Sets the minimum prefix-length. Range is 0 to 32. |
Nexthop resolution for minimum prefix-length is disabled.
VPNv4 Unicast address family
VRF IPv4 Unicast address family
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set the minimum prefix-length for nexthop resolution as 32:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)#nexthop resolution prefix-length minimum 32
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
route-policy-name |
Route policy to use for filtering based on next hops. |
No default behavior or values
IPv4 address family configuration
IPv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 109 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# nexthop route-policy nexthop_A
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 }
critical |
Specifies critical next-hop events. For example, when the next hop is unreachable. |
delay |
Trigger delay, in milliseconds. Range is 0 to 4294967295. |
non-critical |
Specifies noncritical next-hop events. For example, Interior Gateway Protocol (IGP) metric changes. |
critical : 3000 msec for IPv4 address family and IPv6 address family
critical: 0 msec for VPNv4 address family and VPNv6 address family
non-critical: 10000 msec IPv4, IPv6, VPNv4, and VPNv6 address families
IPv4 address family configuration
Pv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the nexthop trigger-delay command to allow for a dynamic way for Interior Gateway Protocol (IGP) to converge. This convergence allows BGP to accumulate all notifications and trigger fewer walks, resulting in fewer interprocess communications (IPCs) to the Routing Information Base (RIB) for route addition, deletion, and modification and fewer updates to peers.
![]() Note | A high delay value can be configured to effectively turn off next-hop tracking. |
The non-critical delay value must always be set to at least equal or greater than the critical delay value .
The delay should be slightly higher than the time it takes for the IGP to settle into a steady state after some event (IGP convergence time).
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# nexthop trigger-delay critical 3500
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
route-policy-name |
Name of the route policy. |
No ORF route policy is defined.
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to configure outbound and inbound filtering criteria:
RP/0/RP0/CPU0:router(config)#router bgp 6 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)#orf route-policy policy_A
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 ]
clear |
Specifies that an unencrypted password follows. The password must be a case-sensitive, clear-text unencrypted password. |
encrypted |
Specifies that an encrypted password follows. The password must be a case-sensitive, encrypted password. |
password |
Password of up to 80 characters. The password can contain any alphanumeric characters. However, if the first character is a number or the password contains a space, the password must be enclosed in double quotation marks; for example, “2 password.” |
When this command is not specified in the appropriate configuration mode, MD5 authentication is not enabled on a TCP connection between two BGP neighbors.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 140 RP/0/RP0/CPU0:router(config-bgp)#neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)#password clear password1
To specify a SSH password for the RPKI cache-server, use the password command in rpki-server configuration mode. To remove the SSH passwords, use the no form of this command.
password password
no password password
password |
Enters a password to be used for the SSH transport mechanism. |
Password is not configured.
RPKI server configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
SSH expects to use an authentication method to connect to a remote server. The SSH authentication method to connect to RPKI server is password-based. So, the RPKI cache-server must be configured with username and password. A username and password must be configure for each server configured under BGP that uses the SSH transport
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to configure a username (rpki-user) and password (rpki-ssh-pass) for the RPKI cache-server SSH transport mechanism:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#rpki server 172.168.35.40 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)# transport ssh port 22 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#username rpki-user RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#password rpki-ssh-pass
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
This command has no arguments or keywords.
Configured passwords for neighbor and session groups are inherited.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 140 RP/0/RP0/CPU0:router(config-bgp)# session-group group1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# password clear password1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 2 RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# password-disable
To define a prefix set as permanent, use the permanent-network command in the global address family configuration mode. To remove a prefix set as permanent, use the no form of this command. The permanent-network command uses a route-policy to identify the set of prefixes (networks) for which permanent paths needs to be created.
The permanent network feature supports only prefixes in IPv4 unicast and IPv6 unicast address-families under the default Virtual Routing and Forwarding (VRF).
permanent-network route-policy route-policy-name
no permanent-network
route-policy route-policy-name |
Specifies a configured routing policy. |
None
Address-family configuration.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
This example shows how to define permanent path for a route policy named POLICY-PERMANENT-NETWORK-IPv4:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-af)# permanent-network route-policy POLICY-PERMANENT-NETWORK-IPv4
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 ]
value |
Value of the precedence. The precedence value can be a number from 0 to 7, or it can be one of the following keywords: routine —Set packets with routine precedence (0) priority —Set packets with priority precedence (1) immediate —Set packets with immediate precedence (2) flash — Set packets with flash precedence (3) flash-override —Set packets with flash override precedence (4) critical —Set packets with critical precedence (5) internet —Set packets with internetwork control precedence (6) network —Set packets with network control precedence (7) |
No default behavior or values
Neighbor configuration
Neighbor session group configuration
Neighbor group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the precedence command to set the precedence value.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 5 RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100 RP/0/RP0/CPU0:router(config-bgp-nbr)# precedence 2
To specify a preference value for the RPKI cache-server, use the preference command rpki-server configuration mode. To remove the preference value, use the no form of this command.
preference preference-value
no preference preference-value
preference-value |
Specifies a RPKI cache preference value. Range is 1 to 10.
|
Preference value is not set.
RPKI server configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set preference value for RPKI configuration as 1:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#rpki server 172.168.35.40 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)# transport ssh port 22 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#username rpki-user RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#password rpki-ssh-pass RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#preference 1
To configure the time BGP waits to keep routes from RPKI cache-server after the cache session drops, use the purge-time command in rpki-server configuration mode. To remove the purge-time configuration, use the no form of this command.
purge-time time-in-seconds
no purge-time time-in-seconds
time-in-seconds |
Sets the purge time in seconds. Range is 30 to 360 seconds. |
Purge time is not set.
RPKI server configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
When a cache session is dropped then a "purge-timer" is started for that cache. If the session re-establishes within the timer interval, then the purge timer is stopped and no further action is taken. If the cache session does not re-establish within the timer interval, only then does BGP remove all ROAs from the cache.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set the purge-time for RPKI cache as 30 seconds:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#rpki cache 172.168.35.40 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)# transport ssh port 22 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#username rpki-user RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#password rpki-ssh-pass RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#preference 1 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#purge-time 30
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 }
as-number:nn |
|
ip-address:nn |
IP address of the route distinguisher. |
auto |
Automatically assigns a unique route distinguisher. |
No default behavior or values
VRF configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
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 1 RP/0/RP0/CPU0:router(config-bgp)# vrf vrf-1 RP/0/RP0/CPU0:router(config-bgp-vrf)# rd auto
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 ]
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. |
socket-size : 32,768 bytes
bgp-size : 4,032 bytes
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the receive-buffer-size command to increase the buffer size when receiving updates from a neighbor. Using larger buffers can improve convergence time because it allows the software to process a larger number of packets simultaneously. However, allocating larger buffers consumes more memory on the router.
![]() Note | Increasing the socket buffer size uses more memory only when more messages are waiting to be processed by the software. In contrast, increasing the BGP buffer size uses extra memory indefinitely. |
If this command is configured for a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# receive-buffer-size 65536 8192
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.
redistribute connected [ metric metric-value ] [ route-policy route-policy-name ]
no redistribute connected [ metric metric-value ] [ route-policy route-policy-name ]
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 ]
redistribute ospf process-id
no redistribute ospf process-id
redistribute ospf process-id
no redistribute ospf process-id
redistribute static [ metric metric-value ] [ route-policy route-policy-name ]
no redistribute static [ metric metric-value ] [ route-policy route-policy-name ]
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.
IPv4 address family configuration, both unicast and multicast (connected, isis, ospf, and static are supported)
IPv6 address family configuration, both unicast and multicast (connected,
isis,
ospfv3,
and static are supported)
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
![]() Note | When redistributing routes (into BGP) using both command keywords for setting or matching of attributes and a route policy, the routes are run through the route policy first, followed by the keyword matching and setting. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 109 RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# redistribute ospf 110
To configure the time BGP waits in between sending periodic serial queries to the RPKI server, use the refresh-time command in rpki-server configuration mode. To remove the refresh-time configuration, use the no form of this command.
refresh-time { time-in-seconds | off }
no refresh-time { time-in-seconds | off }
off |
Specifies not to send serial queries periodically. |
time-in-seconds |
Sets the refresh-time in seconds. Range is 30 to 3600 seconds. |
Refresh-time is not set.
RPKI cache configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set the refresh-time for BGP to wait in between sending periodic serial queries to the server as 30 seconds:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#rpki server 172.168.35.40 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)# transport ssh port 22 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#username rpki-user RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#password rpki-ssh-pass RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#preference 1 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#purge-time 30 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#refresh-time 30
To configure the time BGP waits for a response from the RPKI cache-server after sending a serial or reset query, use the response-time command in rpki-server configuration mode. To remove the response-time configuration, use the no form of this command.
response-time { time-in-seconds | off }
no response-time { time-in-seconds | off }
off |
Specifies to wait indefinitely for a response from the RPKI cache. |
time-in-seconds |
Specifies the response-time in seconds. Range is 30 to 3600 seconds. |
Response-time is not set.
RPKI server configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to set the time for BGP to wait for a response from the RPKI server as 30 seconds, after sending a serial or reset query:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#rpki server 72.168.35.40 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)# transport ssh port 22 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#username rpki-user RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#password rpki-ssh-pass RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#preference 1 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#purge-time 30 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#refresh-time 30 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#response-time 30
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 ]
as-number |
Autonomous system (AS) to which the neighbor belongs. |
No BGP neighbors exist.
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the remote-as command to create a neighbor and assign it a remote autonomous system number. A neighbor must have a remote autonomous system number before any other commands can be configured for it. Removing the remote autonomous system from a neighbor causes the neighbor to be deleted. You cannot remove the autonomous system number if the neighbor has other configuration.
![]() Note | We recommend that you use the no neighbor command rather than the no remote-as command to delete a neighbor. |
A neighbor specified with a remote autonomous system number that matches the autonomous system number specified in the router bgp command identifies the neighbor as internal to the local autonomous system. Otherwise, the neighbor is considered external.
Configuration of the remote-as command for a neighbor group or session group using the neighbor-group command or session-group command causes all neighbors using the group to inherit the characteristics configured with the command. Configuring the command directly for the neighbor overrides the value inherited from the group.
In the neighbor configuration submode, configuring use of a session group or neighbor group for which remote-as is configured creates a neighbor and assigns it an autonomous system number if the neighbor has not already been created.
![]() Note | Do not combine remote-as commands and no use neighbor-group commands, or remote-as commands and no use session-group commands, in the same configuration commit. |
Task ID |
Operations |
---|---|
bgp |
read, write |
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 1 RP/0/RP0/CPU0:router(config-bgp)# session-group group2 RP/0/RP0/CPU0:router(config-bgp-sngrp)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-sngrp)#exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1 RP/0/RP0/CPU0:router(config-bgp-nbr)#use session-group group2
The following example shows how to configure a session group called group2 with an autonomous system number 1. Neighbor 10.0.0.1 is created when it inherits the autonomous system number 1 from session group group2.
RP/0/RP0/CPU0:router(config)#router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# session-group group2 RP/0/RP0/CPU0:router(config-bgp-sngrp)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group2
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 [ inheritance-disable ] [entire-aspath]
no remove-private-as [ inheritance-disable ] [entire-aspath]
inheritance-disable |
(Optional) Permits the feature to be disabled from a neighbor group or address family group instead of being inherited. |
entire-aspath |
(Optional) Removes the entire private autonomous system numbers from an autonomous system path only if all ASes in the path are private. |
When this command is not specified in the appropriate configuration mode, private autonomous system numbers are not removed from updates sent to external neighbors.
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
This feature is available for external BGP (eBGP) neighbors only.
When an update is passed to the external neighbor, the software drops any private autonomous system numbers, no matter it is leading or in the middle of the AS_SEQUENCE.
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.
Use the entire-aspath to removes the entire private autonomous system numbers from an autonomous system path only if all ASes in the path are private.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# remove-private-as
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# remove-private-as RP/0/RP0/CPU0:router(config-bgp-afgrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr-af)# remove-private-as inheritance-disable
To retain the local label until the network is converged, use the retain local-label command in an appropriate address family configuration mode. To disable the retaining of the local label, use the no form of this command.
retain local-label minutes
no retain local-label
minutes |
Local retention time in minutes. The range is 3 to 60 minutes. The default retention time is 5 minutes. |
minutes : 5
L2VPN address family configuration
VPNv4 address family configuration
VPNv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
The following example shows how to enable local label retention for 5 minutes:
RP/0/RP0/CPU0:router# configure RP/0/RP0/CPU0:router(config)# router bgp 100 RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# retain local-label 5
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 ]
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. |
The default is to accept all route targets.
VPNv4 address family configuration
VPNv6 address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the retain route-target command to configure a route reflector (RR) to retain routes tagged with specific route targets (RT).
The retain route-target is a required command for Inter-AS option B ASBR. By default, an Inter-AS option B ASBR needs the retain route-target configured to get VPNv4 BGP table from PE routers, either with the all or with the route-policy option.
A provider edge (PE) router is not required to hold all VPNv4 routes. The PE router holds only routes that match the import RT of the VPNs configured on it, but a RR must retain all VPNv4 routes because it may peer with PE routers and different PEs may require different RT-tagged VPNv4 routes. Configuring an RR to hold only routes that have a defined set of RT communities and configuring some of these RRs to service a different set of VPNs provides scalability to the RRs. A PE can be configured to peer with all RRs that service the VPN routing and forwarding (VRF) instances configured on the PE. When a new VRF is configured with an RT for which the PE does not already hold routes, the PE issues route refresh requests to the RRs and gets the relevant VPN routes.
The route-policy route-policy-name keyword and argument takes the policy name that lists the extended communities that a path should have for the RR to retain the path.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# address-family vpnv4 unicast RP/0/RP0/CPU0:router(config-bgp-af)# retain route-target route-filter ft-policy-A
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 }
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. |
No policy is applied.
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 | Configuring a large number of uniquely named outbound neighbor policies can adversely affect performance. This is true even if the uniquely named route policies are functionally identical. The user is discouraged from configuring multiple functionally identical route policies for use with this command. For example, if Policy A and Policy B are identical but named for different neighbors, the two policies should be configured as a single policy. |
If the route-policy command is configured for a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 unicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# route-policy In-Ipv4 in
To configure the Border Gateway Protocol (BGP) routing process, use the router bgp command in XR Config mode. To remove all BGP configurations and terminate the BGP routing process, use the no form of this command.
router bgp as-number [ instance instance-name ]
no router bgp [ as-number ]
as-number |
Number that identifies the autonomous system (AS) in which the router resides. |
instance instance-name |
Specifies an instance and instance name. The maximum length for the instance name is 32 characters. The router bgp instance instance-name command replaced the distributed speaker command. |
No BGP routing process is enabled.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
rib |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 120
To enter resource public key infrastructure (RPKI) cache-server (rpki-sever) configuration mode and enable rpki parameters configuration, use the rpki server command in Router BGP configuration mode. To remove the rpki-server configuration mode and delink cache-server from the cache list, use the no form of this command.
rpki server { host-name | ip-address }
no rpki server { host-name | ip-address }
host-name |
Host name of the RPKI cache database. |
ip-address |
IP Address of the RPKI cache databse. |
RPKI server configuration is disabled.
Router BGP configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read, write |
This example shows how to configure an rpki cache-server database and enter rpki-server configuration mode:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#router bgp 100 RP/0/RP0/CPU0:router(config-bgp)#rpki server 172.168.35.40 RP/0/RP0/CPU0:router(config-bgp-rpki-cache)#
To disable selective VRF download (SVD) on a line card to enable download all prefixes and labels to the line card, use the selective-vrf-download disable command in XR Config mode. To enable the SVD, use the no form of this command.
selective-vrf-download disable
no selective-vrf-download disable
This command has no keywords or arguments.
SVD is enabled.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
You must failover the active RP or reload the router after disabling SVD for the configuration change to get activated.
Task ID | Operation |
---|---|
ip-services |
read, write |
This example shows how to disable selective vrf download:
RP/0/RP0/CPU0:router#configure RP/0/RP0/CPU0:router(config)#selective-vrf-download disable
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 ]
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. |
socket-size : 10240 bytes
bgp-size : 4096 bytes
Use the socket send-buffer-size command to change the defaults.
Neighbor configuration
VRF neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the send-buffer-size command to increase the buffer size employed when sending updates to a neighbor. Using larger buffers can improve convergence time because the software can process more packets simultaneously. However, allocating larger buffers uses more memory on the router.
![]() Note | Increasing the socket buffer size uses more memory only when more messages are waiting to be processed by the software. In contrast, increasing the BGP buffer size uses more memory indefinitely. |
If this command is configured for a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# send-buffer-size 8192 8192
To specify that community attributes should be sent to an external Border Gateway Protocol (eBGP) neighbor, use the send-community-ebgp command in an appropriate configuration mode. To disable sending community attributes to an eBGP neighbor, use the no form of this command.
send-community-ebgp [ inheritance-disable ]
no send-community-ebgp [ inheritance-disable ]
inheritance-disable |
(Optional) Allows configuration inherited from a neighbor group or address family group to be overridden. |
Community (COMM) attributes are NOT sent to eBGP peers (including PE-CE peers).
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the send-community-ebgp command to control whether community attributes are sent to eBGP neighbors. This command cannot be configured for iBGP neighbors as community attributes are always sent to iBGP neighbors.
When IOS XR BGP updates community attributes for eBGP VPN peers (VPNv4 or VPNv6), there is no need to configure the send-community-ebgp command separately. The community attributes are updated by default.
If this command is configured for a neighbor group or address family group, all neighbors using the group inherit the configuration. Configuring the command specifically for a neighbor overrides inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
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 140 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-community-ebgp
The following example shows how to disable the delivery of community attributes to neighbor 172.20.1.1, preventing this feature from being inherited from address family group group1:
RP/0/RP0/CPU0:router(config)#router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# send-community-ebgp RP/0/RP0/CPU0:router(config-bgp-afgrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-community-ebgp inheritance-disable
To specify that extended community attributes should be sent to external Border Gateway Protocol (eBGP) neighbors, use the send-extended-community-ebgp command in an appropriate configuration mode. To disable sending extended community attributes to eBGP neighbors, use the no form of this command.
send-extended-community-ebgp [ inheritance-disable ]
no send-extended-community-ebgp [ inheritance-disable ]
inheritance-disable |
(Optional) Allows configurations inherited from a neighbor group or address family group to be overridden. |
Extended community (EXTCOMM) attributes are NOT sent to eBGP peers (including PE-CE peers).
IPv4 address family group configuration
IPv6 address family group configuration
IPv4 neighbor address family configuration
IPv4 neighbor group address family configuration
IPv6 neighbor group address family configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the send-extended-community-ebgp command to control whether extended community attributes are sent to eBGP neighbors. This command cannot be used for iBGP neighbors as extended community attributes are always sent to iBGP neighbors.
When IOS XR BGP updates community attributes for eBGP VPN peers (VPNv4 or VPNv6), there is no need to configure the send-extended-community-ebgp command separately. The community attributes are updated by default.
If this command is configured for a neighbor group or neighbor address family group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-extended-community-ebgp
RP/0/RP0/CPU0:router(config)# router bgp 140 RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-afgrp)# send-extended-community-ebgp RP/0/RP0/CPU0:router(config-bgp-afgrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 172.20.1.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicast RP/0/RP0/CPU0:router(config-bgp-nbr-af)# use af-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr-af)# send-extended-community-ebgp inheritance-disable
To create a session group and enter session group configuration mode, use the session-group command inXR Config 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
name |
Name of the session group. |
No session groups are created.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read, write |
RP/0/RSP0RP0/CPU0:router(config)# router bgp 1 RP/0/RSP0RP0/CPU0:router(config-bgp)# session-group group1 RP/0/RSP0RP0/CPU0:router(config-bgp-sngrp)# remote-as 1 RP/0/RSP0RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 2 RP/0/RSP0RP0/CPU0:router(config-bgp-sngrp)# exit RP/0/RSP0RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1 RP/0/RSP0RP0/CPU0:router(config-bgp-nbr)# use session-group group1 RP/0/RSP0RP0/CPU0:router(config-bgp-nbr)# exit RP/0/RSP0RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2 RP/0/RSP0RP0/CPU0:router(config-bgp-nbr)# use session-group group1
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# session-group group1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# remote-as 1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# advertisement-interval 2 RP/0/RP0/CPU0:router(config-bgp-sngrp)# password password1 RP/0/RP0/CPU0:router(config-bgp-sngrp)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1 RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# exit RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.2 RP/0/RP0/CPU0:router(config-bgp-nbr)# use session-group group1 RP/0/RP0/CPU0:router(config-bgp-nbr)# password-disable
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 ]
active-only |
Ensures that the BGP session can be established only when the request is initiated by the local end (active-open request) and all passive-open requests (from the other end) are rejected by the local BGP. |
both |
Allows BGP sessions to be established from both incoming or outgoing TCP connection requests, with one being rejected in the event of a request collision. |
passive-only |
Ensures that the local BGP does not initiate any TCP open requests and the session can be established only when the request comes from the remote end. |
The default is both .
Neighbor configuration
Neighbor group configuration
Session group configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 | The BGP connection is not opened and, as a result the BGP session, is not established if both the peering neighbors use the same nondefault TCP session open mode—active-only or passive-only. If both ends are configured with active-only, each neighbor rejects the TCP open request from the other end. One neighbor must be configured as passive-only or both. Similarly, if both neighbors are configured with passive-only, neither neighbor initiates the TCP open request and the BGP session is not established. Again, one neighbor must be configured as active-only or both. There is one exception. A connection open request from a neighbor that is configured with the TCP session open mode to be passive-only is processed to detect whether there is a connection collision before the request is rejected. This exception enables the local BGP to reset the session if the remote neighbor goes down and it is not detected by the local router. |
Use the session-open-mode command when it may be necessary to preconfigure a neighbor that does not exist. Ensure that BGP does not spend any time actively trying to set up a TCP session with the neighbor. A BGP session does not come up between two neighbors, both of which configure the same nondefault value ( active-only or passive-only keyword) for this command.
Task ID |
Operations |
---|---|
bgp |
read, write |
RP/0/RP0/CPU0:router(config)# router bgp 1 RP/0/RP0/CPU0:router(config-bgp)# neighbor 45.67.89.01 RP/0/RP0/CPU0:router(config-bgp-nbr)# session-open-mode active-only
To set the flow-tag value for the PBR BGP, use the set flow-tag command in route-policy configuration mode.
set flow-tag { number | parameter }
number |
Flow-tag value. Range is from 1 to 63. |
parameter |
Parameter name. The parameter name must be preceded with a “$.” |
No default behavior or values
Route-policy configuration
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
Use the set flow-tag command to set the flow-tag to classify packets.
This command is supported at the BGP table-policy attachpoint. Prefixes are marked for subsequent processing in the forwarding plane. After flow-tag propagation through Border Gateway Protocol (BGP), flow-tag is enabled on an interface, corresponding traffic shaping and policing is completed using packet classification based on the flow-tag value.
Task ID |
Operations |
---|---|
route-policy |
read, write |
This example shows how to use set flow-tag command:
RP/0/RP0/CPU0:router(config)# route-policy policy_1 RP/0/RP0/CPU0:router(config-rpl)# set flow-tag 12 RP/0/RP0/CPU0:router(config-rpl)# end-policy
To display entries in the Border Gateway Protocol (BGP) routing table, use the show bgp command in XR EXEC mode.
show bgp [ ipv4 { unicast } | ipv6 { unicast } ]
ipv4 |
(Optional) Specifies IP Version 4 address prefixes. |
unicast |
(Optional) Specifies unicast address prefixes. |
ipv6 |
(Optional) Specifies IP Version 6 address prefixes. |
ipv4 { unicast | labeled-unicast } |
(Optional) For VRF, specifies IPv4 unicast or labeled-unicast address families. |
ipv6 unicast |
(Optional) For VRF, specifies IPv6 unicast address families. |
If no address family or subaddress family is specified, the default address family and subaddress family specified using the set default-afi and set default-safi commands are used.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
![]() Note | The set default-afi command is used to specify the default address family for the sessions and the set default-safi command is used to specify the default subaddress family for the session. See the System Management Command Reference for Cisco NCS 5000 Series Routers for detailed information and syntax for the set default-afi and set default-safi commands. If you do not specify a default address family, the default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family is unicast. |
BGP contains a separate routing table for each address family and subaddress family combination that has been configured. The address family and subaddress family options specify the routing table to be examined. If the all keyword is specified for an address family or a subaddress family, each matching routing table is examined in turn.
![]() Note | Running the show bgp command immediately after configuring a large and complex route policy may result in timeout of the system database shown through an error message (SYSDB-SYSDB-6-TIMEOUT_EDM). It is recommended, that the show command be run, after the new route policy takes effect. |
Use the show bgp ip-address { mask | / prefix-length } command to display detailed information for a specific route. If the mask and prefix length are omitted, the details of the longest matching prefix for the IP address are displayed.
Use the show bgp command to display all routes in the specified BGP routing table. Use the show bgp ip-address { mask | / prefix-length } longer-prefixes command to display those routes more specific than a particular prefix.
Use the unknown-attributes keyword to display details of any transitive attributes associated with a route that are not understood by the local system.
Use the show bgp ip-address/prefix-length detail command to display details of the specified prefix.
Task ID |
Operations |
---|---|
bgp |
read |
RP/0/RP0/CPU0:router# show bgp vpnv4 uni rd 2:1 3.0.0.0/24
[KBGP routing table entry for 3.0.0.0/24, Route Distinguisher: 2:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 350584 350584
Local Label: 16010
Last Modified: Jun 23 06:22:12.821 for 00:03:27
Paths: (1 available, best #1)
Not advertised to any peer
Path #1: Received by speaker 0
Not advertised to any peer
6913, (Received from a RR-client), (long-lived stale)
4.4.4.4 (metric 3) from 3.3.3.3 (4.4.4.4)
Received Label 16000
Origin EGP, localpref 100, valid, internal, best, group-best, import-candidate, not-in-vrf
Received Path ID 0, Local Path ID 1, version 350584
Extended community: RT:2:1
Originator: 4.4.4.4, Cluster list: 3.3.3.3
The following is the sample output from the show bgp <IP address> command displaying the graceful-shutdown community and the graceful-shut path attribute with BGP graceful maintenance feature activated:
RP/0/0/CPU0:R4#show bgp 5.5.5.5 ... 10.10.10.1 from 10.10.10.1 (192.168.0.5) Received Label 24000 Origin incomplete, metric 0, localpref 100, valid, internal, best, group-best, import-candidate Received Path ID 0, Local Path ID 1, version 4 Community: graceful-shutdown Originator: 192.168.0.5, Cluster list: 192.168.0.1 ...
The following is sample output from the show bgp command in XR EXEC mode:
RP/0/RP0/CPU0:router#show bgp BGP router identifier 172.20.1.1, local AS number 1820 BGP generic scan interval 60 secs BGP table state: Active Table ID: 0xe0000000 BGP main routing table version 3 Dampening enabled BGP scan interval 60 secs Status codes: s suppressed, d damped, h history, * valid, > best i - internal, S stale Origin codes: i - IGP, e - EGP, ? - incomplete Network 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 i Processed 8 prefixes, 8 paths
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/24 BGP router table entry for 11.0.0.0/24 Versions: Process bRIB/RIB SendTblVer Speaker 2 2 Last Modified: Mar 3 16:12:07.147 for 2d21h Paths: (3 available, best #1) Advertised to update-groups (with more than one peer): 0.1 Advertised to peers (in unique update groups): 10.4.101.1 Received by speaker 0 Local 0.0.0.0 from 0.0.0.0 (10.4.0.1) Origin IGP, metric 0, localpref 100, weight 32768, valid, local, best Received by speaker 0 2 3 4 10.4.101.1 from 10.4.101.1 (10.4.101.1) Origin IGP, localpref 100, valid, external Received by speaker 0 Local 10.4.101.2 from 10.4.101.2 (10.4.101.2) Origin IGP, localpref 100, valid, internal
Field |
Description |
---|---|
BGP router table entry |
Network that is being displayed. |
Versions |
List of the network versions in each BGP process. |
Process |
Name of the BGP process. |
bRIB/RIB |
Version of the network for sending to the RIB. You can compare this version with the bRIB/RIB version for the process (at the top of show bgp summary ) to verify whether the network has been sent to the RIB. |
SendTblVer |
Version of the network for advertising to neighbors. This can be compared with the neighbor version to determine whether the network has been advertised to a particular neighbor. |
Last Modified |
Timestamp when this route was last modified. |
Paths |
List of paths for the network (that is, routes to reach the network). The number of paths and the index of the best path are given. |
not advertised to any peer |
Best path was received with a NO_ADVERTISE community and is not advertised to any neighbor. |
not advertised to EBGP peer |
Best path was received with a NO_EXPORT community and is not advertised to any eBGP neighbor. |
not advertised outside local AS |
Best path was received with a LOCAL_AS community and is not advertised to peers outside the local AS. |
Advertisements of this net are suppressed by an aggregate |
Network is a more-specific prefix of a configured aggregate and has been suppressed. It is not advertised to any neighbors unless they have an unsuppress-map configured. |
Advertised to update-groups |
List of update-groups to which the net has been advertised. Update-groups that have only one peer are not listed here. |
Advertised to peers |
List of neighbors to which the net has been advertised to. Neighbors that are in one of the update-groups listed above are not listed separately. Only neighbors that are in unique update-groups are listed. |
Received by speaker 0 |
BGP process where the path originated. This is always “speaker 0” for standalone mode. It will be the speaker-id when BGP is in distributed mode. |
AS Path |
Autonomous system (AS) path that was received for the path. If the AS path is empty, then “Local” is displayed. This is the case for paths that are locally generated on this router or on a neighboring router within the same AS. |
aggregated by |
If the path is an aggregate, the router-id of the router that performed the aggregation. |
suppressed due to dampening |
Path has been suppressed due to the configured path dampening. |
history entry |
Path is withdrawn, but a copy is kept to store the dampening information. |
Received from a RR-client |
Path was received from a route reflector client. |
received-only |
If soft reconfiguration inbound is configured, the path was received but dropped by inbound policy, or was accepted and modified. In either event, the received-only value is a copy of the original, unmodified path. |
received & used |
If soft reconfiguration inbound is configured, the path was received and accepted by inbound policy, but not modified. |
stale |
Neighbor from which the path was received is down, and the path is kept and marked as stale to support graceful restart. |
<nexthop> from <neighbor> (<router-id>) |
Next hop for the path. If the next hop is known by a mechanism outside BGP (for example, for redistributed paths), then 0.0.0.0 is displayed. After the next hop, the neighbor from whom the path was received is displayed, along with the neighbor’s router-id. If the path was locally generated (for example, an aggregate or redistributed path), then 0.0.0.0 is displayed for the neighbor address. |
Origin |
IGP: the path originated from an IGP. EGP: the path originated from an EGP. incomplete: the origin of the path is unknown. |
metric |
MED value of the path. |
localpref |
Local preference value. This is used to determine the preferred exit point from the local autonomous system. It is propagated throughout the local autonomous system. |
weight |
Locally assigned weight (if not 0) of the path. Weight is used in choosing the preferred path to a route. It is not advertised to any neighbor. |
valid |
Path is valid and can be considered in the best-path calculation. |
redistributed |
Path is redistributed through a redistribute command. |
aggregated |
Path is a locally generated aggregate created due to an aggregate-address command. |
local |
Path is a local network source due to a network command. |
internal |
Path was received from an iBGP neighbor. |
external |
Path was received from an eBGP neighbor. |
atomic-aggregate |
Path was received with the atomic-aggregate flag set. Some path information has been removed through aggregation. |
best |
Path is the best path for the network and is used for routing and advertised to peers. |
multipath |
Path is a multipath and is installed into the RIB along with the best path. |
Community |
List of communities attached to the path. |
Extended community |
List of extended communities attached to the path. |
Originator |
Originator of the path within the AS Cluster list if the path is reflected. |
AS Cluster list |
List of RR clusters the path has passed through if the path is reflected |
Dampinfo |
Penalty and reuse information if the path is dampened. |
penalty |
Current penalty for the path. |
flapped |
Number of times the path has flapped and the time since the first flap. |
reuse in |
Time until the path is re-used (undampened). |
half life |
Configured half-life for the path. |
suppress value |
Penalty at which the path is suppressed. |
reuse value |
Penalty at which the path is re-used. |
Maximum suppress time |
Maximum length of time for which the path can be suppressed. |
The following is sample output from the show bgp command with the ip-address/prefix-length detail options:
RP/0/RP0/CPU0:router# show bgp 51.0.0.0/24 detail
Sat Mar 14 00:37:14.109 PST PDT
BGP routing table entry for 51.0.0.0/24
Versions:
Process bRIB/RIB SendTblVer
Speaker 3 3
Flags: 0x3e1000, label_retention: not enabled
Last Modified: Mar 13 19:32:17.976 for 05:04:56
Paths: (1 available, best #1)
Advertised to update-groups (with more than one peer):
0.3 0.4 0.7 0.8
Advertised to peers (in unique update groups):
201.48.20.1
Path #1: Received by speaker 0
Flags: 0x1000003
200 201
213.0.0.6 from 213.0.0.6 (200.200.3.1)
Origin IGP, localpref 100, valid, external, best
The following is sample output from the show bgp command with the additional paths received from:
BGP routing table entry for 51.0.1.0/24, Route Distinguisher: 2:1 Versions: Process bRIB/RIB SendTblVer Speaker 63 63 Flags: 0x040630f2 Last Modified: Nov 11 12:44:05.811 for 00:00:16 Paths: (3 available, best #2) Advertised to CE peers (in unique update groups): 10.51.0.10 Path #1: Received by speaker 0 Flags: 0x3 Not advertised to any peer 111 111 111 111 111 111 111 111 10.51.0.10 from 10.51.0.10 (11.11.11.11) Origin IGP, metric 0, localpref 100, valid, external Received Path ID 0, Local Path ID 0, version 0 Extended community: RT:55:1 Path #2: Received by speaker 0 Flags: 0x5060007 Advertised to CE peers (in unique update groups): 10.51.0.10 561 562 563 564 565 13.0.6.50 from 13.0.6.50 (13.0.6.50) Received Label 16 Origin IGP, localpref 100, valid, internal, best, group-best, import-candidate, imported Received Path ID 0, Local Path ID 1, version 63 Extended community: RT:55:1 Path #3: Received by speaker 0 Flags: 0x4060007 Not advertised to any peer 591 592 593 594 595 13.0.9.50 from 13.0.9.50 (13.0.9.50) Received Label 16 Origin IGP, localpref 100, valid, internal, backup, add-path, import-candidate, imported Received Path ID 0, Local Path ID 4, version 63 Extended community: RT:22:232 RT:55:1
RP/0/RP0/CPU0:router#show bgp vpnv4 unicast rd 11:111 100.16.11.0/24
BGP routing table entry for 100.16.11.0/24, Route Distinguisher: 11:111
Versions:
Process bRIB/RIB SendTblVer
Speaker 1834195 1834195
Paths: (2 available, best #1)
Advertised to update-groups (with more than one peer):
0.1
Path #1: Received by speaker 0
11
1:16.16.16.16 (metric 30) from 55.55.55.55 (16.16.16.16)
Received Label 19602
Origin incomplete, localpref 100, valid, internal, best, import-candidate, not-in-vrf, import suspect
Extended community: RT:11:11
Originator: 16.16.16.16, Cluster list: 55.55.55.55
Path #2: Received by speaker 0
11
1:16.16.16.16 (metric 30) from 88.88.88.88 (16.16.16.16)
Received Label 19602
Origin incomplete, localpref 100, valid, internal, not-in-vrf, import suspect
Extended community: RT:11:11
Originator: 16.16.16.16, Cluster list: 88.88.88.88
The show bgp command output displays 'import suspect' when potential import oscillation has been detected for the prefix. Import of such a prefix is not affected. However, import of the prefix can be dampened in future if the oscillation continues. If the oscillation stops during the next import run, the prefix will no longer be marked 'import supect'.
RP/0/RP0/CPU0:router#show bgp summary
BGP router identifier 10.1.1.2, local AS number 100
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0xe0000000 RD version: 5
BGP main routing table version 5
BGP scan interval 60 secs
BGP is operating in STANDALONE mode.
Process RcvTblVer RIBVer/RIBAckVer LabelVer ImportVer SendTblVer StandbyVer
Speaker 5 5/5 5 5 5 5
Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd
10.1.1.1 0 500 0 0 0 0 0 00:00:00 Idle
RP/0/RP0/CPU0:router#show bgp vpnv4 unicast rd 10.10.10.10:1 110.1.1.1/32 detail
BGP routing table entry for 110.1.1.1/32, Route Distinguisher: 10.10.10.10:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 1412487 1412487
Local Label: 137742 (no rewrite);
Flags: 0x04043001+0x00000000;
Last Modified: Jul 19 14:42:43.690 for 00:56:34
Paths: (2 available, best #1)
Advertised to peers (in unique update groups):
45.1.1.1
Path #1: Received by speaker 0
Flags: 0xd040003, import: 0x1f
Advertised to peers (in unique update groups):
45.1.1.1
101
10.5.1.2 from 10.5.1.2 (10.5.1.2)
Origin incomplete, localpref 100, valid, external, best, group-best, import-candidate
Received Path ID 0, Local Path ID 1, version 1412487
Extended community: RT:100:1
Path #2: Received by speaker 0
Flags: 0x324020005, import: 0x01
Not advertised to any peer
101
15.1.1.1 from 55.1.1.1 (15.1.1.1)
Received Label 137742
Origin incomplete, localpref 100, valid, internal, import-candidate, not-in-vrf, accept-own-self
Received Path ID 0, Local Path ID 0, version 0
Community: accept-own
Extended community: RT:100:1 RT:1000:1
Originator: 15.1.1.1, Cluster list: 55.1.1.1, 75.1.1.1, 45.1.1.1
RP/0/RP0/CPU0:router#show bgp vrf customer1 ipv4 uni 110.1.1.1/32
BGP routing table entry for 110.1.1.1/32, Route Distinguisher: 10.10.10.10:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 1412487 1412487
Local Label: 137742
Last Modified: Jul 19 14:42:43.690 for 01:01:22
Paths: (2 available, best #1)
Advertised to PE peers (in unique update groups):
45.1.1.1
Path #1: Received by speaker 0
Advertised to PE peers (in unique update groups):
45.1.1.1
101
10.5.1.2 from 10.5.1.2 (10.5.1.2)
Origin incomplete, localpref 100, valid, external, best, group-best, import-candidate
Received Path ID 0, Local Path ID 1, version 1412487
Extended community: RT:100:1
Path #2: Received by speaker 0
Not advertised to any peer
101
15.1.1.1 from 55.1.1.1 (15.1.1.1)
Received Label 137742
Origin incomplete, localpref 100, valid, internal, import-candidate, not-in-vrf, accept-own-self
Received Path ID 0, Local Path ID 0, version 0
Community: accept-own
Extended community: RT:100:1 RT:1000:1
Originator: 15.1.1.1, Cluster list: 55.1.1.1, 75.1.1.1, 45.1.1.1
RP/0/RP0/CPU0:router#show bgp vrf service1 ipv4 uni 110.1.1.1/32
BGP routing table entry for 110.1.1.1/32, Route Distinguisher: 11.11.11.11:1
Versions:
Process bRIB/RIB SendTblVer
Speaker 1412497 1412497
Last Modified: Jul 19 14:43:08.690 for 01:39:22
Paths: (1 available, best #1)
Advertised to CE peers (in unique update groups):
10.8.1.2
Path #1: Received by speaker 0
Advertised to CE peers (in unique update groups):
10.8.1.2
101
10.5.1.2 from 55.1.1.1 (15.1.1.1)
Origin incomplete, localpref 100, valid, internal, best, group-best, import-candidate, imported, accept-own
Received Path ID 0, Local Path ID 1, version 1412497
Community: accept-own
Extended community: RT:100:1 RT:1000:1
Originator: 15.1.1.1, Cluster list: 55.1.1.1, 75.1.1.1, 45.1.1.1
Field | Description |
---|---|
accept-own-self |
The Accept Own path in the customer VRF contains the "accept-own-self" keyword/flag. |
accept-own |
The Accept Own path contains the "accept-own" keyword/flag. |
Community:accept-own |
List of communities attached to the path: accept-own. |
Extended community |
List of extended communities attached to the path. |
Cluster list |
Router ID or cluster ID of all route reflectors through which the route has passed. |
The RD of the VPNvX net is not the same as any of the RDs configured for VRFs on the router.
The RD of the VPNvX net is the same as the RD configured for a specific VRF on the router, but the path is not imported to the specified VRF. For example, the route-targets attached to the path do not match any of the import route-target [as-number:nn | ip-address:nn] configured for VRF, vrf_1.
If the not-in-vrf net is set, it indicates that the path does not belong to the VRF.
RP/0/RP0/CPU0:router# show bgp ipv4 unicast 1.0.0.0/24
BGP routing table entry for 1.0.0.0/24
Versions:
Process bRIB/RIB SendTblVer
Speaker 90113 90113
Last Modified: Sep 6 04:46:03.650 for 00:14:19
Permanent Network
Paths: (2 available, best #2)
Advertised to peers (in unique update groups):
2.2.2.2
Path #1: Received by speaker 0
Advertised to peers (in unique update groups):
3.3.3.3
Local
0.0.0.0 from 0.0.0.0 (1.1.1.1)
Origin incomplete, metric 0, localpref 100, local, permanent-path
Received Path ID 0, Local Path ID 4, version 90113
Origin-AS validity: not-found
Path #2: Received by speaker 0
Advertised to peers (in unique update groups):
2.2.2.2
7813 7814
11.11.22.22 from 11.11.22.22 (192.1.1.1)
Origin EGP, localpref 100, valid, external, best, group-best, import-candidate
Received Path ID 0, Local Path ID 1, version 4
Origin-AS validity: not-found
To display Border Gateway Protocol (BGP) Monitoring Protocol (BMP) information, use the show bgp bmp command in XR EXEC mode.
show bgp bmp { server server-id [detail] | summary }
server server-id |
Displays information about BMP server as specified by the server-id variable. |
detail |
(Optional) Displays detailed BMP server information. |
summary |
Displays summary information about all the configured BMP servers. |
No default behavior or values
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read |
The following example shows sample output from the show bgp bmp command when the summary keyword is used:
RP/0/RP0/CPU0:router# show bgp bmp summary
ID Host Port State Time NBRs
1 10.0.101.1 16666 ESTAB 00:29:52 1
2 10.0.101.2 16667 ESTAB 00:29:52 0
3 fed0::1001 26666 ESTAB 00:29:52 0
4 fed0::1002 26667 ESTAB 00:29:52 0
5 10.0.101.1 16666 ESTAB 00:21:49 0
6 10.0.101.1 16666 ESTAB 00:29:52 0
7 fed0::1001 26666 ESTAB 00:29:52 0
8 fed0::1001 26666 ESTAB 00:29:52 0
The following example shows sample output from the show bgp bmp command when the server keyword, with server ID as 4, is used:
RP/0/RP0/CPU0:router# show bgp bmp server 4
BMP server 4
Host 10.0.101.1 Port 16666
Connected for 00:25:07
Precedence: internet
BGP neighbors: 1
VRF: - (0x60000000)
Update Source: 9.9.9.9 (Lo9)
Update Source Vrf ID: 0x60000000
Message Stats:
Total messages sent: 60
INITIATION: 1
TERMINATION: 0
STATS-REPORT: 0
PER-PEER messages: 59
Neighbor 20.0.101.11
Messages pending: 0
Messages sent: 59
PEER-UP: 1
PEER-DOWN: 0
ROUTE-MON: 58
To display address-family level update generation information, use the show bgp update out command in XR EXEC mode.
show bgp [ afi safi ] update out [ brief | detail ]
aft |
(Optional) Displays address-family identifier. |
saft |
(Optional) Displays subsequent address family identifier. |
brief |
(Optional) Displays brief information on process level update generation. |
detail |
(Optional) Displays detailed information on process level update generation. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read |
RP/0/RP0/CPU0:router#show bgp update out
Address-family "IPv4 Unicast"
Update generation status: Normal
Update OutQ: 0 bytes (0 messages)
AF update limit: 268435456 bytes (configured 268435456 bytes)
EBGP Sub-group update limit: 33554432 bytes (configured 33554432 bytes)
IBGP Sub-group update limit: 33554432 bytes (configured 33554432 bytes)
Main routing table version: 2
RIB version: 2
Minimum neighbor version: 2
AF Flags: 0x00000000
Update-groups: 1
Sub-groups: 1 (0 throttled)
Refresh sub-groups: 0 (0 throttled)
Filter-groups: 1
Neighbors: 3
History:
Update OutQ Hi: 300 bytes (1 messages)
Update OutQ Cumulative: 600 bytes (2 messages)
Update OutQ Discarded: 0 bytes (0 messages)
Update OutQ Cleared: 0 bytes (0 messages)
Last discarded from OutQ: --- (never)
Last cleared from OutQ: --- (never)
Update generation throttled 0 times, last event --- (never)
Update generation recovered 0 times, last event --- (never)
Update generation mem alloc failed 0 times, last event --- (never)
VRF "default", Address-family "IPv4 Unicast"
RD flags: 0x00000001
RD Version: 2
Table flags: 0x00000021
RIB version: 2
Update-groups: 1
Sub-groups: 1 (0 throttled)
Refresh sub-groups: 0 (0 throttled)
Filter-groups: 1
Neighbors: 3
RP/0/RSP0/CPU0:PE51_ASR-9010#
RP/0/RSP0/CPU0:PE51_ASR-9010#
RP/0/RSP0/CPU0:PE51_ASR-9010#show bgp update out filter-group
Thu Sep 13 01:43:48.183 DST
To display process level update inbound error-handling information, use the show bgp update in error processcommand in XR EXEC mode.
show bgp update in error process [ brief | detail ]
brief |
(Optional) Displays brief information on process level update generation. |
detail |
(Optional) Displays detailed information on process level update generation. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read |
RP/0/RP0/CPU0:router#show bgp update in error process
Basic Update error-handling:
EBGP: [Enabled]
IBGP: [Enabled]
Extended Update error-handling:
EBGP: [Disabled]
IBGP: [Disabled]
Malformed Update messages: 0
Neighbors that received malformed Update messages: 0
Last malformed Update received: --- (never)
To display update generation information at filter-group level, show bgp update out filter-group command in XR EXEC mode.
show bgp [ afi safi ] update out filter-group [fg-process-id] [ brief | detail ]
afi safi |
Specifies the address family and subsequent address family identifiers. |
fg-process-id |
Specifies the filter-group process ID in <x.y> format. Range is < 0-15>.<0-4294967295>. |
brief |
(Optional) Displays brief information on filter-group level update generation |
detail |
(Optional) Displays detailed information on filter-group level update generation. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read |
This example displays sample output from show bgp update out filter-group command:
To display process level update generation information, use the show bgp update out process command in XR EXEC mode.
show bgp update out process [ brief | detail ]
brief |
(Optional) Displays brief information on process level update generation. |
detail |
(Optional) Displays detailed information on process level update generation. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read |
RP/0/RP0/CPU0:router#show bgp update out process Wed Sep 12 08:26:04.308 DST Update generation status: Normal Update OutQ: 0 bytes (0 messages) Update limit: 536870912 bytes (configured 536870912 bytes) Update generation logging: [Disabled] Address-family Status Limit OutQ UG SG(Thr) SG-R(Thr) Nbrs IPv4 Unicast Normal 268435456 0 1 1(0) 0(0) 3 L2VPN VPLS Normal 268435456 0 1 1(0) 0(0) 3 History: Update OutQ Hi: 300 bytes (1 messages) Update OutQ Cumulative: 1200 bytes (4 messages) Update OutQ Discarded: 0 bytes (0 messages) Update OutQ Cleared: 0 bytes (0 messages) Last discarded from OutQ: --- (never) Last cleared from OutQ: --- (never) Update generation throttled 0 times, last event --- (never) Update generation recovered 0 times, last event --- (never) Update generation mem alloc failed 0 times, last event --- (never)
To display sub-group update generation information, use the show bgp update out sub-group command in XR EXEC mode.
show bgp [ afi safi ] update out [ update-group ug-index ] sub-group [sg-index] [ brief | detail ]
aft |
(Optional) Displays address-family identifier. |
saft |
(Optional) Displays subsequent address family identifier. |
brief |
(Optional) Displays brief information on process level update generation. |
detail |
(Optional) Displays detailed information on process level update generation. |
ug-index |
(Optional) Displays the update-group process ID in <x.y> format. |
sg-index |
(Optional) displays the sub-group process ID in <x.y> format. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read |
This example displays sample output from the show bgp update out sub-group command:
RP/0/RP0/CPU0:router#show bgp update out sub-group
VRF "default", Address-family "IPv4 Unicast"
Main routing table version: 2
RIB version: 2
SG UG Status Limit OutQ SG-R Nbrs Version ()
0.2 0.2 Normal 33554432 0 0 3 2 ()
RP/0/RSP0/CPU0:PE51_ASR-9010#
This table describes the significant fields shown in the display:
To display update-group update generation information, use the show bgp update out update-group command in XR EXEC mode.
show bgp [ afi safi ] update out update-group [ug-index] [ brief | detail ]
aft |
(Optional) Displays address-family identifier. |
saft |
(Optional) Displays subsequent address family identifier. |
brief |
(Optional) Displays brief information on process level update generation. |
detail |
(Optional) Displays detailed information on process level update generation. |
ug-index |
(Optional) Displays the update-group process ID in <x.y> format. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID | Operation |
---|---|
bgp |
read |
This example shows the significant fields on display form the show bgp update out update-group command:
RP/0/RP0/CPU0:router#show bgp update out sub-group
VRF "default", Address-family "IPv4 Unicast"
Main routing table version: 2
RIB version: 2
SG UG Status Limit OutQ SG-R Nbrs Version ()
0.2 0.2 Normal 33554432 0 0 3 2 ()
RP/0/RSP0/CPU0:PE51_ASR-9010#show bgp update ou update-group
Wed Sep 12 08:37:24.756 DST
VRF "default", Address-family "IPv4 Unicast"
UG OutQ SG(Thr) SG-R(Thr) FG Nbrs
0.2 0 1(0) 0(0) 1 3
To display VRF level update inbound error-handling information, use the show bgp vrf update in error command in XR EXEC mode.
show bgp [ vrf vrf-name ] update in error [ brief | detail ]
vrf vrf-name |
(Optional) Displays non-default VRF. |
brief |
(Optional) Displays brief information. |
detail |
(Optional) Displays detailed information. |
None
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
No specific guidelines impact the use of this command.
Task ID |
Operations |
---|---|
bgp |
read |
RP/0/RP0/CPU0:router#show bgp update in error
VRF "default"
Malformed Update messages: 0
Neighbors that received malformed Update messages: 0
Last malformed update received: --- (never)
To display advertisements for neighbors or a single neighbor, use the show bgp advertisedcommand in XR EXEC mode.
show bgp [ ipv4 { all | labeled-unicast | mdt | multicast | tunnel | unicast } ] advertised [ neighbor ip-address ] [ standby ] [ summary ]
show bgp [ ipv6 { all | labeled-unicast | multicast | unicast } ] advertised [ neighbor ip-address ] [ standby ] [ summary ]
show bgp [ all { all | labeled-unicast | multicast | tunnel | unicast } ] advertised [ neighbor ip-address ] [ standby ] [ summary ]
show bgp [ vpnv4 unicast [ rd rd-address ] ] advertised [ neighbor ip-address ] [ standby ] [ summary ]
show bgp [ vpnv6 unicast [ rd rd-address ] ] advertised [ neighbor ip-address ] [ standby ] [ summary ]
show bgp [ vrf { vrf-name | all } [ ipv4 | { labeled-unicast | unicast } | ipv6 unicast ] ] advertised [ neighbor ip-address ] [ standby ] [ summary ]
ipv4 |
(Optional) Specifies IP Version 4 address prefixes. |
unicast |
(Optional) Specifies unicast address prefixes. |
ipv6 |
(Optional) Specifies IP Version 6 address prefixes. |
If no address family or subaddress family is specified, the default address family and subaddress family specified using the set default-afi and set default-safi commands are used.
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
![]() Note | The set default-afi command is used to specify the default address family for the session, and the set default-safi command is used to specify the default subaddress family for the session. See the System Management Command Reference for Cisco NCS 5000 Series Routers for detailed information and syntax for the set default-afi and set default-safi commands. If you do not specify a default address family, the default address family is IPv4. If you do not specify a default subaddress family, the default subaddress family is unicast. |
BGP contains a separate routing table for each address family and subaddress family combination that is configured. The address family and subaddress family options specify the routing table to be examined. If the all keyword is specified for the address family or subaddress family, each matching routing table is examined in turn.
Use the show bgp advertised command to display the routes that have been advertised to peers or a specific peer. To preview advertisements that would be sent to a peer under a particular policy, even if the corresponding update messages have not been generated yet, use the show bgp policy command.
![]() Note | When you issue the show bgp advertised command, a route is not displayed in the output unless an advertisement for that route has already been sent (and not withdrawn). If an advertisement for the route has not yet been sent, the route is not displayed. |
Use the summary keyword to display a summary of the advertised routes. If you do not specify the summary keyword, the software displays detailed information about the advertised routes.
![]() Note | The show bgp advertised command does not display the application of any outbound policy in the route details it displays. Consequently, this command provides only an indication of whether a particular route has been advertised, rather than details of which attributes were advertised. Use the show bgp policy sent-advertisements command to display the attributes that are advertised. |
Task ID |
Operations |
---|---|
bgp |
read |
The following is sample output from the show bgp advertised command in XR EXEC mode:
RP/0/RP0/CPU0:router# show bgp advertised neighbor 10.0.101.4 summary
Network Next Hop From AS Path
1.1.1.0/24 10.0.101.1 10.0.101.1 2 3 222 333 444 555 i
1.1.2.0/24 10.0.101.1 10.0.101.1 3 4 5 6 7 i
1.1.3.0/24 10.0.101.1 10.0.101.1 77 88 33 44 55 99 99 99 i
1.1.4.0/24 10.0.101.1 10.0.101.1 2 5 6 7 8 i
1.1.7.0/24 10.0.101.1 10.0.101.1 3 5 i
1.1.8.0/24 10.0.101.1 10.0.101.1 77 88 99 99 99 i
Field |
Description |
---|---|
Network |
IP prefix and prefix length for a network. |
Next Hop |
IP address of the next system that is used when a packet is forwarded to the destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP route to this network. |
From |
IP address of the peer that advertised this route. |
AS Path |
AS path of the peer that advertised this route. |
Local |
Indicates the route originated on the local system. |
Local Aggregate |
Indicates the route is an aggregate created on the local system. |
Advertised to |
Indicates the peer to which this entry was advertised. This field is used in the output when displaying a summary of the advertisements to all neighbors. |
The following is sample output from the show bgp advertised command for detailed advertisement information:
RP/0/RP0/CPU0:router# show bgp advertised neighbor 172.72.77.1
172.16.0.0/24 is advertised to 172.72.77.1
Path info:
neighbor: Local neighbor router id: 172.74.84.1
valid redistributed best
Attributes after inbound policy was applied:
next hop: 0.0.0.0
MET ORG AS
origin: incomplete metric: 0
aspath:
10.52.0.0/16 is advertised to 172.72.77.1
Path info:
neighbor: Local Aggregate neighbor router id: 172.74.84.1
valid aggregated best
Attributes after inbound policy was applied:
next hop: 0.0.0.0
ORG AGG ATOM
origin: IGP aggregator: 172.74.84.1 (1)
aspath:
Field |
Description |
---|---|
is advertised to |
IP address of the peer to which this route has been advertised. If the route has been advertised to multiple peers, the information is shown separately for each peer. |
neighbor |
IP address of the peer that advertised this route, or one of the following: Local—Route originated on the local system. Local Aggregate—Route is an aggregate created on the local system. |
neighbor router id |
BGP identifier for the peer, or the local system if the route originated on the local system. |
Not advertised to any peer |
Indicates the no-advertise well-known community is associated with this route. Routes with this community are not advertised to any BGP peers. |
Not advertised to any EBGP peer |
Indicates the no-export well-known community is associated with this route. Routes with this community are not advertised to external BGP peers, even if those external peers are part of the same confederation as the local router. |
Not advertised outside the local AS |
Indicates the local-AS well-known community is associated with this route. Routes with this community value are not advertised outside the local autonomous system or confederation boundary. |
(Received from a RR-client) |
Path was received from a route reflector client. |
(received-only) |
This path is not used for routing purposes. It is used to support soft reconfiguration, and records the path attributes before inbound policy was applied to a path received from a peer. A path marked “received-only” indicates that either the path was dropped by inbound policy, or the path information was modified by inbound policy and a separate copy of the modified path is used for routing. |
(received & used) |
Indicates that the path is used both for soft reconfiguration and routing purposes. A path marked “received and used,” implies the path information was not modified by inbound policy. |
valid |
Path is valid. |
redistributed |
Path is locally sourced through redistribution. |
aggregated |
Path is locally sourced through aggregation. |
local |
Path is locally sourced through the network command. |
confed |
Path was received from a confederation peer. |
best |
Path is selected as best. |
multipath |
Path is one of multiple paths selected for load-sharing purposes. |
dampinfo |
Indicates dampening information: Penalty—Current penalty for this path. Flapped—Number of times the route has flapped. In—Time (hours:minutes:seconds) since the router noticed the first flap. Reuse in—Time (hours:minutes:seconds) after which the path is made available. This field is displayed only if the path is currently suppressed. |
Attributes after inbound policy was applied |
Displays attributes associated with the received route, after any inbound policy has been applied. AGG—Aggregator attribute is present. AS—AS path attribute is present. ATOM—Atomic aggregate attribute is present. COMM—Communities attribute is present. EXTCOMM—Extended communities attribute is present. LOCAL—Local preference attribute is present. MET—Multi Exit Discriminator (MED) attribute is present. next hop—IP address of the next system used when a packet is forwarded to the destination network. An entry of 0.0.0.0 indicates that the router has a non-BGP route to this network. ORG—Origin attribute is present. |
origin |
Origin of the path: IGP—Path originated from an Interior Gateway Protocol (IGP) and was sourced by BGP using a network or aggregate-address command. EGP—Path originated from an Exterior Gateway Protocol. incomplete—Origin of the path is not clear. For example, a route that is redistributed into BGP from an IGP. |
neighbor as |
First autonomous system (AS) number in the AS path. |
aggregator |
Indicates that the path was received with the aggregator attribute. The autonomous system number and router-id of the system that performed the aggregation are shown. |
metric |
Value of the interautonomous system metric, otherwise known as the MED metric. |
localpref |
Local preference value. This is used to determine the preferred exit point from the local autonomous system. It is propagated throughout the local autonomous system |
aspath |
AS path associated with the route. |
community |
Community attributes associated with the path. Community values are displayed in AA:NN format, except for the following well-known communities: Local-AS—Community with value 4294967043 or hex 0xFFFFFF03. Routes with this community value are not advertised outside the local autonomous system or confederation boundary. no-advertise—Community with value 4294967042 or hex 0xFFFFFF02. Routes with this community value are not advertised to any BGP peers. no-export—Community with value 4294967041 or hex 0xFFFFFF01. Routes with this community are not advertised to external BGP peers, even if those peers are in the same confederation with the local router. |
Extended community |
Extended community attributes associated with the path. For known extended community types, the following codes may be displayed: RT—Route target community SoO—Site of Origin community LB—Link Bandwidth community |
Originator |
Router ID of the originating router when route reflection is used. |
Cluster lists |
Router ID or cluster ID of all route reflectors through which the route has passed. |
To display information about Border Gateway Protocol (BGP) configuration for address family groups, use the show bgp af-group command in XR EXEC mode.
show bgp af-group group-name { configuration [ defaults ] [ nvgen ] | inheritance | users }
group-name |
Name of the address family group to display. |
configuration |
(Optional) Displays the effective configuration for the af-group, including any settings that have been inherited from af-groups used by this af-group. |
defaults |
(Optional) Displays all configuration settings, including any default settings. |
nvgen |
(Optional) Displays output in the format of show running-config output. If the defaults keyword is also specified, the output is not suitable for cutting and pasting into a configuration session. |
inheritance |
Displays the af-groups from which this af-group inherits configuration settings. |
users |
Displays the neighbors, neighbor groups, and af-groups that inherit configuration from this af-group. |
No default behavior or value
Release |
Modification |
---|---|
Release 6.0 |
This command was introduced. |
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 |
Operations |
---|---|
bgp |
read |
The following af-group configuration is used in the examples:
af-group group3 address-family ipv4 unicast remove-private-AS soft-reconfiguration inbound ! af-group group1 address-family ipv4 unicast use af-group group2 maximum-prefix 2500 75 warning-only default-originate soft-reconfiguration inbound disable ! af-group group2 address-family ipv4 unicast use af-group group3 send-community-ebgp send-extended-community-ebgp capability orf prefix both
The following is sample output from the show bgp af-group command with the configuration keyword in XR 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 configuration
af-group group1 address-family ipv4 unicast
capability 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:group2
The 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 users
IPv4 Unicast: a:group1
The following is sample output from the show bgp af-group command with the inheritance keyword. This example shows that the specified af-group group1 directly uses the group2 af-group, which in turn uses the group3 af-group:
RP/0/RSP0RP0/CPU0:router# show bgp af-group group1 inheritance IPv4 Unicast: a:group2 a:group3
Table 1 describes the significant fields shown in the display.
Field |
Description |
---|---|
[ ] |
Configures the command directly on the specified address family group. |
a: |
Indicates the name that follows is an address family group. |
n: |
Indicates the name that follows is a neighbor group. |
[dflt] |
Indicates the setting is not explicitly configured or inherited, and the default value for the setting is used. This field may be shown when the defaults keyword is specified. |
<not set> |
Indicates that the configuration is disabled by default. This field may be shown when the defaults keyword is specified. |
To display all existing attribute keys, use the show bgp attribute-keycommand in XR EXEC mode.
show bgp { ipv4 | ipv6 | all | vpnv4 unicast | }
attribute-key [ standby ]
ipv4 |
(Optional) Specifies IP Version 4 address prefixes. |
unicast |
(Optional) Specifies unicast address prefixes. |
all |
(Optional) For address family, specifies prefixes for all address families. |
ipv6 |
(Optional) Specifies IP Version 6 address prefixes. |
ipv4 { unicast | < |