To display entries in the Border Gateway Protocol (BGP) routing table, use the show
ip
bgp command in user EXEC or privileged EXEC mode.
show ip bgp [ip-address [mask [longer-prefixes [injected] | shorter-prefixes [length] | best-path-reason | bestpath | multipaths | subnets] | best-path-reason | bestpath | internal | multipaths] | all | oer-paths | prefix-list name | pending-prefixes | route-map name | version {version-number | recent offset-value}]
Syntax Description
ip-address
|
(Optional) IP address entered to filter the output to display only a particular host or network in the BGP routing table.
|
mask
|
(Optional) Mask to filter or match hosts that are part of the specified network.
|
longer-prefixes
|
(Optional) Displays the specified route and all more-specific routes.
|
injected
|
(Optional) Displays more-specific prefixes injected into the BGP routing table.
|
shorter-prefixes
|
(Optional) Displays the specified route and all less-specific routes.
|
length
|
(Optional) The prefix length. The range is a number from 0 to 32.
|
bestpath
|
(Optional) Displays the best path for this prefix.
|
best-path-reason |
(Optional) Displays the reason why a path loses to the bestpath.
Note
|
If the best-path is yet to be selected, then the output will be 'Best Path Evaluation: No best path'
|
|
internal |
(Optional) Displays the internal details for this prefix.
|
multipaths
|
(Optional) Displays multipaths for this prefix.
|
subnets
|
(Optional) Displays the subnet routes for the specified prefix.
|
all
|
(Optional) Displays all address family information in the BGP routing table.
|
oer-paths
|
(Optional) Displays Optimized Edge Routing (OER) controlled prefixes in the BGP routing table.
|
prefix-list name
|
(Optional) Filters the output based on the specified prefix list.
|
pending-prefixes
|
(Optional) Displays prefixes that are pending deletion from the BGP routing table.
|
route-map name
|
(Optional) Filters the output based on the specified route map.
|
version version-number
|
(Optional) Displays all prefixes with network versions greater than or equal to the specified version number. The range is
from 1 to 4294967295.
|
recent offset-value
|
(Optional) Displays the offset from the current routing table version. The range is from 1 to 4294967295.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
Cisco IOS XE Everest 16.5.1a
|
This command was introduced.
|
Cisco IOS XE Gibraltar 16.10.1
|
The best-path-reason keyword was added to this command.
BGP Path Installation Time-Stamp was added to the output of the command.
BGP Peak Prefix Watermark was added to the output of the command.
|
Usage Guidelines
The show
ip
bgp command is used to display the contents of the BGP routing table. The output can be filtered to display entries for a specific
prefix, prefix length, and prefixes injected through a prefix list, route map, or conditional advertisement.
When changes are made to the network address, the network version number is incremented. Use the version keyword to view a specific network version.
Examples
The following sample output displays the BGP routing table:
Device#show ip bgp
BGP table version is 6, local router ID is 10.0.96.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
N* 10.0.0.1 10.0.0.3 0 0 3 ?
N*> 10.0.3.5 0 0 4 ?
Nr 10.0.0.0/8 10.0.0.3 0 0 3 ?
Nr> 10.0.3.5 0 0 4 ?
Nr> 10.0.0.0/24 10.0.0.3 0 0 3 ?
V*> 10.0.2.0/24 0.0.0.0 0 32768 i
Vr> 10.0.3.0/24 10.0.3.5 0 0 4 ?
The table below describes the significant fields shown in the display.
Table 24. show ip bgp Field Descriptions
Field
|
Description
|
BGP table version
|
Internal version number of the table. This number is incremented whenever the table changes.
|
local router ID
|
IP address of the router.
|
Status codes
|
Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following
values:
-
s—The table entry is suppressed.
-
d—The table entry is dampened.
-
h—The table entry history.
-
*—The table entry is valid.
-
>—The table entry is the best entry to use for that network.
-
i—The table entry was learned via an internal BGP (iBGP) session.
-
r—The table entry is a RIB-failure.
-
S—The table entry is stale.
-
m—The table entry has multipath to use for that network.
-
b—The table entry has a backup path to use for that network.
-
x—The table entry has a best external route to use for the network.
|
Origin codes
|
Origin of the entry. The origin code is placed at the end of each line in the table. It can be one of the following values:
-
a—Path is selected as an additional path.
-
i—Entry originated from an Interior Gateway Protocol (IGP) and was advertised with a network router configuration command.
-
e—Entry originated from an Exterior Gateway Protocol (EGP).
-
?—Origin of the path is not clear. Usually, this is a router that is redistributed into BGP from an IGP.
|
RPKI validation codes
|
If shown, the RPKI validation state for the network prefix, which is downloaded from the RPKI server. The codes are shown
only if the bgp rpki server or neighbor announce rpki state command is configured.
|
Network
|
IP address of a network entity.
|
Next Hop
|
IP address of the next system that is used when forwarding a packet to the destination network. An entry of 0.0.0.0 indicates
that the router has some non-BGP routes to this network.
|
Metric
|
If shown, the value of the interautonomous system metric.
|
LocPrf
|
Local preference value as set with the set
local-preference route-map configuration command. The default value is 100.
|
Weight
|
Weight of the route as set via autonomous system filters.
|
Path
|
Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the
path.
|
(stale)
|
Indicates that the following path for the specified autonomous system is marked as “stale” during a graceful restart process.
|
Updated on
|
The time at which the path is received or updated.
|
Examples
The following sample output shows the BGP routing table with 4-byte autonomous system numbers, 65536 and 65550, shown under
the Path field. This example requires Cisco IOS Release 12.0(32)SY8, 12.0(33)S3, 12.2(33)SRE, 12.2(33)XNE, 12.2(33)SXI1, Cisco
IOS XE Release 2.4, or a later release.
Device#show ip bgp
BGP table version is 4, local router ID is 172.16.1.99
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.1.1.0/24 192.168.1.2 0 0 65536 i
*> 10.2.2.0/24 192.168.3.2 0 0 65550 i
*> 172.16.1.0/24 0.0.0.0 0 32768 i
Examples
The following sample output displays information about the 192.168.1.0 entry in the BGP routing table:
Device#show ip bgp 192.168.1.0
BGP routing table entry for 192.168.1.0/24, version 22
Paths: (2 available, best #2, table default)
Additional-path
Advertised to update-groups:
3
10 10
192.168.3.2 from 172.16.1.2 (10.2.2.2)
Origin IGP, metric 0, localpref 100, valid, internal, backup/repair
10 10
192.168.1.2 from 192.168.1.2 (10.3.3.3)
Origin IGP, localpref 100, valid, external, best , recursive-via-connected
The following sample output displays information about the 10.3.3.3 255.255.255.255 entry in the BGP routing table:
Device#show ip bgp 10.3.3.3 255.255.255.255
BGP routing table entry for 10.3.3.3/32, version 35
Paths: (3 available, best #2, table default)
Multipath: eBGP
Flag: 0x860
Advertised to update-groups:
1
200
10.71.8.165 from 10.71.8.165 (192.168.0.102)
Origin incomplete, localpref 100, valid, external, backup/repair
Only allowed to recurse through connected route
200
10.71.11.165 from 10.71.11.165 (192.168.0.102)
Origin incomplete, localpref 100, weight 100, valid, external, best
Only allowed to recurse through connected route
200
10.71.10.165 from 10.71.10.165 (192.168.0.104)
Origin incomplete, localpref 100, valid, external,
Only allowed to recurse through connected route
The table below describes the significant fields shown in the display.
Table 25. show ip bgp ip-address Field Descriptions
Field
|
Description
|
BGP routing table entry for
|
IP address or network number of the routing table entry.
|
version
|
Internal version number of the table. This number is incremented whenever the table changes.
|
Paths
|
The number of available paths, and the number of installed best paths. This line displays “Default-IP-Routing-Table” when
the best path is installed in the IP routing table.
|
Multipath
|
This field is displayed when multipath load sharing is enabled. This field will indicate if the multipaths are iBGP or eBGP.
|
Advertised to update-groups
|
The number of each update group for which advertisements are processed.
|
Origin
|
Origin of the entry. The origin can be IGP, EGP, or incomplete. This line displays the configured metric (0 if no metric
is configured), the local preference value (100 is default), and the status and type of route (internal, external, multipath,
best).
|
Extended Community
|
This field is displayed if the route carries an extended community attribute. The attribute code is displayed on this line.
Information about the extended community is displayed on a subsequent line.
|
Examples
The following is sample output from the show
ip
bgp command entered with the all keyword. Information about all configured address families is displayed.
Device#show ip bgp all
For address family: IPv4 Unicast *****
BGP table version is 27, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.1.1.0/24 0.0.0.0 0 32768 ?
*> 10.13.13.0/24 0.0.0.0 0 32768 ?
*> 10.15.15.0/24 0.0.0.0 0 32768 ?
*>i10.18.18.0/24 172.16.14.105 1388 91351 0 100 e
*>i10.100.0.0/16 172.16.14.107 262 272 0 1 2 3 i
*>i10.100.0.0/16 172.16.14.105 1388 91351 0 100 e
*>i10.101.0.0/16 172.16.14.105 1388 91351 0 100 e
*>i10.103.0.0/16 172.16.14.101 1388 173 173 100 e
*>i10.104.0.0/16 172.16.14.101 1388 173 173 100 e
*>i10.100.0.0/16 172.16.14.106 2219 20889 0 53285 33299 51178 47751 e
*>i10.101.0.0/16 172.16.14.106 2219 20889 0 53285 33299 51178 47751 e
* 10.100.0.0/16 172.16.14.109 2309 0 200 300 e
*> 172.16.14.108 1388 0 100 e
* 10.101.0.0/16 172.16.14.109 2309 0 200 300 e
*> 172.16.14.108 1388 0 100 e
*> 10.102.0.0/16 172.16.14.108 1388 0 100 e
*> 172.16.14.0/24 0.0.0.0 0 32768 ?
*> 192.168.5.0 0.0.0.0 0 32768 ?
*> 10.80.0.0/16 172.16.14.108 1388 0 50 e
*> 10.80.0.0/16 172.16.14.108 1388 0 50 e
For address family: VPNv4 Unicast *****
BGP table version is 21, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 1:1 (default for vrf vpn1)
*> 10.1.1.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e
*> 10.1.2.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e
*> 10.1.3.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e
*> 10.1.4.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e
*> 10.1.5.0/24 192.168.4.3 1622 0 100 53285 33299 51178 {27016,57039,16690} e
*>i172.17.1.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.2.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.3.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.4.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.5.0/24 10.3.3.3 10 30 0 53285 33299 51178 47751 ?
For address family: IPv4 Multicast *****
BGP table version is 11, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.40.40.0/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e
* 10.1.1.1 1622 0 15 20 1 {2} e
*> 10.40.40.64/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e
* 10.1.1.1 1622 0 15 20 1 {2} e
*> 10.40.40.128/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e
* 10.1.1.1 2563 0 15 20 1 {2} e
*> 10.40.40.192/26 10.1.1.1 2563 0 15 20 1 {2} e
*> 10.40.41.0/26 10.1.1.1 1209 0 15 20 1 {2} e
*>i10.102.0.0/16 10.1.1.1 300 500 0 5 4 {101,102} e
*>i10.103.0.0/16 10.1.1.1 300 500 0 5 4 {101,102} e
For address family: NSAP Unicast *****
BGP table version is 1, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i45.0000.0002.0001.000c.00 49.0001.0000.0000.0a00 100 0 ?
* i46.0001.0000.0000.0000.0a00 49.0001.0000.0000.0a00 100 0 ?
* i47.0001.0000.0000.000b.00 49.0001.0000.0000.0a00 100 0 ?
* i47.0001.0000.0000.000e.00 49.0001.0000.0000.0a00
Examples
The following is sample output from the show
ip
bgp longer-prefixes command:
Device#show ip bgp 10.92.0.0 255.255.0.0 longer-prefixes
BGP table version is 1738, local router ID is 192.168.72.24
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 10.92.0.0 10.92.72.30 8896 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.1.0 10.92.72.30 8796 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.11.0 10.92.72.30 42482 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.14.0 10.92.72.30 8796 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.15.0 10.92.72.30 8696 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.16.0 10.92.72.30 1400 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.17.0 10.92.72.30 1400 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.18.0 10.92.72.30 8876 32768 ?
* 10.92.72.30 0 109 108 ?
*> 10.92.19.0 10.92.72.30 8876 32768 ?
* 10.92.72.30 0 109 108 ?
Examples
The following is sample output from the show ip bgp
shorter-prefixes command. An 8-bit prefix length is specified.
Device#show ip bgp 172.16.0.0/16 shorter-prefixes 8
*> 172.16.0.0 10.0.0.2 0 ?
* 10.0.0.2 0 0 200 ?
Examples
The following is sample output from the show
ip
bgp prefix-list command:
Device#show ip bgp prefix-list ROUTE
BGP table version is 39, local router ID is 10.0.0.1
Status codes:s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes:i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.0 10.0.0.2 0 ?
* 10.0.0.2 0 0 200 ?
Examples
The following is sample output from the show ip bgp
route-map command:
Device#show ip bgp route-map LEARNED_PATH
BGP table version is 40, local router ID is 10.0.0.1
Status codes:s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes:i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.0 10.0.0.2 0 ?
* 10.0.0.2 0 0 200 ?
Examples
The following output indicates (for each neighbor) whether any of the additional path tags (group-best, all, best 2 or best
3) are applied to the path. A line of output indicates rx pathid (received from neighbor) and tx pathid (announcing to neighbors).
Note that the “Path advertised to update-groups:” is now per-path when the BGP Additional Paths feature is enabled.
Device#show ip bgp 10.0.0.1 255.255.255.224
BGP routing table entry for 10.0.0.1/28, version 82
Paths: (10 available, best #5, table default)
Path advertised to update-groups:
21 25
Refresh Epoch 1
20 50, (Received from a RR-client)
192.0.2.1 from 192.0.2.1 (192.0.2.1)
Origin IGP, metric 200, localpref 100, valid, internal, all
Originator: 192.0.2.1, Cluster list: 2.2.2.2
mpls labels in/out 16/nolabel
rx pathid: 0, tx pathid: 0x9
Updated on Aug 14 2018 18:30:39 PST
Path advertised to update-groups:
18 21
Refresh Epoch 1
30
192.0.2.2 from 192.0.2.2 (192.0.2.2)
Origin IGP, metric 200, localpref 100, valid, internal, group-best, all
Originator: 192.0.2.2, Cluster list: 4.4.4.4
mpls labels in/out 16/nolabel
rx pathid: 0x1, tx pathid: 0x8
Updated on Aug 14 2018 18:30:39 PST
Path advertised to update-groups:
16 18 19 20 21 22 24
25 27
Refresh Epoch 1
10
192.0.2.3 from 192.0.2.3 (192.0.2.3)
Origin IGP, metric 200, localpref 100, valid, external, best2, all
mpls labels in/out 16/nolabel
rx pathid: 0, tx pathid: 0x7
Updated on Aug 14 2018 18:30:39 PST
Path advertised to update-groups:
20 21 22 24 25
Refresh Epoch 1
10
192.0.2.4 from 192.0.2.4 (192.0.2.4)
Origin IGP, metric 300, localpref 100, valid, external, best3, all
mpls labels in/out 16/nolabel
rx pathid: 0, tx pathid: 0x6
Updated on Jun 17 2018 11:12:30 PST
Path advertised to update-groups:
10 13 17 18 19 20 21
22 23 24 25 26 27 28
Refresh Epoch 1
10
192.0.2.5 from 192.0.2.5 (192.0.2.5)
Origin IGP, metric 100, localpref 100, valid, external, best
mpls labels in/out 16/nolabel
rx pathid: 0, tx pathid: 0x0
Updated on Jun 17 2018 11:12:30 PST
Path advertised to update-groups:
21
Refresh Epoch 1
30
192.0.2.6 from 192.0.2.6 (192.0.2.6)
Origin IGP, metric 200, localpref 100, valid, internal, all
Originator: 192.0.2.6, Cluster list: 5.5.5.5
mpls labels in/out 16/nolabel
rx pathid: 0x1, tx pathid: 0x5
Updated on Jun 17 2018 11:12:30 PST
Path advertised to update-groups:
18 23 24 26 28
Refresh Epoch 1
60 40, (Received from a RR-client)
192.0.2.7 from 192.0.2.7 (192.0.2.7)
Origin IGP, metric 250, localpref 100, valid, internal, group-best
Originator: 192.0.2.7, Cluster list: 3.3.3.3
mpls labels in/out 16/nolabel
rx pathid: 0x2, tx pathid: 0x2
Updated on Jun 17 2018 11:12:30 PST
Path advertised to update-groups:
25
Refresh Epoch 1
30 40, (Received from a RR-client)
192.0.2.8 from 192.0.2.8 (192.0.2.8)
Origin IGP, metric 200, localpref 100, valid, internal, all
Originator: 192.0.2.8, Cluster list: 2.2.2.2
mpls labels in/out 16/nolabel
rx pathid: 0x1, tx pathid: 0x3
Updated on Jun 17 2018 11:12:30 PST
Path advertised to update-groups:
18 21 23 24 25 26 28
Refresh Epoch 1
20 40, (Received from a RR-client)
192.0.2.9 from 192.0.2.9 (192.0.2.9)
Origin IGP, metric 200, localpref 100, valid, internal, group-best, all
Originator: 192.0.2.9, Cluster list: 2.2.2.2
mpls labels in/out 16/nolabel
rx pathid: 0x1, tx pathid: 0x4
Updated on Jun 17 2018 18:34:12 PST
Path advertised to update-groups:
21
Refresh Epoch 1
30 40
192.0.2.9 from 192.0.2.9 (192.0.2.9)
Origin IGP, metric 100, localpref 100, valid, internal, all
Originator: 192.0.2.9, Cluster list: 4.4.4.4
mpls labels in/out 16/nolabel
rx pathid: 0x1, tx pathid: 0x1
Updated on Jun 17 2018 18:34:12 PST
Examples
The following is sample output from the show ip bgp command that displays unknown and discarded path attributes:
Device#show ip bgp 192.0.2.0/32
BGP routing table entry for 192.0.2.0/32, version 0
Paths: (1 available, no best path)
Refresh Epoch 1
Local
192.168.101.2 from 192.168.101.2 (192.168.101.2)
Origin IGP, localpref 100, valid, internal
unknown transitive attribute: flag 0xE0 type 0x81 length 0x20
value 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
unknown transitive attribute: flag 0xE0 type 0x83 length 0x20
value 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
discarded unknown attribute: flag 0x40 type 0x63 length 0x64
value 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
Examples
The following is sample output from the show ip bgp version command:
Device#show ip bgp version
BGP table version is 5, local router ID is 10.2.4.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.34.2/24 10.0.0.1 0 0 1 ?
*> 192.168.35.2/24 10.0.0.1 0 0 1 ?
The following example shows how to display the network version:
Device#show ip bgp 192.168.34.2 | include version
BGP routing table entry for 192.168.34.2/24, version 5
The following sample output from the show ip bgp version recent command displays the prefix changes in the specified version:
Device#show ip bgp version recent 2
BGP table version is 5, local router ID is 10.2.4.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.134.1/28 10.0.0.1 0 0 1 ?
*> 192.168.134.19/28 10.0.0.1 0 0 1 ?
*> 192.168.134.34/28 10.0.0.1 0 0 1 ?
Device#show ip bgp 80.230.70.96 best-path-reason
BGP routing table entry for 192.168.3.0/24, version 72
Paths: (2 available, best #2, table default)
Advertised to update-groups:
2
Refresh Epoch 1
2
10.0.101.1 from 10.0.101.1 (10.0.101.1)
Origin IGP, localpref 100, valid, external
Extended Community: RT:100:100
rx pathid: 0, tx pathid: 0
Updated on Aug 14 2018 18:34:12 PST
Best Path Evaluation: Path is younger
Refresh Epoch 1
1
10.0.96.254 from 10.0.96.254 (10.0.96.254)
Origin IGP, localpref 100, valid, external, best
rx pathid: 0, tx pathid: 0x0
Updated on Aug 14 2018 18:30:39 PST
Best Path Evaluation: Overall best path
The following sample output for the show ip bgp summary command shows the peak watermarks and their time-stamps for the peak number of route entries per neighbor bases:
Device#show ip bgp all summary
For address family: IPv4 Unicast
BGP router identifier 10.10.10.10, local AS number 1
BGP table version is 27, main routing table version 27
2 network entries using 496 bytes of memory
2 path entries using 272 bytes of memory
1/1 BGP path/bestpath attribute entries using 280 bytes of memory
1 BGP extended community entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1072 total bytes of memory
BGP activity 58/54 prefixes, 110/106 paths, scan interval 60 secs
20 networks peaked at 00:03:50 Jul 28 2018 PST (00:00:32.833 ago)
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
11.11.11.11 4 1 0 0 1 0 0 00:20:09 Idle
For address family: L2VPN E-VPN
BGP router identifier 10.10.10.10, local AS number 1
BGP table version is 183, main routing table version 183
2 network entries using 688 bytes of memory
2 path entries using 416 bytes of memory
2/2 BGP path/bestpath attribute entries using 560 bytes of memory
1 BGP extended community entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1688 total bytes of memory
BGP activity 58/54 prefixes, 110/106 paths, scan interval 60 secs
30 networks peaked at 00:35:36 Jul 28 2018 PST (00:00:47.321 ago)
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
11.11.11.11 4 1 0 0 1 0 0 00:20:09 Idle