Monitoring BGP
Use the show commands in this section to monitor BGP activity.
 | Note: The E120 router and E320 router output for monitor and show commands is identical to output from other E Series routers, except that the E120 and E320 router output also includes information about the adapter identifier in the interface specifier (slot/adapter/port). |
Use the baseline ip bgp command to set the baseline on all BGP statistics.
You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. See JUNOSe System Basics Configuration Guide, for details.
Use the debug ip bgp command to get information about problems with BGP or the network.
baseline ip bgp
- Use to set the baseline on all BGP statistics as the current values.
- For example, if you issue the baseline ip bgp command, all the current values of BGP statistics become the baseline values. If the current value of the Total message sent parameter is 105, and the value goes up to 120 messages, the new value is displayed as 15.
- Example host1#baseline ip bgp
- There is no no version.
- See baseline ip bgp.
debug ip bgp
- Use to display information about BGP logs for inbound or outbound events, or both.
- Example host1#debug ip bgp
- There is no no version, but you can use the undebug ip bgp command to disable display of information previously enabled with the debug ip bgp command.
- See debug ip bgp.
default-fields peer
- Use to specify fields that are displayed by default by a subsequently issued show ip bgp summary command.
- Use the intro keyword to enable the display of introductory information about BGP attributes.
- The order in which you specify the fields has no effect on the order in which they are displayed.
- Example
host1:pe2(config-router)#default-fields peer remote-as state messages-received messages-sent up-down-time host1:pe2#show ip bgp summary Messages Messages Neighbor AS State Up/down time Sent Received 1.1.1.1 100 Established 00:07:55 94 92
- Use the no version to remove fields from the output of subsequently issued show ip bgp summary commands.
- See default-fields peer.
default-fields route
- Use to specify fields that are displayed by default by any subsequently issued show ip bgp command that displays BGP routes.
- Use the intro keyword to enable the display of introductory information about BGP attributes.
- This command does not affect the output of the show ip bgp summary command.
- The order in which you specify the fields has no effect on the order in which they are displayed.
- Example
host1:pe2(config-router)#default-fields route intro next-hop med loc-pref weight as-path host1:pe2#show ip bgp vpnv4 all Local BGP identifier 2.2.2.2, local AS 100 6 routes (388 bytes) 7 destinations (560 bytes) of which 0 have a route 0 routes selected for route table installation 6 path attribute entries (936 bytes) Local-RIB version 74. FIB version 74.
Prefix Next-hop MED LocPrf Weight AS-path 99.99.99.11/32 1.1.1.1 1 100 0 65011 99.99.99.12/32 1.1.1.1 0 100 0 empty 99.99.99.13/32 1.1.1.1 2 100 0 empty 99.99.99.21/32 21.21.21.2 1 0 65021 99.99.99.22/32 22.22.22.2 0 32768 empty 99.99.99.23/32 23.23.23.2 2 32768 empty
- Use the no version to remove fields from the output of subsequently issued show ip bgp commands that displays BGP routes.
- See default-fields route.
show ip as-path-access-list
- Use to display access lists.
- Example
host1#show ip as-path-access-list AS Path Access List 10: permit [200-220] permit ^114 permit ^117.*225$ AS Path Access List 11: deny .* AS Path Access List 20: deny [1100-1250] permit .*
- See show ip as-path-access-list.
show ip bgp
show bgp ipv6
- Use to display the BGP routing table.
- If you specify an IP address, displays the route that best matches the specified IP address.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- Field descriptions
- Learned from peer—Peer from which route was learned
- Next hop IP address—IP address of the next router that is used when a packet is forwarded to the destination network
- AS path—AS path through which this route has been advertised
- Aggregator AS number—AS number of the AS that aggregated this route
- Aggregate IP address—IP address of the router that aggregated this route
- Origin—Origin of the route
- MED—Multiexit discriminator for the route
- LocPrf—Local preference for the route
- Weight—Weight of the route
- Communities—Community number associated with the route
- Originator ID—Router ID of the router in the local AS that originated the route
- Cluster ID list—List of cluster IDs through which the route has been advertised
- Stale—Route has gone stale due to peer restart
- Example 1—Displays information about routes in the
IPv6 multicast address family
host1# show bgp ipv6 multicast Local BGP identifier 10.13.13.13, local AS 400 4 routes (160 bytes) 4 destinations (288 bytes) of which 4 have a route 4 routes selected for route table installation 3 path attribute entries (456 bytes) Local-RIB version 31. FIB version 31. Status codes: > best, * invalid, s suppressed, d dampened, r rejected, a auto-summarized Prefix Peer Next-hop MED LocPrf Weight Origin ::103.103.103.0/120 103.103.103.3 ::103.103.103.3 0 0 inc. > 3ffe:0:0:1::/64 11.11.11.11 ::101.101.101.1 0 100 0 inc. > 3ffe:0:0:3::/64 103.103.103.3 ::103.103.103.3 0 0 inc. > 3ffe:0:1:1::/64 12.12.12.12 ::102.102.102.2 0 100 0 inc. - Example 2—Displays route information for prefix
10.88.88.1/32
host1:pe1#show ip bgp 10.88.88.1 BGP route information for prefix 10.88.88.1/32 Network route (best route Advertised to both internal and external peers Address Family Identifier (AFI) is ip-v4 Subsequent Address Family Identifier (SAFI) is unicast Next hop IP address is 0.0.0.0 (metric 2) Multi-exit discriminator is 1 Local preference is not present Weight is 32768 Origin is IGP AS path is empty Extended communities empty - Example 3—Displays information about IPv6 prefix
2001:0430::1/128
host1#show bgp ipv6 2001:0430::1/128 BGP route information for prefix 2001:1::1/128 Received route learned from internal peer 2.2.2.2 (best route) Route placed in IP forwarding table Best to advertise to external peers Address Family Identifier (AFI) is ip-v6 Subsequent Address Family Identifier (SAFI) is unicast MPLS in-label is none MPLS out-label is 17 Next hop IP address is ::ffff:2.2.2.2 (metric 3) Multi-exit discriminator is 0 Local preference is 100 Weight is 0 Origin is IGP AS path is 65021 - Example 4—Displays information about next hop routers
for VRF PE 11 in the IPv4 VPN address family
host1:pe1#show ip bgp vpnv4 vrf pe11 next-hops Indirect next-hop 11.11.11.2 Resolution in IP route table of VR pe11 Reachable (metric 0) IP indirect next-hop index 35 Direct next-hop ATM2/0.11 (11.11.11.2) Resolution in IP tunnel-route table of VR pe11 Not reachable Reference count is 1Indirect next-hop 2.2.2.2 Resolution in IP route table of VR pe1 IP indirect next-hop index 123 Reachable (metric 100) Direct next-hop POS4/0 (10.10.10.1) POS4/1 (12.12.12.1)
Resolution in IP tunnel-route table of VR pe1 MPLS indirect next-hop index 578 Reachable (metric 100) Direct next-hop Push 23, POS4/0 (10.10.10.1) Push 43, POS4/1 (12.12.12.1)
Reference count is 1
- Example 5—Displays information about routes in the
route-target address family
host1# show ip bgp route-target signaling Local BGP identifier 13.13.13.13, local AS 100 4 routes (240 bytes) 3 destinations (228 bytes) of which 3 have a route 3 routes selected for route tables installation 0 unicast/multicast routes selected for route table installation 0 unicast/multicast tunnel-usable routes selected for route table installation 0 tunnel-only routes selected for tunnel-route table installation 10 path attribute entries (1520 bytes) Local-RIB version 19. FIB version 19. Status codes: > best, * invalid, s suppressed, d dampened, r rejected, a auto-summarized Prefix Peer Next-hop MED LocPrf Weight Origin > 0:0:0/0 12.12.12.12 12.12.12.12 100 0 IGP > 100:100:1/96 11.11.11.11 11.11.11.11 100 0 IGP 100:100:1/96 14.14.14.14 14.14.14.14 100 0 IGP > 100:100:2/96 11.11.11.11 11.11.11.11 100 0 IGP - Example 6—Displays information for routes in the
route-target address family corresponding to the specified RT-MEM-NLRI
host1#show ip bgp route-target signaling 100:100:1/96 BGP route information for prefix 100:100:1/96 Received route learned from internal peer 11.11.11.11 (best route) Route not placed in IP forwarding table Best to advertise to both internal and external peers Address Family Identifier (AFI) is ip-v4 Subsequent Address Family Identifier (SAFI) is route-target-signaling Next hop IP address is 11.11.11.11 (metric 0) Multi-exit discriminator is not present Local preference is 100 Weight is 0 Origin is IGP AS path is empty Received route learned from internal peer 14.14.14.14 Route not placed in IP forwarding table Do not advertise to any peers Address Family Identifier (AFI) is ip-v4 Subsequent Address Family Identifier (SAFI) is route-target-signaling Next hop IP address is 14.14.14.14 (metric 0) Multi-exit discriminator is not present Local preference is 100 Weight is 0 Origin is IGP AS path is empty - Example 7—Displays for network routes in the route-target
address family
host1:pe1#show ip bgp route-target signaling network Prefix Weight Route-map Backdoor 102:111:34/96 No 1111111111:23:1/96 No
host1:pe1#show ip bgp route-target signaling network 102:111:34 Prefix Weight Route-map Backdoor 102:111:34/96 No
- Example 8—Error message generated when a prefix
less than 32 or greater than 96 is specified for the RT-MEM-NLRI
host1#show ip bgp route-target signaling 100:100:1/31 ^ % Invalid route-target membership NLRI
- You can use the field options to display filtered information about a specified network or all networks in the BGP routing table. Only the fields that you specify are displayed, except that the Prefix field is always displayed.
- The stale field option shows which routes are stale due to peer restart.
- Examples
host1:5#show ip bgp fields peer next-hop next-hop-cost
Prefix Peer Next-hop Next-hop-cost 11.11.11.11/32 3.3.3.3 3.3.3.3 Unreachable 11.11.11.11/32 4.4.4.4 4.4.4.4 Unreachable 22.22.22.22/32 3.3.3.3 3.3.3.3 Unreachable 22.22.22.22/32 4.4.4.4 4.4.4.4 Unreachable 33.33.33.33/32 3.3.3.3 3.3.3.3 Unreachable 44.44.44.44/32 4.4.4.4 4.4.4.4 Unreachable 55.55.55.55/32 0.0.0.0 0.0.0.0 0 66.66.66.66/32 6.6.6.6 6.6.6.6 Unreachable 77.77.77.77/32 57.57.57.7 57.57.57.7 1 88.88.88.88/32 57.57.57.7 57.57.57.7 1
host1:pe1#show ip bgp fields best peer next-hop stale Prefix Stale Peer Next-hop > 10.22.22.1/32 stale 10.12.12.2 10.12.12.2 > 10.22.22.2/32 stale 10.12.12.2 10.12.12.2 > 10.22.22.3/32 stale 10.12.12.2 10.12.12.2 > 10.33.33.1/32 10.13.13.3 10.13.13.3 > 10.33.33.2/32 10.13.13.3 10.13.13.3 > 10.33.33.3/32 10.13.13.3 10.13.13.3
- You can use the default-fields route command to specify default fields to be displayed by subsequently issued show ip bgp commands.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option.
- Field descriptions for introductory fields displayed only
when the intro keyword has been issued
- Local BGP identifier—BGP router ID of the local router
- routes—Total number of routes stored in the BGP routing table and amount of memory consumed by routes. If several peers have advertised a route to the same prefix, all routes are included in this count.
- destinations—Number of routes to unique prefixes stored in the BGP routing table and amount of memory consumed by routes. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- routes selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table, plus prefixes for which there are currently no routes but which have had to be withdrawn from peers to which these prefixes may been previously advertised
- unicast/multicast routes selected for route table installation—Number of unicast routes in the BGP routing table that have been inserted into the IP routing table that are also available for use in the multicast view of the IP routing table
- unicast/multicast tunnel-usable routes selected for route table installation—Number of unicast and multicast routes in the BGP routing table that have been inserted into the IP routing table that are also available for use in the IP tunnel routing table
- tunnel-only routes selected for tunnel-route table installation—Number of routes in the BGP routing table that have been inserted into the IP tunnel routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Local-RIB version—Number that is increased by one each time a route in that RIB is added, removed or modified.
- FIB version—Number that is increased by one each time BGP updates the routes in the IP routing table based on changes in the local RIB. The FIB version matches the local-RIB version when BGP has finished updating the routes in the IP route table. The FIB version is less than the local-RIB version when BGP is still in the process of updating the IP routing table.
- Statistics baseline set—Timestamp indicating when the statistics baseline was last set
- Example
host1#show ip bgp 0.0.0.0 /0 fields intro Local BGP identifier 192.168.254.79, local AS 6730 201058 routes (12063492 bytes) 201540 destinations (15317040 bytes) of which 201058 have a route 193909 routes selected for route tables installation 0 unicast/multicast routes selected for route table installation 0 unicast/multicast tunnel-usable routes selected for route table installation 0 tunnel-only routes selected for tunnel-route table installation 35097 path attribute entries (5334744 bytes) Local-RIB version 20969483. FIB version 20969483. Statistics baseline set WED JUL 12 2006 10:31:53 METDST ...
- See show ip bgp.
- See show bgp ipv6.
show ip bgp advertised-routes
show bgp ipv6 advertised-routes
- Use to display the routes in the specified neighbor’s or peer group’s Adj-RIBs-Out table.
- For peers, the attributes displayed are those associated with the route before the application of any outbound policy.
- For peer groups, the attributes displayed are those associated with the route after the application of any outbound policy; that is, the actual advertised attributes.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- You must first enable storage of routes to the Adj-RIBs-Out tables with the no rib-out disable command or the no neighbor rib-out disable command. Otherwise, this command returns an error message.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local BGP identifier—BGP router ID of the local router
- routes—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct destinations—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- routes selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator for the route
- LocPrf—Local preference for the route
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show ip bgp neighbors 5.72.116.1 advertised-routes Local BGP identifier 2.2.2.2, local AS 2222 0 routes (0 bytes used), 0 distinct destinations (0 bytes used) 0 routes selected for route table installation 0 path attribute entries (0 bytes used)
Status codes: > best, * invalid, s suppressed, d dampened, r rejected
Prefix Peer Next-hop MED LocPrf Weight Origin > 0.0.0.0/0 5.72.116.1 5.72.1.1 0 IGP > 10.10.0.87/32 5.72.116.1 5.72.1.1 0 inc. > 13.13.13.13/32 5.72.116.1 5.72.1.1 0 IGP > 33.0.0.0/16 0.0.0.0 5.72.1.1 1 32768 inc. > 33.0.0.0/24 0.0.0.0 5.72.1.1 1 32768 inc. > 44.44.0.0/16 5.72.116.1 5.72.1.1 0 inc.
- See show ip bgp advertised-routes.
- See show bgp ipv6 advertised-routes.
show ip bgp aggregate-address
show bgp ipv6 aggregate-address
- Use to display information about aggregate addresses.
- Field descriptions
- Prefix—Prefix of the aggregate address
- AS set—ASs in the AS-set path
- Summary only—Displays a summary of aggregate address information
- Attribute map—Displays the attribute maps for aggregate addresses
- Advertise map—Displays the advertise maps for aggregate addresses
- Example
host1# show bgp ipv6 aggregate-address Prefix AS set Summ only Attribute map Advertise map Suppress map 3ffe::/48 No No None None None
- See show ip bgp aggregate-address.
- See show bgp ipv6 aggregate-address.
show ip bgp cidr-only
- Use to display information about routes that have nonnatural network masks.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local BGP identifier—BGP router ID of the local router
- routes—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct destinations—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- routes selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator for the route
- LocPrf—Local preference for the route
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show ip bgp cidr-only Local BGP identifier 111.111.111.111, local AS 444 0 routes (0 bytes used), 0 distinct destinations (0 bytes used) 0 routes selected for route table installation 0 path attribute entries (0 bytes used)
Status codes: > best, * invalid, s suppressed, d dampened, r rejected
Prefix Peer Next-hop MED LocPrf Weight Origin 33.0.0.0/24 5.72.1.1 5.72.1.1 1 0 inc. > 44.44.0.0/24 0.0.0.0 192.168.1.1 1 32768 inc.
- See show ip bgp cidr-only.
show ip bgp community
show bgp ipv6 community
- Use to display all routes that are members of the specified BGP community. Does not accept regular expressions.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- Specify the community number in AA:NN format:
- AA—Number that identifies the autonomous system
- NN—Number that identifies the community within the autonomous system
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local router ID—BGP router ID of the local router
- local AS—Local autonomous system number
- paths—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct prefixes—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- paths selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the route table entry
- Peer—IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator
- CalPrf—Calculated preference
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show ip bgp community 999:999 Local router ID 192.168.1.153, local AS 100 40845 paths, 40845 distinct prefixes (2940840 bytes used) 40845 paths selected for route table installation 13651 path attribute entries (1864908 bytes used)
Prefix Peer Next-hop MED CalPrf Weight Origin > 24.0.0.0/12 10.5.0.48 10.5.0.48 100 100 IGP > 24.4.252.0/22 10.5.0.48 10.5.0.48 100 100 IGP > 24.6.0.0/23 10.5.0.48 10.5.0.48 100 100 IGP > 24.6.11.0/24 10.5.0.48 10.5.0.48 100 100 IGP
- See show ip bgp community.
- See show bgp ipv6 community.
show ip bgp community-list
show bgp ipv6 community-list
- Use to display all routes that are members of communities on the specified BGP community list.
- Accepts regular expressions.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local router ID—BGP router ID of the local router
- local AS—Local autonomous system number
- paths—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct prefixes—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- paths selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Communities—Community number in AA:NN format:
- AA—Number that identifies the autonomous system
- NN—Number that identifies the community within the autonomous system
- Example
host1#show ip bgp community-list 1 fields peer communities Local router ID 192.168.1.153, local AS 100 72077 paths, 72077 distinct prefixes (5189544 bytes used) 72077 paths selected for route table installation 21627 path attribute entries (2957324 bytes used)
Prefix Peer Communities 3.0.0.0/8 10.5.0.48 777:777 888:888 4.0.0.0/8 10.5.0.48 777:777 888:888 4.17.106.0/24 10.5.0.48 777:777 888:888 4.17.115.0/24 10.5.0.48 777:777 888:888 6.0.0.0/8 10.5.0.48 777:777 888:888 9.2.0.0/16 10.5.0.48 777:777 888:888 9.20.0.0/17 10.5.0.48 777:777 888:888 12.0.0.0/8 10.5.0.48 777:777 888:888
- See show ip bgp community-list.
- Seeshow bgp ipv6 community-list.
show ip bgp dampened-paths
show bgp ipv6 dampened-paths
- Use to display information about dampened routes.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local router ID—IP address of the local router
- local AS—Number of the local AS
- Route flap dampening—Status of route flap dampening (enabled or disabled)
- Decay half-life—Time (in minutes) after which a penalty is decreased. After the route has been assigned a penalty, the penalty is decreased by half after the half-life period (which is 15 minutes by default).
- Cutoff threshold—Value of the penalty for a flapping route below which the route is unsuppressed
- Reuse threshold—Time (in hours:minutes:seconds) after which the path will be made available
- Maximum hold-down time—Interval, in seconds, after not receiving a keepalive message that the software declares a peer dead
- route flap history—Status of route flap history for route paths
- Prefix—The prefix for the IP address
- Peer—IP address of the BGP peer
- Status—Status of route dampening of the route path
- Figure of Merit—A measure of the route's stability. Higher values indicate more recent route flap activity or less stability.
- Time until Reuse/Remove—Time until the route is either reused (if currently suppressed) or its history entry is removed (if currently available)
- Example
host1#show ip bgp dampened-paths Local router ID 192.168.1.218, local AS 100 Route flap dampening is enabled Decay half-life is 10 minutes while reachable, 20 minutes while unreachable Cuttoff threshold is 2000, reuse threshold is 750 Maximum hold-down time is 20 minutes 60 paths have active route flap histories (4560 bytes used) 11 paths are suppressed Figure Time until Prefix Peer Status of Merit Reuse/Remove 24.31.128.0/19 10.2.1.48 Suppressed/Reachable 2681 00:17:00 24.93.128.0/19 10.2.1.48 Suppressed/Reachable 2681 00:17:00 24.95.0.0/19 10.2.1.48 Suppressed/Reachable 2681 00:17:00 128.192.0.0/16 10.2.1.48 Available 1997 00:15:08 148.161.0.0/16 10.2.1.48 Available 1997 00:15:10 164.81.0.0/16 10.2.1.48 Available 1997 00:15:11 192.29.60.0/24 10.2.1.48 Available 1997 00:15:12 192.58.228.0/24 10.2.1.48 Available 1997 00:15:15 192.88.8.0/24 10.2.1.48 Available 1997 00:15:17 192.107.253.0/24 10.2.1.48 Suppressed/Unreachable 4331 00:19:42 192.195.44.0/24 10.2.1.48 Suppressed/Reachable 2923 00:19:15 192.195.49.0/24 10.2.1.48 Suppressed/Reachable 2923 00:19:15 192.195.50.0/24 10.2.1.48 Suppressed/Reachable 2923 00:19:15 192.197.150.0/24 10.2.1.48 Available 1997 00:15:25 192.222.89.0/24 10.2.1.48 Suppressed/Unreachable 2788 00:19:42 204.17.195.0/24 10.2.1.48 Suppressed/Reachable 2923 00:17:20 204.52.186.0/24 10.2.1.48 Available 1997 00:15:26 204.68.178.0/24 10.2.1.48 Available 1000 00:19:38 204.101.0.0/16 10.2.1.48 Available 1997 00:15:29 204.128.227.0/24 10.2.1.48 Suppressed/Reachable 2923 00:17:16 204.146.24.0/22 10.2.1.48 Available 1997 00:15:30 204.146.24.0/24 10.2.1.48 Available 1997 00:15:30
- See show ip bgp dampened-paths.
- See show bgp ipv6 dampened-paths.
show ip bgp filter-list
show bgp ipv6 filter-list
- Use to display all routes whose AS-path matches the specified AS-path access list.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local router ID—BGP router ID of the local router
- local AS—Local autonomous system number
- paths—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct prefixes—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- paths selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator
- CalPrf—Calculated preference
- Weight—Assigned path weight
- AS path—Autonomous system path
- Example
host1#show ip bgp filter-list 1 Local router ID 192.168.1.153, local AS 100 72080 paths, 72080 distinct prefixes (5189760 bytes used) 72080 paths selected for route table installation 21667 path attribute entries (2962828 bytes used)
Prefix Next-hop MED CalPrf Weight AS-path > 6.0.0.0/8 10.5.0.48 100 100 11488 701 7018 7170 > 12.0.0.0/8 10.5.0.48 100 100 11488 701 1740 7018 > 12.1.248.0/24 10.5.0.48 100 100 11488 701 7018 13391 > 12.2.6.0/24 10.5.0.48 100 100 11488 701 7018 11101 > 12.2.7.0/24 10.5.0.48 100 100 11488 701 7018 11101 > 12.2.76.0/24 10.5.0.48 100 100 11488 701 7018 11812 > 12.2.99.0/24 10.5.0.48 100 100 11488 701 7018 10656 > 12.2.109.0/24 10.5.0.48 100 100 11488 701 7018 10656 > 12.2.169.0/24 10.5.0.48 100 100 11488 701 7018 11806 > 12.4.114.0/24 10.5.0.48 100 100 11488 701 7018 14065 > 12.4.119.0/24 10.5.0.48 100 100 11488 701 7018 14065 > 12.4.175.0/24 10.5.0.48 100 100 11488 701 7018 11895 > 12.4.196.0/22 10.5.0.48 100 100 11488 701 7018 12163 > 12.5.48.0/21 10.5.0.48 100 100 11488 701 7018 12163 > 12.5.164.0/24 10.5.0.48 100 100 11488 701 7018 11134 > 12.6.42.0/23 10.5.0.48 100 100 11488 701 7018 11090
- See show ip bgp filter-list.
- See show bgp ipv6 filter-list.
show ip bgp flap-statistics
show bgp ipv6 flap-statistics
- Use to display information about flap statistics.
- Field descriptions
- Local BGP identifier—BGP router ID of the local router where route flap dampening is enabled
- local AS—Local autonomous system number
- Route flap dampening—Status of route flap dampening (enabled or disabled)
- Default decay half-life—Time (in minutes) after which a penalty is decreased. After the route has been assigned a penalty, the penalty is decreased by half after the half-life period (which is 15 minutes by default).
- Default cutoff threshold—Value of the penalty for a flapping route below which the route is unsuppressed
- Default reuse threshold—Time in minutes after which the path will be made available
- Default maximum hold-down time—Interval, in seconds, after not receiving a keepalive message that the software declares a peer dead
- route flap history—Status of route flap history for route paths
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Status—Status of route dampening of the route path
- Figure of Merit—Measure of the route's stability. Higher values indicate more recent route flap activity or less stability.
- Time until Reuse/Remove—Time in hours:minutes:seconds until the route is either reused (if currently suppressed) or its history entry is removed (if currently available)
- Example
host1#show ip bgp flap-statistics Local BGP identifier 192.168.1.232, local AS 100 Route flap dampening is enabled Default decay half-life is 15 minutes Default cutoff threshold is 2000, default reuse threshold is 750 Default maximum hold-down time is 60 minutes 307 paths have active route flap histories (27016 bytes used) 5 paths are suppressed Figure Time until Prefix Peer Status of Merit Reuse/Remove 24.201.0.0/18 192.168.1.158 Available 925 00:58:23 24.201.64.0/18 192.168.1.158 Available 925 00:58:23 52.128.224.0/19 192.168.1.158 Available 750 00:54:12 61.8.0.0/19 192.168.1.158 Available 993 00:59:53 61.8.30.0/24 192.168.1.158 Available 993 00:59:53 62.229.73.0/24 192.168.1.158 Unreachable 925 00:58:23 63.69.150.0/24 192.168.1.158 Available 750 00:54:12
- See show ip bgp flap-statistics.
- See show bgp ipv6 flap-statistics.
show ip bgp inconsistent-as
show bgp ipv6 inconsistent-as
- Use to display information about routes that have inconsistent AS-paths.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local BGP identifier—BGP router ID of the local router
- local AS—Local autonomous system number
- routes—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct destinations—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- routes selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator for the route
- LocPrf—Local preference for the route
- Weight—Assigned path weight
- Origin—Origin of the route
- AS-path—AS-path through which this route bas been advertised
- Example
host1#show ip bgp inconsistent-as Local BGP identifier 192.168.1.10, local AS 123 0 routes (0 bytes used), 0 distinct destinations (0 bytes used) 0 routes selected for route table installation 0 path attribute entries (0 bytes used)
Status codes: > best, * invalid, s suppressed, d dampened, r rejected
Prefix Next-hop MED LocPrf Weight AS-path > 4.0.0.0/8 0.0.0.0 1 32768 empty 4.0.0.0/8 192.168.1.1 0 11488 701 1
- See show ip bgp inconsistent-as.
- See show bgp ipv6 inconsistent-as.
show ip bgp
show bgp ipv6
- Use to display all routes with a prefix that is equal to or more specific than the specified prefix.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgpshow ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local router ID—BGP router ID of the local router
- local AS—Local autonomous system number
- paths—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct prefixes—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- paths selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator
- CalPrf—Calculated preference
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show ip bgp 12.2.0.0 255.255.0.0 longer-prefixes Local router ID 192.168.1.153, local AS 100 72074 paths, 72074 distinct prefixes (5189328 bytes used) 72074 paths selected for route table installation 21685 path attribute entries (2965327 bytes used)
Prefix Peer Next-hop MED CalPrf Weight Origin > 12.2.6.0/24 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.7.0/24 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.76.0/24 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.88.0/22 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.97.0/24 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.99.0/24 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.109.0/24 10.5.0.48 10.5.0.48 100 100 IGP > 12.2.169.0/24 10.5.0.48 10.5.0.48 100 100 IGP
- See show ip bgp.
- See show bgp ipv6.
show ip bgp neighbors
show bgp ipv6 neighbors
- Use to display information about BGP neighbors.
- Field descriptions
- BGP neighbor ID—BGP identifier of the BGP neighbor
- remote AS—Remote AS of the BGP neighbor
- Description—Textual description of the BGP neighbor
- Member of peer group—Name of the peer group of which this BGP neighbor is a member
- Remote router ID—Router ID of the remote router
- negotiated BGP version—BGP version being used to communicate with the neighbor
- Administrative status—Desired state of the peer connection
- Connection state—Current state of the BGP connection
- Connection has been established—Time that TCP connection was established
- Reason for last reset—Reason for last reset of the BGP session
- TCP error code—TCP connection error type
- Default originate—Status of default originate (enabled or disabled)
- EBGP multi-hop—Status of EBGP multihop (enabled or disabled)
- IBGP single-hop—Status of IBGP single hop (enabled or disabled)
- Next hop self—Status of next-hop self (enabled or disabled)
- Route reflector status—Identifies the neighbor as a route-reflector client
- Neighbor weight—Weight of routes from the BGP neighbor
- Incoming update distribute list—Distribute list for incoming routes, if configured
- Outgoing update distribute list—Distribute list for outgoing routes, if configured
- Incoming update filter list—Update filter list for incoming routes, if configured
- Outgoing update filter list—Update filter list for outgoing route, if configured
- Weight filter list—Weight filter list for routes, if configured
- Incoming route map—Incoming route map, if configured
- Outgoing route map—Outgoing route map, if configured
- Connect retry interval—Time between a BGP peer’s attempts to reestablish a connection to the neighbor
- Minimum route advertisement interval—Minimum time between route advertisements
- Minimum AS origination interval—Minimum time between advertisement of changes within the speaker’s AS
- Configured keep-alive interval—Frequency of keep-alive messages generated
- Negotiated keepalive interval—Negotiated frequency of keep-alive messages generated
- Configured hold time—Configured maximum time allowed between received messages
- Negotiated hold time—Negotiated maximum time allowed between received messages
- Configured update source IP address—IP address used when sending update messages
- Local IP address—Local IP address used for TCP communication to this peer
- Local port—Local TCP port number used for TCP communication to this peer
- Remote IP address—Remote IP address used for TCP communication to this peer
- Remote port—Remote IP address used for TCP communication to this peer
- Total messages sent—Total BGP messages sent to this neighbor
- Total messages received—Total BGP messages received from this neighbor
- Total update messages sent—Total BGP update messages sent to this neighbor
- Total update messages received—Total BGP update messages received from this neighbor
- Time since last update message was received—Time since last BGP update message was received from this neighbor
- Address Family dependent capabilities—Lists type of ORF send and receive capability per address family and whether it is advertised (configured) or received
- Maximum number of ORF entries—Limit of ORF entries that will be accepted from the neighbor
- Capability advertisement—Lists whether the specific capability (capabilities option, deprecated dynamic capability negotiation, dynamic capability negotiation, multiprotocol extensions, route refresh, route refresh (Cisco proprietary), four octet AS numbers, and graceful restart) has been sent, received, or both
- Multi-protocol extensions negotiation—Lists the relevant address family and whether it has been sent, received, or used
- BFD—Status of BFD configuration, enabled, enabled but not supported because the peer is an IBGP neighbor a multihop EBGP neighbor, or disabled
- BFD session—Type and address of peer to which BFD session is established
- Minimum transmit interval—Desired interval between BFD packets transmitted to members of peer group
- Minimum receive interval—Desired interval between BFD packets received from members of peer group
- Multiplier—Number of BFD packets that can be missed before declaring BFD session down
- Negotiated detection time—Interval between BFD packets negotiated by peers
- Advertise-map—Name of route map that specifies routes to be advertised when routes in conditional route maps are matched
- Condition-map—Name of route map that specifies routes to be matched by routes in the BGP routing table
- Sequence—Position of the specified advertise route map in a list of advertise route maps configured for a particular peer within the same address-family. A lower sequence number has a higher priority; that route map is processed before one with a higher sequence number.
- Status—Status of the routes specified by the route map, advertise (route map condition has been met) or withdraw (route map condition has not been met; regardless of this status, the specified routes might be governed by another route map with a lower sequence number and actually advertised or not according to that map
- Example
host1#show ip bgp neighbors BGP neighbor ID 10.2.1.48, remote AS 11488 (external peer) Remote router ID is 172.31.1.48, negotiated BGP version is 4 Administrative status is Start, connection state is Established Reason for last reset was tcp connection error TCP error code 60 (Connection timed out) Connection has been established 1 time, up for 0 17:42:31 Options: Default originate is disabled EBGP multi-hop is enabled IBGP single-hop is disabled Next hop self is disabled seconds Policy: Neighbor weight is 100 Timers: Connect retry interval is 120 seconds Minimum route advertisement interval is 30 seconds Minimum AS origination interval is 10 seconds Configured keep-alive interval is 30 seconds, negotiated 30 seconds Configured hold time is 90 seconds, negotiated 90 TCP connection: Local IP address is 192.168.1.218, local port is 1024 Remote IP address is 10.2.1.48, remote port is 179 Statistics: Total of 4100 messages sent, 44913 messages received 2053 update messages sent, 42785 update messages received 0 00:00:17 since last update message was received - Fields relevant to multiprotocol extensions:
Multi-protocol extensions negotiation: ip-v4 unicast: sent, received, used ip-v6 unicast-labeled: sent, received, used - For the graceful restart capability, additional information
is presented.
- Fields concerning graceful restart attributes that apply
to peers as a whole (for all address families):
Graceful restart negotiation: Sent restart time is 120 seconds Sent restart state bit is zero (we are not restarting) Received restart time is 120 seconds Received restart state bit is zero (peer is not restarting) Maximum time for keeping stale paths is 360 seconds - Fields concerning attributes that apply to peers a particular
address family:
Peer is capable of preserving forwarding stat(3) Peer preserved forwarding state during last restart We have received an end-of-rib marker from the peer We have sent an end-of-rib marker to the peer
- Fields relevant if the peer is currently restarting:
Graceful restart waiting for the session to come back up Restart-time advertised by the peer is 120 seconds Remaining time for the peer to come back up is 117 seconds Remaining time for keeping stale routes from the peer is 357 seconds - Fields relevant during reconvergence after the peer has
restarted:
Graceful restart negotiation: Sent restart time is 120 seconds Sent restart state bit is zero (we are not restarting) Received restart time is 120 seconds Received restart state bit is zero (peer is not restarting) Maximum time for keeping stale paths is 300 seconds Remaining time for keeping stale routes from the peer is 297 seconds
- Fields concerning graceful restart attributes that apply
to peers as a whole (for all address families):
- For BFD, additional information is presented.
- Fields relevant to BFD when BFD is not configured:
BFD is disabled
- Fields relevant to BFD when BFD is configured for an IBGP
peer:
BFD is enabled but not supported (IBGP neighbor)
- Fields relevant to BFD when BFD is configured for a multihop
EBGP peer:
BFD is enabled but not supported (multi-hop EBGP neighbor)
- Fields relevant to BFD when BFD is configured but the
BGP session is not established:
BFD is enabled: Single-hop IPv4 BFD session to 1.2.3.4 Minimum transmit interval is 300 ms Minimum receive interval is 300 ms Multiplier is 3 Waiting for BGP to become established before initiating BFD session - Fields relevant to BFD when BFD is configured, the BGP
session is established, but the BFD protocol session is not up:
BFD is enabled: Single-hop IPv4 BFD session to 1.2.3.4 Minimum transmit interval is 300 ms Minimum receive interval is 300 ms Multiplier is 3 BFD session is down - Fields relevant to BFD when BFD is configured, the BGP
session is established, and the BFD protocol session is up:
BFD is enabled: Single-hop IPv4 BFD session to 1.2.3.4 Minimum transmit interval is 300 ms Minimum receive interval is 300 ms Multiplier is 3 BFD session is up for 00:00:50 Negotiated detection time is 900 ms
- Fields relevant to BFD when BFD is not configured:
- Fields relevant to conditional advertisement:
Advertise-map is advertisetoR1 Condition-map: trigger1 Sequence: 5 Status: Withdraw Advertise-map is alternatetoR1 Condition-map: trigger2 Sequence: 10 Status: Advertise - See show ip bgp neighbors.
- See show bgp ipv6 neighbors.
show ip bgp neighbors dampened-routes
show bgp ipv6 neighbors dampened-routes
- Use to display information about routes with a dampening history for the specified BGP neighbor.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local BGP identifier—BGP router ID of the local router
- routes—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.
- distinct destinations—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- routes selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator for the route
- LocPrf—Local preference for the route
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show ip bgp neighbors 192.168.1.158 dampened-routes Local BGP identifier 192.168.1.232, local AS 100 120 routes (5760 bytes used), 94 distinct destinations (9024 bytes used) 67 routes selected for route table installation 23 path attribute entries (3450 bytes used)
Status codes: > best, * invalid, s suppressed, d dampened, r rejected Prefix Peer Next-hop MED LocPrf Weight Origin d12.8.12.0/24 192.168.1.158 192.168.1.1 0 IGP d24.48.12.0/24 192.168.1.158 192.168.1.1 0 IGP d24.72.12.0/24 192.168.1.158 192.168.1.1 0 inc. d24.116.12.0/23 192.168.1.158 192.168.1.1 0 IGP d24.143.12.0/24 192.168.1.158 192.168.1.1 0 IGP d24.154.12.0/24 192.168.1.158 192.168.1.1 0 inc. d24.216.12.0/24 192.168.1.158 192.168.1.1 0 IGP d24.240.12.0/24 192.168.1.158 192.168.1.1 0 IGP d24.244.12.0/22 192.168.1.158 192.168.1.1 0 IGP d24.246.12.0/22 192.168.1.158 192.168.1.1 0 IGP d61.0.12.0/24 192.168.1.158 192.168.1.1 0 IGP d61.11.12.0/24 192.168.1.158 192.168.1.1 0 IGP d62.74.12.0/22 192.168.1.158 192.168.1.1 0 IGP d62.76.12.0/22 192.168.1.158 192.168.1.1 0 IGP d63.65.12.0/24 192.168.1.158 192.168.1.1 0 inc. d63.73.12.0/24 192.168.1.158 192.168.1.1 0 IGP - See show ip bgp neighbors dampened-routes.
- See show bgp ipv6 neighbors dampened-routes.
show ip bgp neighbors paths
show bgp ipv6 neighbors paths
- Use to display path information for the specified BGP neighbor.
- This command displays only the most common path attributes. BGP internally maintains additional attributes that are not displayed—for example, the MED, local preference, and communities attributes.
- Field descriptions
- Address—Hexadecimal number that uniquely identifies the path attributes
- Refcount—Number of routes that share the path attributes
- Origin—Value of the origin path attribute
- Next-hop—Value of the next-hop path attribute
- AS-path—Value of the AS-path attribute
- Example
host1# show ip bgp neighbors 1.02.3.4 paths Address Refcount Origin Next-hop AS-path 0xC384BD0 1 IGP 192.168.1.1 11488 701 2853 5515 764 0xC384C40 1 IGP 192.168.1.1 11488 701 4183 0xC384CB0 1 IGP 192.168.1.1 11488 701 1239 1833 1833 1833 1299 8308 0xC384D20 1 IGP 192.168.1.1 11488 701 6453 786 0xC384D90 1 IGP 192.168.1.1 11488 701 6453 1103 1103 0xC384E00 1 IGP 192.168.1.1 11488 701 6762 9116 9116 9116 6888 6888 0xC384E70 1 IGP 192.168.1.1 11488 701 6453 8297 6758 0xC384EE0 1 IGP 192.168.1.1 11488 701 5511 3215 0xC384F50 1 IGP 192.168.1.1 11488 701 3561 5683 5551 0xC384FC0 1 IGP 192.168.1.1 11488 701 1239 1755 1273 8793 8793 8793 0xC385030 1 IGP 192.168.1.1 11488 701 5705 5693
- See show ip bgp neighbors paths.
- See show bgp ipv6 neighbors paths.
show ip bgp neighbors received prefix-filter
- Use to display prefix-list outbound route filters received from the neighbor.
- Field descriptions
- seq—Sequence number of the entry in the prefix list
- permit, deny—Condition statement for addresses matching the listed address
- Example
host1#show ip bgp neighbors 192.168.1.158 received prefix-filter ip prefix-list filter 192.168.1.158 for address family ipv4:unicast seq 5 permit 10.1.1.1/32 seq 10 permit 10.1.1.2/32 seq 15 permit 10.1.1.3/32
- See show ip bgp neighbors received prefix-filter.
show ip bgp neighbors received-routes
show bgp ipv6 neighbors received-routes
- Use to display routes originating from the specified BGP neighbor before inbound policy is applied.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Prefix—Prefix for the routing table entry
- Peer—IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator for the route
- LocPrf—Local preference for the route
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show ip bgp neighbors 192.168.1.158 received-routes Local BGP identifier 111.111.111.111, local AS 444 0 routes (0 bytes used), 0 distinct destinations (0 bytes used) 0 routes selected for route table installation 0 path attribute entries (0 bytes used)
Status codes: > best, * invalid, s suppressed, d dampened, r rejected
Prefix Peer Next-hop MED LocPrf Weight Origin >0.0.0.0/0 192.168.1.158 192.168.1.158 0 IGP >13.13.13.13/32 192.168.1.158 192.168.1.158 0 0 IGP
- See show ip bgp neighbors received-routes.
- See show bgp ipv6 neighbors received-routes.
show ip bgp neighbors routes
show bgp ipv6 neighbors routes
- Use to display, after inbound policy is applied, all routes that originate from the specified BGP neighbor.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- Field descriptions
- Local router ID—BGP router ID of the local router
- local AS—Local autonomous system number
- paths—Total number of routes stored in the BGP routing table. If several peers have advertised a route to the same prefix, all routes are included in this count.‘
- distinct prefixes—Number of routes to unique prefixes stored in the BGP routing table. If several peers have advertised a route to the same prefix, only the best route is included in this count.
- paths selected for route table installation—Number of routes in the BGP routing table that have been inserted into the IP routing table
- path attribute entries—Number of distinct path attributes stored in BGP's internal path attributes table. If BGP receives two routes for different prefixes but with identical path attributes, BGP will create only one entry in its internal path attribute table and share it between the two routes to conserve memory.
- Local-RIB version—Number that is increased by one each time a route in that RIB is added, removed or modified.
- FIB version—Number that is increased by one each time BGP updates the routes in the IP routing table based on changes in the local RIB. The FIB version matches the local-RIB version when BGP has finished updating the routes in the IP route table. The FIB version is less than the local-RIB version when BGP is still in the process of updating the IP routing table.
- Prefix—Prefix for the routing table entry
- Peer— IP address of BGP peer
- Next-hop—IP address of the next hop
- MED—Multiexit discriminator
- CalPrf—Calculated preference
- Weight—Assigned path weight
- Origin—Origin of the route
- Example
host1#show bgp ipv6 neighbors 12.12.12.12 routes Local BGP identifier 11.11.11.11, local AS 400 5 routes (200 bytes) 5 destinations (360 bytes) of which 5 have a route 5 routes selected for route table installation 4 path attribute entries (608 bytes) Local-RIB version 33. FIB version 33. Status codes: > best, * invalid, s suppressed, d dampened, r rejected, a auto-summarized Prefix Peer Next-hop MED LocPrf Weight Origin > 3ffe:0:1:1::/64 12.12.12.12 ::102.102.102.2 0 100 0 inc. - See show ip bgp neighbors routes.
- See show bgp ipv6 neighbors routes.
show ip bgp network
show bgp ipv6 network
- Use to display information about networks in an AS.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgpshow ip bgp for descriptions of the fields displayed by this keyword.
- Example
host1#show bgp ipv6 network Prefix Weight Route-map Backdoor 3ffe:0:0:2::/64 No
- See show ip bgp network.
- See show bgp ipv6 network.
show ip bgp next-hops
show bgp ipv6 next-hops
- Use to display information about BGP next hops.
- Specify all indirect next hops or a particular indirect next hop.
- Example
host1:3#show ip bgp next-hops Indirect next-hop 4.4.4.4 Reachable (metric 2) Direct next-hop atm2/0.34 (34.34.34.4) Reference count is 3
Indirect next-hop ::ffff:2.2.2.2 MPLS stacked label 17 Reachable (metric 3) Direct next-hop tun mpls:vpnInL17-23 Reference count is 1
Indirect next-hop 5.5.5.5 Reachable (metric 2) Direct next-hop atm2/0.35 (35.35.35.5) Reference count is 3
Indirect next-hop 6.6.6.6 Reachable (metric 3) Direct next-hop atm2/0.34 (34.34.34.4) atm2/0.35 (35.35.35.5) Reference count is 3Indirect next-hop 13.13.13.1 Not reachable Reference count is 2
- See show ip bgp next-hops.
- See show bgp ipv6 next-hops.
show ip bgp paths
show bgp ipv6 paths
- Use to display information about BGP paths.
- This command displays only the most common path attributes. BGP internally maintains additional attributes that are not displayed—for example, the MED, local preference, and communities attributes.
- Field descriptions
- Address—Hexadecimal number that uniquely identifies the path attributes
- Refcount—Number of routes that share the path attributes
- Origin—Value of the origin path attribute
- Next-hop—Value of the next-hop path attribute
- AS-path—Value of the AS-path attribute
- Example
host1#show bgp ipv6 paths Address Refcount Metric AS-path 0x4B311118 1 100 0x4C548224 1 0 100 0x4C548530 1 0 200 0x4C548704 2 0 300
- See show ip bgp paths.
- See show bgp ipv6 paths.
show ip bgp peer-group
show bgp ipv6 peer-group
- Use to display information about BGP peer groups.
- Field descriptions
- BGP peer group—Name of a BGP peer group
- remote AS—Number of the remote AS
- Description—Textual description of the BGP peer group
- Members—IP addresses of the members of the BGP peer group
- Default originate—Status of default origination of the BGP peer group
- EBGP multi-hop—Status of EBGP multihop for the peer group
- IBGP single-hop—Status of IBGP single hop for the peer group
- BFD—Status of BFD configuration for the peer group
- BFD session—Type and address of peer to which BFD session is established
- Minimum transmit interval—Desired time interval between BFD packets transmitted to members of peer group
- Minimum receive interval—Desired time interval between BFD packets received from members of peer group
- Multiplier—Number of BFD packets that can be missed before declaring BFD session down
- Next hop self—Status of next-hop self information for the peer group
- Peers are route reflector clients—BGP peer group is configured as a route reflector. This field does not appear when route reflectors are not configured.
- weight—Neighbor weights assigned to BGP peer groups
- Incoming update distribute list—Distribute lists for incoming routes, if configured
- Outgoing update distribute list—Distribute list for outgoing routes, if configured
- Incoming update filter list—Filter list for incoming routes, if configured
- Outgoing update filter list—Filter list for outgoing routes, if configured
- Weight filter list—Weight filter list for routes, if configured
- Incoming route map—Incoming route map, if configured
- Outgoing route map—Outgoing route map, if configured
- Minimum route advertisement interval—Minimum time between route advertisements
- Configured update source IP address—IP address used when sending update messages
- Advertise-map—Name of route map that specifies routes to be advertised when routes in conditional route maps are matched
- Condition-map—Name of route map that specifies routes to be matched by routes in the BGP routing table
- Sequence—Position of the specified advertise route map in a list of advertise route maps configured for a particular peer group within the same address-family. A lower sequence number has a higher priority; that route map is processed before one with a higher sequence number.
- Status—Status of the routes specified by the route map, advertise (route map condition has been met) or withdraw (route map condition has not been met; regardless of this status, the specified routes might be governed by another route map with a lower sequence number and actually advertised or not according to that map
- Example
host1#show ip bgp peer-group BGP peer-group leftcoast, remote AS 200 Peer-group members are external peers Local AS 100 Administrative status is Start EBGP multi-hop is disabled IBGP single-hop is disabled BFD is enabled: Single-hop IPv4 BFD session Minimum transmit interval is 300 ms Minimum receive interval is 300 ms Multiplier is 3 Maximum update message size is 1024 octets Neighbor weight is 0 Connect retry interval is 10 seconds initially Configured keep-alive interval is 30 seconds Configured hold time is 90 seconds Minimum route advertisement interval is 30 seconds Minimum AS origination interval is 10 seconds Graceful restart negotiation: Restart time is 120 seconds Stale paths time is 360 secondsConfiguration for address family ipv4:unicast RIB-out is disabled Default originate is disabled Next hop self is disabled Next hop unchanged is disabled Don't send communities Inbound soft reconfiguration is disabled Private AS number stripping is disabled Override site AS with provider AS is disabled No loops in the received AS-path are allowed Members: 10.2.2.2 10.3.3.3 - Fields relevant to conditional advertisement:
Advertise-map is advertisetoR1 Condition-map: trigger1 Sequence: 5 Status: Withdraw Advertise-map is alternatetoR1 Condition-map: trigger2 Sequence: 10 Status: Advertise - See show ip bgp peer-group.
- See show bgp ipv6 peer-group.
show ip bgp quote-regexp
show bgp ipv6 quote-regexp
- Use to display information about BGP routes whose AS-path matches the specified regular expression.
- Use with only a single regular expression element.
- You can use output filtering.
- You must enclose any elements containing a space within quotation marks (“ element” ).
- Regular expressions match numbers for which the specified path is a substring—for example, if you specify 20, 200 matches because 20 is a substring of 200. You can disallow substring matching by using the underscore (_) metacharacter to constrain matching to the specified pattern, for example, _20_.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- See show ip bgp quote-regexp.
- See show bgp ipv6 quote-regexp.
show ip bgp regexp
show bgp ipv6 regexp
- Use to display information about BGP routes whose AS-path matches the specified regular expression.
- Use with one or more regular expression elements.
- You cannot use output filtering.
- You do not have to enclose elements containing a space within quotation marks.
- Regular expressions match numbers for which the specified path is a substring—for example, if you specify 20, 200 matches because 20 is a substring of 200. You can disallow substring matching by using the underscore (_) metacharacter to constrain matching to the specified pattern, for example, _20_.
- Reports whether the indirect next hop of a route is unreachable; if not, displays the IGP cost to the indirect next hop.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- See show ip bgp regexp.
- See show bgp ipv6 regexp.
Examples for regexp and quote-regexp
In many cases, you can use either show ip bgp regexp or show ip bgp quote-regexp with the same results. For example, to show all routes whose AS-path starts with 200 you can use either command as follows:
host1#show ip bgp regexp ^200 Local router ID 192.168.1.232, local AS 100 6 paths, 3 distinct prefixes (324 bytes used) 3 paths selected for route table installation 7 path attribute entries (872 bytes used)
Prefix Next-hop MED CalPrf Weight AS-path 10.99.1.2/32 10.1.1.2 100 100 200 10.99.1.3/32 10.1.1.2 100 100 200 10 10.99.1.4/32 10.1.1.2 100 100 200 10 20
host1#show ip bgp quote-regexp ^200 Local router ID 192.168.1.232, local AS 100 6 paths, 3 distinct prefixes (324 bytes used) 3 paths selected for route table installation 7 path attribute entries (872 bytes used)
Prefix Next-hop MED CalPrf Weight AS-path 10.99.1.2/32 10.1.1.2 100 100 200 10.99.1.3/32 10.1.1.2 100 100 200 10 10.99.1.4/32 10.1.1.2 100 100 200 10 20
If the regular expression contains one or more spaces, you must place quotation marks around the expression in the show ip bgp quote-regexp command but not in the show ip bgp regexp command. For example, to show all routes whose AS-path contains AS number 10 followed immediately by AS number 20:
host1#show ip bgp regexp 10 20 Local router ID 192.168.1.232, local AS 100 6 paths, 3 distinct prefixes (324 bytes used) 3 paths selected for route table installation 7 path attribute entries (872 bytes used)
Prefix Next-hop MED CalPrf Weight AS-path 10.99.1.4/32 10.1.1.2 100 100 200 10 20
host1#show ip bgp quote-regexp 10 20
^
% Invalid input detected at '^' marker.host1#show ip bgp quote-regexp “ 10 20" Local router ID 192.168.1.232, local AS 100 6 paths, 3 distinct prefixes (324 bytes used) 3 paths selected for route table installation 7 path attribute entries (872 bytes used)
Prefix Next-hop MED CalPrf Weight AS-path 10.99.1.4/32 10.1.1.2 100 100 200 10 20
The show ip bgp regexp command accepts multiple strings as arguments. If you try to apply output filtering, the command interprets the filter information as a regular expression and fails:
host1#show ip bgp regexp ^200 | begin Prefix % invalid regular expression
Because the show ip bgp quote-regexp command accepts only one string as an argument to the regular expression, output filtering is possible:
host1#show ip bgp quote-regexp ^200 | begin Prefix Prefix Next-hop MED CalPrf Weight AS-path 10.99.1.2/32 10.1.1.2 100 100 200 10.99.1.3/32 10.1.1.2 100 100 200 10 10.99.1.4/32 10.1.1.2 100 100 200 10 20
show ip bgp summary
show bgp ipv6 summary
- Use to summarize the status of all BGP neighbors.
- You can use the field options to display filtered information about BGP neighbors.
- If you filter the display with field options, the usual introductory information about BGP attributes is displayed only if you issue the intro fields option. See show ip bgp for descriptions of the fields displayed by this keyword.
- You can use the default-fields peer command to specify default fields to be displayed by subsequently issued show ip bgp summary commands.
- Field descriptions
- Local router ID—Router ID of the local router
- Local AS—AS number of local router
- Administrative state—BGP administrative state, start or stop
- BGP Operational state—Operational state, up, down, or overload
- Shutdown in overload state—Status, enabled or disabled
- Default local preference—Default value for local preference
- IGP synchronization—Synchronization status, enabled or disabled
- Default originate—Whether network 0.0.0.0 is redistributed into BGP (enabled) or not (disabled)
- Auto-summary—Status of auto summarization of routes redistributed into BGP
- Always compare MED—Status, enabled or disabled
- Compare MED within confederation—Status, enabled or disabled
- Advertise inactive routes—Status, enabled or disabled
- Advertise best external route to internal peer—Status, enabled or disabled
- Enforce first AS—Status, enabled or disabled
- Missing MED as worst—Status, enabled or disabled
- Route flap dampening—Status, enabled or disabled
- Maximum number of equal-cost EBGP paths—Number of paths
- Maximum number of equal-cost IBGP paths—Number of paths
- Log neighbor changes—Status, enabled or disabled
- Fast External Fallover—Status, enabled or disabled
- No maximum received AS-path length—Indicates whether limit is set for AS path length and, if set, the limit
- BGP administrative distances—Distances for external, internal, and local BGP routes
- Router is a route reflector—Indicates whether the router has been configured as a route reflector
- Client-to-client reflection—Whether client-to-client reflection is configured (enabled) or not (disabled)
- Cluster ID—Identifying number for cluster ID
- Route-target filter—Status, enabled or disabled
- Default IPv4-unicast—Status, enabled or disabled
- Redistribution of iBGP routes—Status, enabled or disabled
- Check reachability of next-hops for VPN routes—Status, enabled or disabled
- Graceful restart—Status, enabled or disabled
- Global graceful-restart restart time—Time in seconds
- Global graceful-restart stale paths time—Time in seconds
- Graceful-restart path selection defer time—Time in seconds
- Route Distinguisher—RD assigned to the VRF
- Confederation ID—Confederation ID
- Confederation peers—Confederation peers
- Import route map—Route map associated with the VRF that filters and modifies routes imported to the VRF from the global BGP VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes).
- Export route map—Route map associated with the VRF that modifies and filters routes exported by the VRF to the global BGP VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes). The can filter routes text appears only if the filter keyword was issued for export map.
- Global import route map—Route map associated with the VRF that modifies routes imported to the VRF from the global BGP non-VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes).
- routes imported from global table—Number of routes imported from the global BGP non-VPN RIB; also lists the maximum number of routes that can be imported
- Global export route map—Route map associated with the VRF that modifies routes exported by the VRF to the global BGP non-VPN RIB. The map applies to both IPv4 and IPv6 routes, unless the field name is preceded by IPv4 (applies the map to only IPv4 routes) or IPv6 (applies the map to only IPv6 routes).
- Local-RIB version—Number that is increased by one each time a route in that RIB is added, removed or modified.
- FIB version—Number that is increased by one each time BGP updates the routes in the IP routing table based on changes in the local RIB. The FIB version matches the local-RIB version when BGP has finished updating the routes in the IP route table. The FIB version is less than the local-RIB version when BGP is still in the process of updating the IP routing table.
- Neighbor—BGP neighbors
- AS—AS number of the peer
- Ver—Negotiated BGP version number
- State—State of the connection
- Up/down time—Time the connection has been up or down
- Messages sent—Number of messages sent to peer
- Messages received—Number of messages received from peer
- Prefixes received—Number of prefixes received from peer
- Rib Ver—Last RIB version queued to be sent to peer
- Send Q—Number of messages queued to be sent to peer
- More InQ—Status indicating whether any messages are waiting to be sent to peer
- Example 1
host1#show bgp ipv6 summary Local router ID 10.13.13.13, local AS 400 Administrative state is Start BGP Operational state is Up Shutdown in overload state is disabled Default local preference is 100 IGP synchronization is disabled Default originate is disabled Always compare MED is disabled Compare MED within confederation is disabled Advertise inactive routes is disabled Advertise best external route to internal peers is disabled Enforce first AS is disabled Missing MED as worst is disabled Route flap dampening is disabled Maximum number of equal-cost EBGP paths is 2 Maximum number of equal-cost IBGP paths is 2 Log neighbor changes is disabled Fast External Fallover is disabled No maximum received AS-path length BGP administrative distances are 20 (ext), 200 (int), and 200 (local) Client-to-client reflection is enabled Cluster ID is 10.13.13.13 Route-target filter is enabled Default IPv4-unicast is enabled Redistribution of iBGP routes is disabled Graceful restart is globally disabled Global graceful-restart restart time is 120 seconds Global graceful-restart stale paths time is 360 seconds Graceful-restart path selection defer time is 360 seconds This platform supports only the receiver role of graceful restart Route Distinguisher: 100:11 Import route map: test2-import-map Export route map: test1-export-map (can not filter routes) Global import route map: test3-global-import-map 103 routes imported from global table (max 5000 routes allowed) Global export route map: test4-global-export-map Local-RIB version 7. FIB version 7. Messages Messages Prefixes Neighbor AS State Up/down time Sent Received Received 11.11.11.11 400 Established 00:36:19 78 81 2 12.12.12.12 400 Established 00:36:21 78 78 1 103.103.103.3 300 Established 00:36:34 85 80 2 - Example 2—Status of next hop reachability checking
is displayed only if you specify vpnv4.
host1#show ip bgp vpnv4 all summary Local router ID 10.13.5.19, local AS 100 Administrative state is Start BGP Operational state is Up ... Default IPv4-unicast is enabled Redistribution of iBGP routes is disabled Check reachability of next-hops for VPN routes is enabled ...
- Example 3—Status of fields related to enabling local
AS numbers to be received in routes
host1#show ip bgp summary fields remote-as state rib-version send-queue-length more-in-queue Send More Neighbor AS State RIB Ver Q InQ 2.2.2.2 100 Established 2 0 no - See show ip bgp summary.
- See show bgp ipv6 summary.
show ip community-list
- Use to display routes that are permitted by a BGP community list.
- Example
host1#show ip community-list Community List 1: permit 752877569 (11488:1) permit 752877570 (11488:2) permit 752877571 (11488:3) permit 752877572 (11488:4) Community List 2: permit 4294967043 (local-as)
- See show ip community-list.
undebug ip bgp
- Use to disable the display of information about BGP logs that was previously enabled with the debug ip bgp command.
- Example host1#undebug ip bgp
- There is no no version.
- See undebug ip bgp.
