-
Cisco IOS XR Routing Command Reference, Release 3.6
-
Preface
-
BGP Commands on Cisco IOS XR Software
-
EIGRP Commands on Cisco IOS XR Software
-
IS-IS Commands on Cisco IOS XR Software
-
OSPF Commands on Cisco IOS XR Software
-
OSPFv3 Commands on Cisco IOS XR Software
-
RIB Commands on Cisco IOS XR Software
-
RIP Commands on Cisco IOS XR Software
-
Routing Policy Commands on Cisco IOS XR Software
-
Static Routing Commands on Cisco IOS XR Software
-
Index
-
Table Of Contents
BGP Commands on Cisco IOS XR Software
bgp auto-policy-soft-reset disable
bgp bestpath cost-community ignore
bgp bestpath med missing-as-worst
bgp client-to-client reflection disable
bgp fast-external-fallover disable
bgp graceful-restart graceful-reset
bgp graceful-restart purge-time
bgp graceful-restart restart-time
bgp graceful-restart stalepath-time
bgp log neighbor changes disable
clear bgp nexthop performance-statistics
clear bgp nexthop registration
clear bgp performance-statistics
default-information originate (BGP)
show bgp truncated-communities
BGP Commands on Cisco IOS XR Software
This chapter describes the commands used to configure and monitor Border Gateway Protocol (BGP) for IP Version 4 (IPv4), IP Version 6 (IPv6), Virtual Private Network Version 4 (VPNv4), Virtual Private Network Version 6 (VPNv6), and multicast distribution tree (MDT) routing sessions.
For detailed information about BGP concepts, configuration tasks, and examples, see Implementing BGP on Cisco IOS XR Software in Cisco IOS XR Routing Configuration Guide.
address-family (BGP)
To enter various address family configuration modes while configuring Border Gateway Protocol (BGP), use the address-family command in an appropriate configuration mode. To disable support for an address family, use the no form of this command.
address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
no address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
Syntax Description
Defaults
An address family must be explicitly configured in the router configuration mode for the address family to be active in BGP. Similarly, an address family must be configured under the neighbor for the BGP session to be established for that address family. An address family must be configured in router configuration mode before it can be configured under a neighbor.
Command Modes
Router configuration
Neighbor configuration
Neighbor group configuration
VRF configuration
VRF neighbor configuration (IPv4 address families)Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the address-family command to enter various address family configuration modes while configuring BGP routing sessions. When you enter the address-family command from router configuration mode, you enable the address family and enter global address family configuration mode.
The IPv4 unicast address family must be configured in router configuration mode before configuring the IPv4 labeled-unicast address family for a neighbor in neighbor configuration mode. The IPv6 unicast address family must be configured in router configuration mode before configuring the IPv6 labeled-unicast address family for a neighbor in neighbor configuration mode.
When you enter the address-family command from neighbor configuration mode, you activate the address family on the neighbor and enter neighbor address family configuration mode.
IPv4 neighbor sessions support IPv4 unicast, multicast, labeled-unicast, and VPNv4 unicast address families. IPv6 neighbor sessions support IPv6 unicast and multicast address families.
The IPv4 unicast address family must be configured in router configuration mode before configuring the IPv4 labeled-unicast address family for a neighbor in neighbor configuration mode. The IPv6 unicast address family must be configured in router configuration mode before configuring the IPv6 labeled-unicast address family for a neighbor in neighbor configuration mode. See Table 2.
Task ID
Examples
The following example shows how to place the router in global address family configuration mode for the IPv4 address family:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)#The following example shows how to activate IPv4 multicast for neighbor 10.0.0.1 and place the router in neighbor address family configuration mode for the IPv4 multicast address family:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 1RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-af)# exitRP/0/RP0/CPU0:router(config-bgp)# neighbor 10.0.0.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 1RP/0/RP0/CPU0:router(config-bgp-nbr)# address-family ipv4 multicastRP/0/RP0/CPU0:router(config-bgp-nbr-af)#The following example shows how to place the router in global address family configuration mode for the IPv4 address family:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# router bgp 12RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 tunnelRP/0/RP0/CPU0:router(config-bgp-af)#advertisement-interval
To set the minimum interval between the sending of Border Gateway Protocol (BGP) routing updates, use the advertisement-interval command in an appropriate configuration mode. To remove the advertisement-interval command from the configuration file and restore the system to its default interval values, use the no form of this command.
advertisement-interval seconds
no advertisement-interval [seconds]
Syntax Description
Defaults
Default minimum interval:
For internal BGP (iBGP) peers is 0 seconds
For external BGP (eBGP) peers is 30 seconds
For customer edge (CE) peers is 0 secondsCommand Modes
Neighbor configuration
Neighbor group configuration
Session group configuration
VRF neighbor configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If this command configures a neighbor group or session group, all neighbors using the group inherit the configuration. Values of commands configured specifically for a neighbor override inherited values.
Task ID
Examples
The following example shows how to set the minimum time between sending BGP routing updates to 10 seconds:
RP/0/RP0/CPU0:router(config)# router bgp 5RP/0/RP0/CPU0:router(config-bgp)# neighbor 10.1.1.1RP/0/RP0/CPU0:router(config-bgp-nbr)# remote-as 100RP/0/RP0/CPU0:router(config-bgp-nbr)# advertisement-interval 10Related Commands
Creates a neighbor group and enters neighbor group configuration mode.
Creates a session group and enters session group configuration mode.
af-group
To create an address family group for Border Gateway Protocol (BGP) neighbors and enter address family group configuration mode, use the af-group command in router configuration mode. To remove an address family group, use the no form of this command.
af-group af-group-name address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
no af-group af-group-name address-family {ipv4 unicast | ipv4 multicast | ipv4 labeled-unicast | ipv4 tunnel | ipv4 mdt | ipv6 unicast | ipv6 multicast | ipv6 labeled-unicast | vpnv4 unicast | vpnv6 unicast}
Syntax Description
Defaults
No BGP address family group is configured.
Command Modes
Router configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the af-group command to group address family-specific neighbor commands within an IPv4 or IPv6 address family. Neighbors that have address family configuration are able to use the address family group. Further, neighbors inherit the configuration parameters of the entire address family group.
You cannot define two address family groups with the same name in different address families.
Task ID
Examples
The following example shows how to create address family group group1 and enter address family group configuration mode for IPv4 unicast. Group1 contains the next-hop-self feature, which is inherited by neighbors that use address family group1.
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# af-group group1 address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# next-hop-selfRelated Commands
aggregate-address
To create an aggregate entry in a Border Gateway Protocol (BGP) routing table, use the aggregate-address command in an appropriate configuration mode. To remove the aggregate-address command from the configuration file and restore the system to its default condition, use the no form of this command.
aggregate-address address/mask-length [as-set] [as-confed-set] [summary-only] [route-policy route-policy-name]
no aggregate-address address/mask-length [as-set] [as-confed-set] [summary-only] [route-policy route-policy-name]
Syntax Description
Defaults
When you do not specify this command, no aggregate entry is created in the BGP routing table.
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
You can implement aggregate routing in BGP either by redistributing an aggregate route into BGP using the network command or the aggregate-address command.
Use the aggregate-address command without optional arguments to create an aggregate entry in the BGP routing table if any more-specific BGP routes are available that fall in the specified range. The aggregate route is advertised as coming from your autonomous system and has the atomic aggregate attribute set to show that information might be missing. (By default, the atomic aggregate attribute is set unless you specify the as-set keyword.)
Use of the as-set keyword creates an aggregate entry using the same rules that the command follows without this keyword. However, the advertised path for this route is an AS_SET, a set of all autonomous systems contained in all paths that are being summarized.
Do not use this form of the aggregate-address command when aggregating many paths because this route must be continually withdrawn and updated as autonomous system path reachability information for the summarized routes changes.
Use the as-confed-set keyword to create an AS_CONFED_SET in the autonomous system path of the aggregate from any confederation segments in the paths being summarized. This keyword takes effect only if the as-set keyword is also specified.
Use of the summary-only keyword creates an aggregate entry (for example, 10.0.0.0/8) but suppresses advertisements of more-specific routes to all neighbors. If you want to suppress only advertisements to certain neighbors, use the route-policy (BGP) command in neighbor address family configuration mode with caution. If a more-specific route leaks out, all BGP speakers (the local router) prefer that route over the less-specific aggregate you generate (using longest-match routing).
Use the route-policy keyword to specify a routing policy for the aggregate entry. The route-policy keyword is used to select which more-specific information to base the aggregate entry on and which more-specific information to suppress. You can also use the keyword to modify the attributes of the aggregate entry.
Task ID
Examples
The following example shows how to create an aggregate address. The path advertised for this route is an autonomous system set consisting of all elements contained in all paths that are being summarized.
RP/0/RP0/CPU0:router(config)# router bgp 100RP/0/RP0/CPU0:router(config-bgp)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-af)# aggregate-address 10.0.0.0/8 as-setRelated Commands
allocate-label
To allocate Multiprotocol Label Switching (MPLS) labels for specific IPv4 unicast or VPN routing and forwarding (VRF) IPv4 unicast routes so that the BGP router can send labels with BGP routes to a neighboring router configured for labeled-unicast sessions, use the allocate-label command in the appropriate configuration mode. To restore the system to its default condition, use the no form of this command.
allocate-label {route-policy route-policy-name | all}
no allocate-label {route-policy route-policy-name | all}
Syntax Description
Defaults
No default behavior or values
Command Modes
IPv4 address family configuration
IPv6 address family configuration
VRF IPv4 address family configuration
VRF IPv6 address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the allocate-label command with a route policy to trigger BGP to allocate labels for all or a filtered set of global IPv4 routes (as dictated by the route policy). The command enables autonomous system border routers (ASBRs) that have labeled IPv4 unicast sessions to exchange Multiprotocol Label Switching (MPLS) labels with the IPv4 routes to the other autonomous system (AS) in Layer 3 Virtual Private Network (L3VPN) inter-AS deployments.
Note
The allocate-label all command is functionally equivalent to the allocate-label route-policy route-policy-name command when the route policy is a pass-all policy.
See Cisco IOS XR Multiprotocol Label Switching Configuration Guide for information on using the allocate-label command for L3VPN inter-AS deployments and carrier-supporting-carrier IPv4 BGP label distribution.
Task ID
Examples
The following example shows how to enable allocating labels for IPv4 routes:
RP/0/0/CPU0:router(config)# router bgp 6RP/0/0/CPU0:router(config-bgp)# address family ipv4 unicastRP/0/0/CPU0:router(config-bgp-af)# allocate-label route-policy policy_Aallowas-in
To allow an AS path with the provider edge (PE) autonomous system number (ASN) a specified number of times, use the allowas-in command in an appropriate configuration mode. To restore the system to its default condition, use the no form of this command.
allowas-in [as-occurrence-number]
no allowas-in [as-occurrence-number]
Syntax Description
Defaults
No default behavior or values
Command Modes
Address family group configuration
Neighbor address family configurationCommand History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Hub and spoke VPN networks require looping back of routing information to the hub PE through the hub customer edge (CE). See Cisco IOS XR Multiprotocol Label Switching Configuration Guide for information on hub and spoke VPN networks. This looping back, in addition to the presence of the PE ASN, causes the looped-back information to be dropped by the hub PE.
The allowas-in command prevents the looped-back information from being dropped by replacing the neighbor autonomous system number (ASN) with the PE ASN in the AS path. This allows the VPN customer to see a specified number of occurrences of the PE ASN in the AS path.
Task ID
Examples
The following example shows how to allow five occurrences of the PE ASN:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# af-group group_1 address-family vpnv4 unicastRP/0/RP0/CPU0:router(config-bgp-afgrp)# allowas-in 5as-override
To configure a provider edge (PE) router to override the autonomous system number (ASN) of a site with the ASN of a provider, use the as-override command in VRF neighbor address family configuration mode. To restore the system to its default condition, use the no form of this command.
as-override [disable]
no as-override [disable]
Syntax Description
Defaults
Automatic override of the ASN is disabled.
Command Modes
VRF neighbor address family configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the as-override command in conjunction with the site-of-origin (SoO) feature, identifying the site where a route originated, and preventing routing loops between routers within a VPN.
Task ID
Examples
The following example shows how to configure an ASN override:
RP/0/RP0/CPU0:router(config)# router bgp 6RP/0/RP0/CPU0:router(config-bgp)# vrf vrf_ARP/0/RP0/CPU0:router(config-bgp-vrf)# neighbor 192.168.70.24RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# remote-as 10RP/0/RP0/CPU0:router(config-bgp-vrf-nbr)# address-family ipv4 unicastRP/0/RP0/CPU0:router(config-bgp-vrf-nbr-af)# as-overrideRelated Commands
bfd
To specify a bidirectional forwarding detection (BFD) multiplier and minimum-interval arguments per neighbor, use the bfd command in neighbor address family independent configuration mode. To return to the system defaults, use the no form of this command.
Previous to this enhancement, BFD could be configured only in global scope in BGP. This change makes available two new command-line arguments under neighbor address family independent configuration:
bfd multiplier (minimum-interval) value
no bfd multiplier (minimum-interval) value
Syntax Description
multiplier value
Specifies the BFD session's multiplier value for the neighbor.
minimum-interval value
Specifies the BFD session's minimum-interval value for the neighbor.
Defaults
No default per neighbor parameters are set.
Command Modes
Neighbor address family independent configuration
Command History
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
If the minimum interval is changed using the bfd minimum-interval command, the new parameter updates all affected BFD sessions under the command mode in which the minimum interval was changed.
If the multiplier is changed using the bfd multiplier command, the new parameter is used to update only the BFD sessions associated with the affected neighbor gets affected.
The assumption is that when BFD fast-detect is enabled under neighbor address family independent configuration, the values for the multiplier and minimum-interval values are always derived from the per-neighbor values if they are configured; otherwise, they are to be taken from the global BGP configuration mode. In the event that this has not been explicitly stated, then these values are taken to be the default values. Also, the bfd arguments can be configured under neighbor-group and session-group and the inheritance adheres to the standard way of BGP configuration inheritance.
Accordingly, there are four cases in which bfd-fast detect is enabled.
This is shown in table below where the BFD value is either multiplier or minimum-interval. Local indicates per NBR value, global is the BGP global value.
Yes
Yes
BFD value (local)
Yes
No
BFD value (global)
No
Yes
BFD value (local)
No
No
BFD value (default)
Examples
The following example shows how to specify the BFD session's multiplier value for the neighbor:
RP/0/0/CPU0:router # conf tRP/0/0/CPU0:router(config)# router bgp 65000RP/0/0/CPU0:router(config-bgp-nbrgrp)# neighbor 3.3.3.2RP/0/0/CPU0:router(config-bgp-nbr)# bfd minimum-interval 311RP/0/0/CPU0:router(config-bgp-nbr)# bfd multiplier 7RP/0/0/CPU0:router(config-bgp-nbr)# neighbor 5.5.5.2RP/0/0/CPU0:router(config-bgp-nbr)# bfd minimum-interval 318RP/0/0/CPU0:router(config-bgp-nbr)# bfd multiplier 4RP/0/0/CPU0:router(config-bgp-nbr)# vrf oneRP/0/0/CPU0:router(config-bgp-vrf)# neighbor 3.12.1.2RP/0/0/CPU0:router(config-bgp-vrf-nbr)# bfd minimum-interval 119RP/0/0/CPU0:router(config-bgp-vrf-nbr)# bfd multiplier 10RP/0/0/CPU0:router(config-bgp-vrf-nbr)# commitRP/0/0/CPU0:router# show bfd sessionInterface Dest Addr Local det time(int*mult) StateEcho Async-------------------- --------------- ---------------- ---------------- ---------Gi0/2/0/2 3.3.3.2 2177ms(311ms*7) 14s(2s*7) UPGi0/2/0/2.1 3.12.1.2 1190ms(119ms*10) 20s(2s*10) UPPO0/3/0/6 5.5.5.2 1272ms(318ms*4) 8s(2s*4) UPRP/0/0/CPU0:router# show bfd session detailI/f: GigabitEthernet0/2/0/2, Location: 0/2/CPU0, dest: 3.3.3.2, src: 3.3.3.1State: UP for 0d:0h:4m:44s, number of times UP: 1Received parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 7, diag: NoneMy discr: 524295, your discr: 524296, state UP, D/F/P/C/A: 0/0/0/1/0Transmitted parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 7, diag: NoneMy discr: 524296, your discr: 524295, state UP, D/F/P/C/A: 0/0/0/1/0Timer Values:Local negotiated async tx interval: 2 sRemote negotiated async tx interval: 2 sDesired echo tx interval: 311 ms, local negotiated echo tx interval: 311 msEcho detection time: 2177 ms(311 ms*7), async detection time: 14 s(2 s*7)Local Stats:Intervals between async packets:Tx: Number of intervals=100, min=1664 ms, max=2001 ms, avg=1838 msLast packet transmitted 313 ms agoRx: Number of intervals=100, min=1662 ms, max=2 s, avg=1828 msLast packet received 1615 ms agoIntervals between echo packets:Tx: Number of intervals=100, min=181 ms, max=462 ms, avg=229 msLast packet transmitted 289 ms agoRx: Number of intervals=100, min=178 ms, max=461 ms, avg=229 msLast packet received 287 ms agoLatency of echo packets (time between tx and rx):Number of packets: 100, min=0 us, max=4 ms, avg=860 usSession owner information:Client Desired interval Multiplier---------------- -------------------- --------------bgp-0 311 ms 7I/f: GigabitEthernet0/2/0/2.1, Location: 0/2/CPU0, dest: 3.12.1.2, src: 3.12.1.1State: UP for 0d:0h:4m:44s, number of times UP: 1Received parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 10, diag: NoneMy discr: 524296, your discr: 524295, state UP, D/F/P/C/A: 0/0/0/1/0Transmitted parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 10, diag: NoneMy discr: 524295, your discr: 524296, state UP, D/F/P/C/A: 0/0/0/1/0Timer Values:Local negotiated async tx interval: 2 sRemote negotiated async tx interval: 2 sDesired echo tx interval: 119 ms, local negotiated echo tx interval: 119 msEcho detection time: 1190 ms(119 ms*10), async detection time: 20 s(2 s*10)Local Stats:Intervals between async packets:Tx: Number of intervals=100, min=1664 ms, max=2001 ms, avg=1838 msLast packet transmitted 314 ms agoRx: Number of intervals=100, min=1662 ms, max=2 s, avg=1828 msLast packet received 1616 ms agoIntervals between echo packets:Tx: Number of intervals=100, min=120 ms, max=223 ms, avg=125 msLast packet transmitted 112 ms agoRx: Number of intervals=100, min=119 ms, max=223 ms, avg=125 msLast packet received 110 ms agoLatency of echo packets (time between tx and rx):Number of packets: 100, min=0 us, max=2 ms, avg=850 usSession owner information:Client Desired interval Multiplier---------------- -------------------- --------------bgp-0 119 ms 10I/f: POS0/3/0/6, Location: 0/3/CPU0, dest: 5.5.5.2, src: 5.5.5.1State: UP for 0d:0h:4m:50s, number of times UP: 1Received parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 4, diag: NoneMy discr: 786436, your discr: 786433, state UP, D/F/P/C/A: 0/0/0/1/0Transmitted parameters:Version: 1, desired tx interval: 2 s, required rx interval: 2 sRequired echo rx interval: 1 ms, multiplier: 4, diag: NoneMy discr: 786433, your discr: 786436, state UP, D/F/P/C/A: 0/0/0/1/0Timer Values:Local negotiated async tx interval: 2 sRemote negotiated async tx interval: 2 sDesired echo tx interval: 318 ms, local negotiated echo tx interval: 318 msEcho detection time: 1272 ms(318 ms*4), async detection time: 8 s(2 s*4)Local Stats:Intervals between async packets:Tx: Number of intervals=100, min=1663 ms, max=2 s, avg=1821 msLast packet transmitted 1740 ms agoRx: Number of intervals=100, min=1663 ms, max=2001 ms, avg=1832 msLast packet received 160 ms agoIntervals between echo packets:Tx: Number of intervals=100, min=181 ms, max=484 ms, avg=232 msLast packet transmitted 44 ms agoRx: Number of intervals=100, min=179 ms, max=484 ms, avg=232 msLast packet received 41 ms agoLatency of echo packets (time between tx and rx):Number of packets: 100, min=0 us, max=3 ms, avg=540 usSession owner information:Client Desired interval Multiplier---------------- -------------------- --------------bgp-0 318 ms 4RP/0/0/CPU0:router# show bgp nei 3.3.3.2BGP neighbor is 3.3.3.2Remote AS 500, local AS 65000, external linkRemote router ID 16.0.0.1BGP state = Established, up for 00:05:01BFD enabled (session up): mininterval: 311 multiplier: 7Last read 00:00:56, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and received4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedReceived 8 messages, 0 notifications, 0 in queueSent 9 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 30 secondsFor Address Family: IPv4 UnicastBGP neighbor version 2Update group: 0.2AF-dependant capabilities:Graceful Restart Capability advertised and receivedNeighbor preserved the forwarding state during latest restartLocal restart time is 120, RIB purge time is 600 secondsMaximum stalepath time is 360 secondsRemote Restart time is 120 secondsRoute refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all1 accepted prefixes, 1 are bestpathsPrefix advertised 1, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was not received during read-only modeConnections established 1; dropped 0Last reset 00:06:58, due to User clear requested (CEASE notification sent - administrative reset)Time since last notification sent to neighbor: 00:06:58Error Code: administrative resetNotification data sent:NoneRP/0/0/CPU0:router# show bgp nei 5.5.5.2BGP neighbor is 5.5.5.2Remote AS 500, local AS 65000, external linkRemote router ID 16.0.0.1BGP state = Established, up for 00:05:04BFD enabled (session up): mininterval: 318 multiplier: 4Last read 00:00:58, hold time is 180, keepalive interval is 60 secondsPrecedence: internetNeighbor capabilities:Route refresh: advertised and received4-byte AS: advertised and receivedAddress family IPv4 Unicast: advertised and receivedReceived 8 messages, 0 notifications, 0 in queueSent 9 messages, 1 notifications, 0 in queueMinimum time between advertisement runs is 30 secondsFor Address Family: IPv4 UnicastBGP neighbor version 2Update group: 0.2AF-dependant capabilities:Graceful Restart Capability advertised and receivedNeighbor preserved the forwarding state during latest restartLocal restart time is 120, RIB purge time is 600 secondsMaximum stalepath time is 360 secondsRemote Restart time is 120 secondsRoute refresh request: received 0, sent 0Policy for incoming advertisements is pass-allPolicy for outgoing advertisements is pass-all1 accepted prefixes, 0 are bestpathsPrefix advertised 1, suppressed 0, withdrawn 0, maximum limit 524288Threshold for warning message 75%An EoR was not received during read-only modeConnections established 1; dropped 0Last reset 00:07:01, due to User clear requested (CEASE notification sent - administrative reset)Time since last notification sent to neighbor: 00:07:01Error Code: administrative resetNotification data sent:NoneRP/0/0/CPU0:router# show bgp vrf one nei 3.12.1.2BGP neighbor is 3.12.1.2, vrf oneRemote AS 500, local AS 65000, external linkRemote router ID 16.0.0.1BGP state = Established, up for 00:05:06
