Table Of Contents
show ip bgp
show ip bgp cidr-only
show ip bgp community
show ip bgp community-list
show ip bgp dampened-paths
show ip bgp dampening dampened-paths
show ip bgp dampening flap-statistics
show ip bgp dampening parameters
show ip bgp filter-list
show ip bgp flap-statistics
show ip bgp inconsistent-as
show ip bgp injected-paths
show ip bgp ipv4
show ip bgp ipv4 multicast
show ip bgp ipv4 multicast summary
show ip bgp l2vpn
show ip bgp neighbors
show ip bgp paths
show ip bgp peer-group
show ip bgp quote-regexp
show ip bgp regexp
show ip bgp replication
show ip bgp rib-failure
show ip bgp summary
show ip bgp template peer-policy
show ip bgp template peer-session
show ip bgp update-group
show ip bgp vpnv4
show ip community-list
show ip extcommunity-list
show ip policy-list
show ip prefix-list
soo
synchronization
table-map
template peer-policy
template peer-session
timers bgp
show ip bgp
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]]] | all |
oer-paths | prefix-list name | route-map name]
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-prefix
|
(Optional) Displays the specified route and all less specific routes.
|
length
|
(Optional) Specifies the prefix length. The value for this argument is a number from 0 to 32.
|
all
|
(Optional) Displays all address family information in the BGP routing table.
|
oer-paths
|
(Optional) Displays OER controlled prefixes in the BGP routing table.
|
prefix-list name
|
(Optional) Filters the output based on the specified prefix list.
|
route-map name
|
(Optional) Filters the output based on the specified route map.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0
|
The display of prefix advertisement statistics was added.
|
12.0(6)T
|
The display of a message indicating support for route refresh capability was added.
|
12.0(14)ST
|
The prefix-list, route-map, and shorter-prefixes keywords were added.
|
12.2(2)T
|
The output was modified to display multipaths and a best path to the specified network.
|
12.0(21)ST
|
The output was modified to show the number of MPLS labels that arrive at and depart from the prefix.
|
12.0(22)S
|
A new status code indicating stale routes was added to support BGP graceful restart.
|
12.2(14)S
|
A message indicating support for BGP policy accounting was added and this command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(14)SX
|
This command was integrated into Cisco IOS Release 12.2(14)SX.
|
12.2(15)T
|
A new status code indicating stale routes was added to support BGP graceful restart.
|
12.3(2)T
|
The all keyword was added.
|
12.2(17b)SXA
|
This command was integrated into Cisco IOS Release 12.2(17b)SXA.
|
12.3(8)T
|
The oer-paths keyword was added.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.0(32)S12
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.0(32)SY8
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.4(24)T
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
Cisco IOS XE Release 2.3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.2(33)SXI1
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.0(33)S3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Cisco IOS XE Release 2.4
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
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.
In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538 for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the bgp asnotation dot command followed by the clear ip bgp * command to perform a hard reset of all current BGP sessions.
In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, the Cisco implementation of 4-byte autonomous system numbers uses asdot—1.2 for example—as the only configuration format, regular expression match, and output display, with no asplain support.
oer-paths Keyword
BGP prefixes that are monitored and controlled by Optimized Edge Routing (OER) are displayed by entering the show ip bgp command with the oer-paths keyword.
Examples
•
show ip bgp: Example
•show ip bgp (4-Byte Autonomous System Numbers): Example
•show ip bgp ip-address: Example
•show ip bgp all: Example
•show ip bgp longer-prefixes: Example
•show ip bgp shorter-prefixes: Example
•show ip bgp prefix-list: Example
•show ip bgp route-map: Example
show ip bgp: Example
The following example output shows the BGP routing table:
BGP table version is 13, local router ID is 10.1.1.99
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
*> 10.1.1.0/24 0.0.0.0 0 32768 i
*> 172.17.1.0/24 192.168.1.1 0 0 45000 i
Table 25 describes the significant fields shown in the display.
Table 25 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.
|
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:
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.
|
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.
|
show ip bgp (4-Byte Autonomous System Numbers): Example
The following example 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.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, or a later release.
BGP table version is 4, local router ID is 172.17.1.99
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
*> 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.17.1.0/24 0.0.0.0 0 32768 i
show ip bgp ip-address: Example
The following example displays information about the 192.168.1.0 entry in the BGP routing table:
Router B# show ip bgp 192.168.1.0
BGP routing table entry for 192.168.1.0/24, version 48
Paths: (2 available, best #2, table Default-IP-Routing-Table)
Advertised to update-groups:
172.16.1.1 from 172.16.1.1 (10.1.1.1)
Origin incomplete, metric 0, localpref 100, valid, external, multipath, best
Extended Community: 0x0:0:0
172.16.2.2 from 172.16.2.2 (10.2.2.2)
Origin incomplete, metric 0, localpref 100, valid, external, multipath, best
Extended Community: 0x0:0:0
Table 26 describes the significant fields shown in the display.
Table 26 show ip bgp 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 loadsharing 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.
|
show ip bgp all: Example
The following example output from the show ip bgp command entered with the all keyword. Information about all configured address families is displayed.
For address family: IPv4 Unicast *****
BGP table version is 27, local router ID is 1.1.1.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
*> 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 1.1.1.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
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 3.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.2.0/24 3.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.3.0/24 3.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.4.0/24 3.3.3.3 10 30 0 53285 33299 51178 47751 ?
*>i172.17.5.0/24 3.3.3.3 10 30 0 53285 33299 51178 47751 ?
For address family: IPv4 Multicast *****
BGP table version is 11, local router ID is 1.1.1.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
*> 10.40.40.0/26 172.16.14.110 2219 0 21 22 {51178,47751,27016} e
* 1.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
* 1.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
* 1.1.1.1 2563 0 15 20 1 {2} e
*> 10.40.40.192/26 1.1.1.1 2563 0 15 20 1 {2} e
*> 10.40.41.0/26 1.1.1.1 1209 0 15 20 1 {2} e
*>i10.102.0.0/16 1.1.1.1 300 500 0 5 4 {101,102} e
*>i10.103.0.0/16 1.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 1.1.1.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
* i45.0000.0002.0001.000c.00
* i46.0001.0000.0000.0000.0a00
* i47.0001.0000.0000.000b.00
* i47.0001.0000.0000.000e.00
show ip bgp longer-prefixes: Example
The following is example output from the show ip bgp command entered with the longer-prefixes keyword:
Router# 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 ?
show ip bgp shorter-prefixes: Example
The following is example output from the show ip bgp command entered with the shorter-prefixes keyword. An 8-bit prefix length is specified.
Router# show ip bgp 172.16.0.0/16 shorter-prefixes 8
*> 172.16.0.0 10.0.0.2 0 ?
show ip bgp prefix-list: Example
The following is example output from the show ip bgp command entered with the prefix-list keyword:
Router# 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 -
Origin codes:i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.0 10.0.0.2 0 ?
show ip bgp route-map: Example
The following is example output from the show ip bgp command entered with the route-map keyword:
Router# 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 -
Origin codes:i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.1.0 10.0.0.2 0 ?
Related Commands
Command
|
Description
|
bgp asnotation dot
|
Changes the default display and the regular expression match format of BGP 4-byte autonomous system numbers from asplain (decimal values) to dot notation.
|
router bgp
|
Configures the BGP routing process.
|
show ip bgp cidr-only
To display routes with classless interdomain routing (CIDR), use the show ip bgp cidr-only command in EXEC mode.
show ip bgp cidr-only
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show ip bgp cidr-only command in privileged EXEC mode:
Router# show ip bgp cidr-only
BGP table version is 220, local router ID is 172.16.73.131
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 192.168.0.0/8 172.16.72.24 0 1878 ?
*> 172.16.0.0/16 172.16.72.30 0 108 ?
Table 27 describes the significant fields shown in the display.
Table 27 show ip bgp cidr-only Field Descriptions
Field
|
Description
|
BGP table version is 220
|
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.
*—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.
|
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:
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.
|
Network
|
Internet address of the network the entry describes.
|
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 access server has some non-BGP route 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. At the end of the path is the origin code for the path:
i—The entry was originated with the IGP and advertised with a network router configuration command.
e—The route originated with EGP.
?—The origin of the path is not clear. Usually this is a path that is redistributed into BGP from an IGP.
|
show ip bgp community
To display routes that belong to specified BGP communities, use the show ip bgp community command in EXEC mode.
show ip bgp community community-number [exact]
Syntax Description
community-number
|
Valid value is a community number in the range from 1 to 4294967200, or AA:NN (autonomous system-community number/2-byte number), internet, no-export, local-as, or no-advertise.
|
exact
|
(Optional) Displays only routes that have the same specified communities.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.0
|
The local-as community was added.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show ip bgp community command in privileged EXEC mode:
Router# show ip bgp community 111:12345 local-as
BGP table version is 10, local router ID is 224.0.0.10
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
*> 172.16.2.2/32 10.43.222.2 0 0 222 ?
*> 10.0.0.0 10.43.222.2 0 0 222 ?
*> 10.43.0.0 10.43.222.2 0 0 222 ?
*> 10.43.44.44/32 10.43.222.2 0 0 222 ?
* 10.43.222.0/24 10.43.222.2 0 0 222 i
*> 172.17.240.0/21 10.43.222.2 0 0 222 ?
*> 192.168.212.0 10.43.222.2 0 0 222 i
*> 172.31.1.0 10.43.222.2 0 0 222 ?
Table 28 describes the significant fields shown in the display.
Table 28 show ip bgp community 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.
*—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.
|
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:
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.
|
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, this is the value of the interautonomous system metric. This field is frequently not used.
|
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.
|
show ip bgp community-list
To display routes that are permitted by the Border Gateway Protocol (BGP) community list, use the show ip bgp community-list command in user or privileged EXEC mode.
show ip bgp community-list {community-list-number | community-list-name [exact-match]}
Syntax Description
community-list-number
|
A standard or expanded community list number in the range from 1 to 500.
|
community-list-name
|
Community list name. The community list name can be standard or expanded.
|
exact-match
|
(Optional) Displays only routes that have an exact match.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.0(10)S
|
Named community list support was added.
|
12.0(16)ST
|
Named community lists support was integrated into Cisco IOS Release 12.0(16)ST.
|
12.1(9)E
|
Named community lists support was integrated into Cisco IOS Release 12.1(9)E.
|
12.2(8)T
|
Named community lists support was integrated into Cisco IOS Release 12.2(8)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB to support the Cisco 10000 Series Routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command requires you to specify an argument when used. The exact-match keyword is optional.
Examples
The following is sample output of the show ip bgp community-list command in privileged EXEC mode:
Router# show ip bgp community-list 20
BGP table version is 716977, local router ID is 192.168.32.1
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* i10.3.0.0 10.0.22.1 0 100 0 1800 1239 ?
*>i 10.0.16.1 0 100 0 1800 1239 ?
* i10.6.0.0 10.0.22.1 0 100 0 1800 690 568 ?
*>i 10.0.16.1 0 100 0 1800 690 568 ?
* i10.7.0.0 10.0.22.1 0 100 0 1800 701 35 ?
*>i 10.0.16.1 0 100 0 1800 701 35 ?
* 10.92.72.24 0 1878 704 701 35 ?
* i10.8.0.0 10.0.22.1 0 100 0 1800 690 560 ?
*>i 10.0.16.1 0 100 0 1800 690 560 ?
* 10.92.72.24 0 1878 704 701 560 ?
* i10.13.0.0 10.0.22.1 0 100 0 1800 690 200 ?
*>i 10.0.16.1 0 100 0 1800 690 200 ?
* 10.92.72.24 0 1878 704 701 200 ?
* i10.15.0.0 10.0.22.1 0 100 0 1800 174 ?
*>i 10.0.16.1 0 100 0 1800 174 ?
* i10.16.0.0 10.0.22.1 0 100 0 1800 701 i
*>i 10.0.16.1 0 100 0 1800 701 i
* 10.92.72.24 0 1878 704 701 i
Table 29 describes the significant fields shown in the display.
Table 29 show ip bgp community-list 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.
*—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.
|
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:
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.
|
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, this is the value of the interautonomous system metric. This field is frequently not used.
|
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.
|
show ip bgp dampened-paths
To display BGP dampened routes, use the show ip bgp dampened-paths command in EXEC mode.
show ip bgp dampened-paths
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
On the Cisco 10000 series router, use the show ip bgp dampening dampened-paths command to display BGP dampened routes.
Examples
The following is sample output from the show ip bgp dampened-paths command in privileged EXEC mode:
Router# show ip bgp dampened-paths
BGP table version is 10, local router ID is 172.29.232.182
Status codes: s suppressed, d damped, h history, * valid, > best, i -
Origin codes: i - IGP, e - EGP, ? - incomplete
*d 10.0.0.0 172.16.232.177 00:18:4 100 ?
*d 10.2.0.0 172.16.232.177 00:28:5 100 ?
Table 30 describes the significant fields shown in the display.
Table 30 show ip bgp dampened-paths Field Descriptions
Field
|
Description
|
BGP table version
|
Internal version number of the table. This number is incremented whenever the table changes.
|
local router
|
IP address of the router where route dampening is enabled.
|
*d
|
Route to the network indicated is dampened.
|
From
|
IP address of the peer that advertised this path.
|
Reuse
|
Time (in hours:minutes:seconds) after which the path will be made available.
|
Path
|
Autonomous system path of the route that is being dampened.
|
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
clear ip bgp dampening
|
Clears BGP route dampening information and unsuppresses the suppressed routes.
|
show ip bgp dampening dampened-paths
To display Border Gateway Protocol (BGP) dampened routes on the Cisco 10000 series router, use the show ip bgp dampening dampened-paths command in EXEC mode.
show ip bgp dampening dampened-paths [community-list-number | community-list-name
[exact-match]]
Syntax Description
community-list-number
|
(Optional) Community list number. The range is from 1 to 500.
|
community-list-name
|
(Optional) Community list name.
|
exact-match
|
(Optional) Displays only routes that have an exact match.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
Usage Guidelines
For router platforms other than the Cisco 10000 series router, use the show ip bgp dampened-paths command to display BGP dampened routes.
Examples
The following example show how to display BGP dampened routes information:
Router# show ip bgp dampening dampened-paths
BGP table version is 10, local router ID is 172.29.232.182
Status codes: s suppressed, d damped, h history, * valid, > best, i -
Origin codes: i - IGP, e - EGP, ? - incomplete
*d 10.0.0.0 172.16.232.177 00:18:4 100 ?
*d 10.2.0.0 172.16.232.177 00:28:5 100 ?
Table 31 describes the significant fields shown in the display.
Table 31 show ip bgp dampening dampened-paths 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 where route dampening is enabled.
|
*d
|
Route to the network indicated is dampened.
|
From
|
IP address of the peer that advertised this path.
|
Reuse
|
Time (in hours:minutes:seconds) after which the path will be made available.
|
Path
|
Autonomous system (AS) path of the route that is being dampened.
|
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
clear ip bgp dampening
|
Clears BGP route dampening information and unsuppresses the suppressed routes.
|
show dampening interface
|
Displays a summary of the dampening parameters and status.
|
show ip bgp dampening flap-statistics
To display Border Gateway Protocol (BGP) flap statistics for all paths on the Cisco 10000 series router, use the show ip bgp dampening flap-statistics command in privileged EXEC mode.
show ip bgp dampening flap-statistics [ip-address [mask] | cidr-only | filter-list
access-list-number | injected-paths | labels | prefix-list prefix-list | quote-regexp regexp |
regexp regexp | route-map route-map-name | template {peer-policy template-name |
peer-session template-name}]
Syntax Description
ip-address
|
Specifies the IP address for the flap statistics you want to display.
|
mask
|
Specifies the mask to filter or match hosts that are part of the specified network.
|
cidr-only
|
Displays flap statistics for routes with classless interdomain routing (CIDR).
|
filter-list access-list-number
|
Displays flap statistics for routes that conform to the specified autonomous system (AS) path access list number.
|
injected-paths
|
Displays flap statistics for all injected paths.
|
labels
|
Displays flap statistics for IPv4 Network Layer Reachability Information (NLRI) labels.
|
prefix-list prefix-list
|
Filters output based on the specified prefix list.
|
quote-regexp regexp
|
Filters output based on the specified quoted expression.
|
regexp regexp
|
Filters output based on the specified regular expression.
|
route-map route-map-name
|
Filters output based on the specified route map.
|
template
|
Displays peer-policy or peer-session template information.
|
peer-policy template-name
|
Used with the template keyword, displays peer-policy template information for the specified template name.
|
peer-session template-name
|
Used with the template keyword, displays peer-session template information for the specified template name.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
Usage Guidelines
For router platforms other than the Cisco 10000 series router, use the show ip bgp flap-statistics command to display BGP flap statistics.
Examples
The following example show how to display the BGP flap statistics for routes with nonnatural network masks (CIDR):
Router# show ip bgp dampening flap-statistics cidr-only
BGP table version is 56, local router ID is 100.10.7.11
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
*>i205.0.5.0/30 100.10.5.11 0 100 0 i
*>i205.0.5.4/30 205.0.5.1 0 100 0 105 ?
*>i205.10.5.9/32 205.0.5.1 2 100 0 105 ?
*>i205.10.5.13/32 205.0.5.1 2 100 0 105 ?
*>i206.0.6.0/30 100.10.5.11 0 100 0 i
*>i206.0.6.4/30 206.0.6.1 0 100 0 106 ?
*>i206.10.6.9/32 206.0.6.1 2 100 0 106 ?
*>i206.10.6.13/32 206.0.6.1 2 100 0 106 ?
*> 207.0.7.0/30 0.0.0.0 0 32768 i
*> 207.0.7.4/30 207.0.7.1 0 0 107 ?
*> 207.10.7.9/32 207.0.7.1 2 0 107 ?
*> 207.10.7.13/32 207.0.7.1 2 0 107 ?
*> 208.0.8.0/30 0.0.0.0 0 32768 i
*> 208.0.8.4/30 208.0.8.1 0 0 108 ?
*> 208.10.8.9/32 208.0.8.1 2 0 108 ?
*> 208.10.8.13/32 208.0.8.1 2 0 108 ?
Table 32 describes the significant fields shown in the display.
Table 32 show ip bgp dampening flap-statistics cidr-only 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 where route dampening is enabled.
|
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.
*—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.
|
Network
|
Internet address of the network the entry describes.
|
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 access server has some non-BGP route 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. At the end of the path is the origin code for the path:
i—The entry was originated with the IGP and advertised with a network router configuration command.
e—The route originated with EGP.
?—The origin of the path is not clear. Usually this is a path that is redistributed into BGP from an IGP.
|
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
clear ip bgp flap-statistics
|
Clears BGP flap statistics.
|
show dampening interface
|
Displays a summary of the dampening parameters and status.
|
show ip bgp dampening parameters
To display detailed Border Gateway Protocol (BGP) dampening information on the Cisco 10000 series router, use the show ip bgp dampening parameters command in privileged EXEC mode.
show ip bgp dampening parameters
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2S
|
This command was introduced.
|
Examples
The following example shows how to display detailed BGP dampening information:
Router# show ip bgp dampening parameters
dampening 15 750 2000 60 (DEFAULT)
Half-life time : 15 mins Decay Time : 2320 secs
Max suppress penalty: 12000 Max suppress time: 60 mins
Table 33 describes the significant fields shown in the display.
Table 33 show ip bgp dampening parameters Field Descriptions
Field
|
Description
|
Half-life time
|
Time after which a penalty is decreased, in minutes. Once the interface has been assigned a penalty, the penalty is decreased by half after the half-life period. The process of reducing the penalty happens every 5 seconds. The range of the half-life period is 1 to 45 minutes. The default is 1 minute.
|
Decay Time
|
Penalty value below which an unstable interface is unsuppressed, in seconds. The process of unsupressing routers occurs at 10 second increments. The range of the reuse value is 1 to 20000 seconds. The default value is 750 seconds.
|
Max suppress penalty
|
Limit at which an interface is suppressed when its penalty exceeds that limit, in seconds. The default value is 2000 seconds.
|
Max suppress time
|
Maximum time that an interface can be suppressed, in minutes. This value effectively acts as a ceiling that the penalty value cannot exceed. The default value is four times the half-life period.
|
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
clear ip bgp dampening
|
Clears BGP dampening information.
|
show dampening interface
|
Displays a summary of the dampening parameters and status.
|
show ip bgp filter-list
To display routes that conform to a specified filter list, use the show ip bgp filter-list command in EXEC mode.
show ip bgp filter-list access-list-number
Syntax Description
access-list-number
|
Number of an autonomous system path access list. It can be a number from 1 to 199, or on the Cisco 10000 series router this is a number from 1 to 500.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show ip bgp filter-list command in privileged EXEC mode:
Router# show ip bgp filter-list 2
BGP table version is 1738, local router ID is 172.16.72.24
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 172.16.0.0 172.16.72.30 0 109 108 ?
* 172.16.1.0 172.16.72.30 0 109 108 ?
* 172.16.11.0 172.16.72.30 0 109 108 ?
* 172.16.14.0 172.16.72.30 0 109 108 ?
* 172.16.15.0 172.16.72.30 0 109 108 ?
* 172.16.16.0 172.16.72.30 0 109 108 ?
* 172.16.17.0 172.16.72.30 0 109 108 ?
* 172.16.18.0 172.16.72.30 0 109 108 ?
* 172.16.19.0 172.16.72.30 0 109 108 ?
* 172.16.24.0 172.16.72.30 0 109 108 ?
* 172.16.29.0 172.16.72.30 0 109 108 ?
* 172.16.30.0 172.16.72.30 0 109 108 ?
* 172.16.33.0 172.16.72.30 0 109 108 ?
* 172.16.35.0 172.16.72.30 0 109 108 ?
* 172.16.36.0 172.16.72.30 0 109 108 ?
* 172.16.37.0 172.16.72.30 0 109 108 ?
* 172.16.38.0 172.16.72.30 0 109 108 ?
* 172.16.39.0 172.16.72.30 0 109 108 ?
Table 34 describes the significant fields shown in the display.
Table 34 show ip bgp filter-list 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.
*—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.
|
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:
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.
|
Network
|
Internet address of the network the entry describes.
|
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 route to this network.
|
Metric
|
If shown, this is the value of the interautonomous system metric. This field is frequently not used.
|
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. At the end of the path is the origin code for the path:
i—The entry was originated with the IGP and advertised with a network router configuration command.
e—The route originated with EGP.
?—The origin of the path is not clear. Usually this is a path that is redistributed into BGP from an IGP.
|
show ip bgp flap-statistics
To display BGP flap statistics, use the show ip bgp flap-statistics command in EXEC mode.
show ip bgp flap-statistics [regexp regexp | filter-list access-list | ip-address mask
[longer-prefix]]
Syntax Description
regexp regexp
|
(Optional) Clears flap statistics for all the paths that match the regular expression.
|
filter-list access-list
|
(Optional) Clears flap statistics for all the paths that pass the access list.
|
ip-address
|
(Optional) Clears flap statistics for a single entry at this IP address.
|
mask
|
(Optional) Network mask applied to the value.
|
longer-prefix
|
(Optional) Displays flap statistics for more specific entries.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
If no arguments or keywords are specified, the router displays flap statistics for all routes.
Examples
The following is sample output from the show ip bgp flap-statistics command in privileged EXEC mode:
Router# show ip bgp flap-statistics
BGP table version is 10, local router ID is 172.29.232.182
Status codes: s suppressed, d damped, h history, * valid, > best, i -
Origin codes: i - IGP, e - EGP, ? - incomplete
Network From Flaps Duration Reuse Path
*d 10.0.0.0 172.29.232.177 4 00:13:31 00:18:10 100
*d 10.2.0.0 172.29.232.177 4 00:02:45 00:28:20 100
Table 35 describes the significant fields shown in the display.
Table 35 show ip bgp flap-statistics 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 where route dampening is enabled.
|
Network
|
Route to the network indicated is dampened.
|
From
|
IP address of the peer that advertised this path.
|
Flaps
|
Number of times the route has flapped.
|
Duration
|
Time (in hours:minutes:seconds) since the router noticed the first flap.
|
Reuse
|
Time (in hours:minutes:seconds) after which the path will be made available.
|
Path
|
Autonomous system path of the route that is being dampened.
|
Related Commands
Command
|
Description
|
bgp dampening
|
Enables BGP route dampening or changes various BGP route dampening factors.
|
clear ip bgp flap-statistics
|
Clears BGP flap statistics.
|
show ip bgp inconsistent-as
To display routes with inconsistent originating autonomous systems, use the show ip bgp inconsistent-as command in EXEC mode.
show ip bgp inconsistent-as
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show ip bgp inconsistent-as command in privileged EXEC mode:
Router# show ip bgp inconsistent-as
BGP table version is 87, local router ID is 172.19.82.53
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 10.1.0.0 172.29.232.55 0 0 300 88 90 99 ?
*> 172.29.232.52 2222 0 400 ?
* 172.29.0.0 172.29.232.55 0 0 300 90 99 88 200 ?
*> 172.29.232.52 2222 0 400 ?
* 10.200.199.0 172.29.232.55 0 0 300 88 90 99 ?
*> 172.29.232.52 2222 0 400 ?
show ip bgp injected-paths
To display all the injected paths in the Border Gateway Protocol (BGP) routing table, use the show ip bgp injected-paths command in user or privileged EXEC mode.
show ip bgp injected-paths
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(14)ST
|
This command was introduced.
|
12.2(4)T
|
This command was integrated into Cisco IOS Release 12.2(4)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
Examples
The following is sample output from the show ip bgp injected-paths command in EXEC mode:
Router# show ip bgp injected-paths
BGP table version is 11, local router ID is 10.0.0.1
Status codes:s suppressed, d damped, h history, * valid, > best, i -
Origin codes:i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 172.16.0.0 10.0.0.2 0 ?
*> 172.17.0.0/16 10.0.0.2 0 ?
Table 36 describes the significant fields shown in the display.
Table 36 show ip bgp injected-paths 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.
|
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:
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.
|
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
|
The Multi Exit Discriminator (MED) metric for the path. (The name of this metric for BGP versions 2 and 3 is INTER_AS.)
|
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.
|
show ip bgp ipv4
To display entries in the IP version 4 (IPv4) Border Gateway Protocol (BGP) routing table, use the show ip bgp ipv4 command in privileged EXEC mode.
show ip bgp ipv4 {mdt {all | rd | vrf} | multicast | tunnel | unicast}
Syntax Description
mdt
|
Displays entries for multicast discovery tree sessions.
|
all
|
Displays all multicast discovery tree information.
|
rd
|
Displays information about the VPN route distinguisher in the MDT session.
|
vrf
|
Displays information about the VRF in the MDT session.
|
multicast
|
Displays entries for multicast sessions.
|
tunnel
|
Displays entries for tunnel sessions.
|
unicast
|
Displays entries for unicast sessions.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(7)T
|
This command was introduced.
|
12.0(29)S
|
The mdt keyword was added.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
12.4(20)T
|
The mdt keyword was added.
|
Examples
The following is sample output from the show ip bgp ipv4 unicast command:
Router# show ip bgp ipv4 unicast
BGP table version is 4, local router ID is 10.0.40.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
*> 10.10.10.0/24 172.16.10.1 0 0 300 i
*> 10.10.20.0/24 172.16.10.1 0 0 300 i
* 10.20.10.0/24 172.16.10.1 0 0 300 i
The following is sample output from the show ip bgp ipv4 multicast command:
Router# show ip bgp ipv4 multicast
BGP table version is 4, local router ID is 10.0.40.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
*> 10.10.10.0/24 172.16.10.1 0 0 300 i
*> 10.10.20.0/24 172.16.10.1 0 0 300 i
* 10.20.10.0/24 172.16.10.1 0 0 300 i
Table 37 describes the significant fields shown in the display.
Table 37 show ip bgp ipv4 unicast 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 damped.
•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.
|
Origin codes
|
Origin of the entry. The origin code is displayed at the end of each line in the table. It can be one of the following values:
•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.
|
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.
|
Related Commands
Command
|
Description
|
clear ip bgp ipv4 mdt
|
Resets multicast discovery tree IPv4 BGP address-family sessions.
|
show ip bgp
|
Displays entries in the BGP routing table.
|
show ip bgp ipv4 multicast
To display IP Version 4 multicast database-related information, use the show ip bgp ipv4 multicast command in EXEC mode.
show ip bgp ipv4 multicast [command]
Syntax Description
command
|
(Optional) Any multiprotocol BGP command supported by the show ip bgp ipv4 multicast command.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(7)T
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Use this command in conjunction with the show ip rpf command to determine if IP multicast routing is using multiprotocol BGP routes.
To determine which multiprotocol BGP commands are supported by the show ip bgp ipv4 multicast command, enter the following command while in EXEC mode:
Router# show ip bgp ipv4 multicast ?
The show ip bgp ipv4 multicast command replaces the show ip mbgp command.
Examples
The following is sample output from the show ip bgp ipv4 multicast command:
Router# show ip bgp ipv4 multicast
MBGP table version is 6, local router ID is 192.168.200.66
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
*> 10.0.20.16/28 0.0.0.0 0 0 32768 i
*> 10.0.35.16/28 0.0.0.0 0 0 32768 i
*> 10.0.36.0/28 0.0.0.0 0 0 32768 i
*> 10.0.48.16/28 0.0.0.0 0 0 32768 i
*> 10.2.0.0/16 0.0.0.0 0 0 32768 i
*> 10.2.1.0/24 0.0.0.0 0 0 32768 i
*> 10.2.2.0/24 0.0.0.0 0 0 32768 i
*> 10.2.3.0/24 0.0.0.0 0 0 32768 i
*> 10.2.7.0/24 0.0.0.0 0 0 32768 i
*> 10.2.8.0/24 0.0.0.0 0 0 32768 i
*> 10.2.10.0/24 0.0.0.0 0 0 32768 i
*> 10.2.11.0/24 0.0.0.0 0 0 32768 i
*> 10.2.12.0/24 0.0.0.0 0 0 32768 i
*> 10.2.13.0/24 0.0.0.0 0 0 32768 i
Table 38 describes the significant fields shown in the display.
Table 38 show ip bgp ipv4 multicast Field Descriptions
Field
|
Description
|
MBGP 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 is historical.
*—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.
|
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:
i—Entry originated from an Interior Gateway Protocol (IGP) and was advertised with a network router configuration or address family 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.
|
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.
|
Related Commands
Command
|
Description
|
show ip rpf
|
Displays how IP multicast routing does RPF.
|
show ip bgp ipv4 multicast summary
To display a summary of IP Version 4 multicast database-related information, use the show ip bgp ipv4 multicast summary command in EXEC mode.
show ip bgp ipv4 multicast summary
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(7)T
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
The show ip bgp ipv4 multicast summary command replaces the show ip mbgp summary command.
Examples
The following is sample output from the show ip bgp ipv4 multicast summary command:
Router# show ip bgp ipv4 multicast summary
BGP router identifier 10.0.33.34, local AS number 34
BGP table version is 5, main routing table version 1
4 network entries and 6 paths using 604 bytes of memory
5 BGP path attribute entries using 260 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
2 BGP community entries using 48 bytes of memory
2 BGP route-map cache entries using 32 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP activity 8/28 prefixes, 12/0 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.0.33.35 4 35 624 624 5 0 0 10:13:46 3
Table 39 describes the significant fields shown in the display.
Table 39 show ip bgp ipv4 multicast summary Field Descriptions
Field
|
Description
|
Neighbor
|
IP address of configured neighbor in the multicast routing table.
|
V
|
Version of multiprotocol BGP used.
|
AS
|
Autonomous system to which the neighbor belongs.
|
MsgRcvd
|
Number of messages received from the neighbor.
|
MsgSent
|
Number of messages sent to the neighbor.
|
TblVer
|
Number of the table version, which is incremented each time the table changes.
|
InQ
|
Number of messages received in the input queue.
|
OutQ
|
Number of messages ready to go in the output queue.
|
Up/Down
|
Days and hours that the neighbor has been up or down (no information in the State column means the connection is up).
|
State/PfxRcd
|
State of the neighbor/number of routes received. If no state is indicated, the state is up.
|
Related Commands
Command
|
Description
|
show ip rpf
|
Displays how IP multicast routing does RPF.
|
show ip bgp l2vpn
To display Layer 2 Virtual Private Network (L2VPN) address family information from the Border Gateway Protocol (BGP) table, use the show ip bgp l2vpn command in user EXEC or privileged EXEC mode.
With BGP show Command Argument
show ip bgp l2vp vpls {all | rd route-distinguisher} [bgp-keyword]
With IP Prefix and Mask Length Syntax
show ip bgp l2vp vpls {all | rd route-distinguisher} [ip-prefix/length [bestpath] [longer-prefixes
[injected]] [multipaths] [shorter-prefixes [mask-length]] [subnets]]
With Network Address Syntax
show ip bgp l2vp vpls {all | rd route-distinguisher} [network-address [mask | bestpath |
multipaths] [bestpath] [longer-prefixes [injected]] [multipaths] [shorter-prefixes
[mask-length]] [subnets]]
Syntax Description
vpls
|
Displays L2VPN address family database information for the Virtual Private LAN Service (VPLS) subsequent address family identifier (SAFI).
|
all
|
Displays the complete L2VPN database.
|
rd route-distinguisher
|
Displays prefixes that match the specified route distinguisher.
|
bgp-keyword
|
(Optional) Argument representing a show ip bgp command keyword that can be added to this command. See Table 40.
|
ip-prefix/length
|
(Optional) The IP prefix address (in dotted decimal format) and the length of the mask (0 to 32). The slash mark must be included.
|
bestpath
|
(Optional) Displays the best path for the specified prefix.
|
longer-prefixes
|
(Optional) Displays the route and more specific routes.
|
injected
|
(Optional) Displays more specific routes that were injected because of the specified prefix.
|
multipaths
|
(Optional) Displays the multipaths for the specified prefix.
|
shorter-prefixes
|
(Optional) Displays the less specific routes.
|
mask-length
|
(Optional) The length of the mask as a number in the range from 0 to 32. Prefixes longer than the specified mask length are displayed.
|
subnets
|
(Optional) Displays the subnet routes for the specified prefix.
|
network-address
|
(Optional) The IP address of a network in the BGP routing table.
|
mask
|
(Optional) The mask of the network address, in dotted decimal format.
|
Command Default
If no arguments or keywords are specified, this command displays the complete L2VPN database.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(33)SRB
|
This command was introduced.
|
Usage Guidelines
Table 40 displays optional show ip bgp command keywords that can be configured with the show ip bgp l2vpn command. Replace the bgp-keyword argument with the appropriate keyword from the table. For more details about each command in its show ip bgp bgp-keyword form, see the Cisco IOS IP Routing Protocols Command Reference.
Table 40 Optional show ip bgp Command Keywords and Descriptions
Keyword
|
Description
|
community
|
Displays routes that match a specified community
|
community-list
|
Displays routes that match a specified community list.
|
dampening
|
Displays paths suppressed because of dampening (BGP route from peer is up and down).
|
extcommunity-list
|
Displays routes that match a specified extcommunity list.
|
filter-list
|
Displays routes that conform to the filter list.
|
inconsistent-as
|
Displays only routes that have inconsistent autonomous systems of origin.
|
neighbors
|
Displays details about TCP and BGP neighbor connections.
|
oer-paths
|
Displays all OER-managed path information.
|
paths [regexp]
|
Displays autonomous system path information. If the optional regexp argument is entered, the autonomous system paths that are displayed match the autonomous system path regular expression.
|
peer-group
|
Displays information about peer groups.
|
pending-prefixes
|
Displays prefixes that are pending deletion.
|
prefix-list
|
Displays routes that match a specified prefix list.
|
quote-regexp
|
Displays routes that match the quoted autonomous system path regular expression.
|
regexp
|
Displays routes that match the autonomous system path regular expression.
|
replication
|
Displays the replication status update groups.
|
route-map
|
Displays routes that match the specified route map.
|
rt-filter-list
|
Displays the specified inbound route target filter list.
|
summary
|
Displays a summary of BGP neighbor status.
|
update-group
|
Displays information on update groups.
|
Examples
The following example shows output for the show ip bgp l2vpn command when the vpls and all keywords are used to display the complete L2VPN database:
Router# show ip bgp l2vpn vpls all
BGP table version is 5, local router ID is 192.168.3.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
Route Distinguisher: 45000:100
*> 45000:100:172.17.1.1/96
*>i45000:100:172.18.2.2/96
Route Distinguisher: 45000:200
*> 45000:200:172.17.1.1/96
*>i45000:200:172.18.2.2/96
Table 41 describes the significant fields shown in the display.
Table 41 show ip bgp l2vpn vpls all 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 is a historical entry.
•*—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 failed to install in the routing information base (RIB) table.
•S—The table entry is Stale (old). This entry is useful in BGP graceful restart situations.
|
Origin codes
|
Origin of the entry. The origin code is displayed at the end of each line in the table. It can be one of the following values:
•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.
|
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.
|
Route Distinguisher
|
Route distinguisher that identifies a set of routing and forwarding tables used in virtual private networks.
|
The following example shows output for the show ip bgp l2vpn command when the vpls and rd keywords are used to display the L2VPN information that matches the route distinguisher 45000:100. Note that the information displayed is a subset of the information displayed using the all keyword.
Router# show ip bgp l2vpn vpls rd 45000:100
BGP table version is 5, local router ID is 192.168.3.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
Route Distinguisher: 45000:100
*> 45000:100:172.17.1.1/96
*>i45000:100:172.18.2.2/96
Related Commands
Command
|
Description
|
address-family l2vpn
|
Enters address family configuration mode to configure a routing session using L2VPN endpoint provisioning information.
|
show ip bgp neighbors
To display information about Border Gateway Protocol (BGP) and TCP connections to neighbors, use the show ip bgp neighbors command in user or privileged EXEC mode.
show ip bgp neighbors [ip-address [advertised-routes | dampened-routes | flap-statistics |
paths [reg-exp] | received prefix-filter | received-routes | routes | policy [detail]]]
Syntax Description
ip-address
|
(Optional) IP address of a neighbor. If this argument is omitted, information about all neighbors is displayed.
|
advertised-routes
|
(Optional) Displays all routes that have been advertised to neighbors.
|
dampened-routes
|
(Optional) Displays the dampened routes received from the specified neighbor.
|
flap-statistics
|
(Optional) Displays the flap statistics of the routes learned from the specified neighbor (for external BGP peers only).
|
paths reg-exp
|
(Optional) Displays autonomous system paths learned from the specified neighbor. An optional regular expression can be used to filter the output.
|
received prefix-filter
|
(Optional) Displays the prefix-list (outbound route filter [ORF]) sent from the specified neighbor.
|
received-routes
|
(Optional) Displays all received routes (both accepted and rejected) from the specified neighbor.
|
routes
|
(Optional) Displays all routes that are received and accepted. The output displayed when this keyword is entered is a subset of the output displayed by the received-routes keyword.
|
policy
|
(Optional) Displays the policies applied to this neighbor per address family.
|
detail
|
(Optional) Displays detailed policy information such as route maps, prefix lists, community lists, access control lists (ACLs), and autonomous system path filter lists.
|
Command Default
The output of this command displays information for all neighbors.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
0S Release
|
Modification
|
12.0(18)S
|
The output was modified to display the no-prepend configuration option, and this command was integrated into Cisco IOS Release 12.0(18)S.
|
12.0(21)ST
|
The output was modified to display Multiprotocol Label Switching (MPLS) label information.
|
12.0(22)S
|
Support for the BGP graceful restart capability was integrated into the output. Support for the Cisco 12000 series routers (Engine 0 and Engine 2) was also added.
|
12.0(25)S
|
The policy and detail keywords were added.
|
12.0(27)S
|
The command output was modified to support the BGP TTL Security Check feature and to display explicit-null label information.
|
12.0(31)S
|
Support for the Bidirectional Forwarding Detection (BFD) feature was integrated into the output.
|
12.0(32)S12
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.0(32)SY8
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.0(33)S3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
S Release
|
Modification
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(17b)SXA
|
This command was integrated into Cisco IOS Release 12.2(17b)SXA.
|
12.2(18)SXE
|
Support for the Bidirectional Forwarding Detection (BFD) feature was integrated into the output.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA, and the output was modified to support BGP TCP path MTU discovery.
|
12.2(33)SRB
|
Support for the policy and detail keywords was integrated into Cisco IOS Release 12.2(33)SRB.
|
12.2(33)SXH
|
The output was modified to support BGP dynamic neighbors.
|
12.2(33)SRC
|
The output was modified to support BGP graceful restart per peer.
|
12.2(33)SB
|
The output was modified to support the BFD and the BGP graceful restart per peer features, and support for the policy and detail keywords was integrated into Cisco IOS Release 12.2(33)SB.
|
12.2(33)SXI1
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
Mainline and T Release
|
Modification
|
10.0
|
This command was introduced.
|
11.2
|
The received-routes keyword was added.
|
12.2(4)T
|
The received and prefix-filter keywords were added, and this command was integrated into Cisco IOS Release 12.2(4)T.
|
12.2(15)T
|
Support for the BGP graceful restart capability was integrated into the output.
|
12.3(7)T
|
This command was modified. The command output was modified to support the BGP TTL Security Check feature and to display explicit-null label information.
|
12.4(4)T
|
This command was modified. Support for the Bidirectional Forwarding Detection (BFD) feature was integrated into the output.
|
12.4(11)T
|
This command was modified. Support for the policy and detail keywords was integrated into Cisco IOS Release 12.4(11)T.
|
12.4(20)T
|
This command was modified. The output was modified to support BGP TCP path MTU discovery.
|
12.4(24)T
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
Cisco IOS XE Release 2
|
Modification
|
Cisco IOS XE Release 2.1
|
This command was integrated into Cisco IOS XE Release 2.1.
|
Cisco IOS XE Release 2.3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
Cisco IOS XE Release 2.4
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Usage Guidelines
Use the show ip bgp neighbors command to display BGP and TCP connection information for neighbor sessions. For BGP, this includes detailed neighbor attribute, capability, path, and prefix information. For TCP, this includes statistics related to BGP neighbor session establishment and maintenance.
Prefix activity is displayed based on the number of prefixes that are advertised and withdrawn. Policy denials display the number of routes that were advertised but then ignored based on the function or attribute that is displayed in the output.
In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538 for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the bgp asnotation dot command followed by the clear ip bgp * command to perform a hard reset of all current BGP sessions.
In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, the Cisco implementation of 4-byte autonomous system numbers uses asdot—1.2 for example—as the only configuration format, regular expression match, and output display, with no asplain support.
Cisco IOS Releases 12.0(25)S, 12.4(11)T, 12.2(33)SRB, 12.2(33)SB, and Later Releases
When BGP neighbors use multiple levels of peer templates, it can be difficult to determine which policies are applied to the neighbor.
In Cisco IOS Releases 12.0(25)S, 12.4(11)T, 12.2(33)SRB, 12.2(33)SB, and later releases, the policy and detail keywords were added to display the inherited policies and the policies configured directly on the specified neighbor. Inherited policies are policies that the neighbor inherits from a peer-group or a peer-policy template.
Examples
Example output is different for the various keywords available for the show ip bgp neighbors command. Examples using the various keywords appear in the following sections:
•show ip bgp neighbors: Example
•show ip bgp neighbors (4-Byte Autonomous System Numbers): Example
•show ip bgp neighbors advertised-routes: Example
•show ip bgp neighbors paths: Example
•show ip bgp neighbors received prefix-filter: Example
•show ip bgp neighbors policy: Example
•Cisco IOS Release 12.0(31)S, 12.4(4)T, 12.2(18)SXE, and 12.2(33)SB: Example
•Cisco IOS Release 12.2(33)SRA and 12.4(20)T: Example
•Cisco IOS Release 12.2(33)SXH: Example
•Cisco IOS Releases 12.2(33)SRC and 12.2(33)SB: Example
show ip bgp neighbors: Example
The following example shows output for the BGP neighbor at 10.108.50.2. This neighbor is an internal BGP (iBGP) peer. This neighbor supports the route refresh and graceful restart capabilities.
Router# show ip bgp neighbors 10.108.50.2
BGP neighbor is 10.108.50.2, remote AS 1, internal link
BGP version 4, remote router ID 192.168.252.252
BGP state = Established, up for 00:24:25
Last read 00:00:24, last write 00:00:24, hold time is 180, keepalive interval is
60 seconds
Route refresh: advertised and received(old & new)
MPLS Label capability: advertised and received
Graceful Restart Capability: advertised
Address family IPv4 Unicast: advertised and received
Default minimum time between advertisement runs is 5 seconds
For address family: IPv4 Unicast
BGP table version 1, neighbor version 1/0
Index 1, Offset 0, Mask 0x2
Prefix activity: ---- ----
Local Policy Denied Prefixes: -------- -------
Number of NLRIs in the update sent: max 0, min 0
Connections established 3; dropped 2
Last reset 00:24:26, due to Peer closed the session
External BGP neighbor may be up to 2 hops away.
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Connection is ECN Disabled
Local host: 10.108.50.1, Local port: 179
Foreign host: 10.108.50.2, Foreign port: 42698
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x68B944):
Timer Starts Wakeups Next
iss: 3915509457 snduna: 3915510016 sndnxt: 3915510016 sndwnd: 15826
irs: 233567076 rcvnxt: 233567616 rcvwnd: 15845 delrcvwnd: 539
SRTT: 292 ms, RTTO: 359 ms, RTV: 67 ms, KRTT: 0 ms
minRTT: 12 ms, maxRTT: 300 ms, ACK hold: 200 ms
Flags: passive open, nagle, gen tcbs
Datagrams (max data segment is 1460 bytes):
Rcvd: 38 (out of order: 0), with data: 27, total data bytes: 539
Sent: 45 (retransmit: 0, fastretransmit: 0, partialack: 0, Second Congestion: 08
Table 42 describes the significant fields shown in the display. Fields that are preceded by the asterisk character (*) are displayed only when the counter has a nonzero value.
Table 42 show ip bgp neighbors Field Descriptions
Field
|
Description
|
BGP neighbor
|
IP address of the BGP neighbor and its autonomous system number.
|
remote AS
|
Autonomous system number of the neighbor.
|
local AS 300 no-prepend (not shown in display)
|
Verifies that the local autonomous system number is not prepended to received external routes. This output supports the hiding of the local autonomous systems when migrating autonomous systems.
|
internal link
|
"internal link" is displayed for iBGP neighbors. "external link" is displayed for external BGP (eBGP) neighbors.
|
BGP version
|
BGP version being used to communicate with the remote router.
|
remote router ID
|
IP address of the neighbor.
|
BGP state
|
Finite state machine (FSM) stage of session negotiation.
|
up for
|
Time, in hhmmss, that the underlying TCP connection has been in existence.
|
Last read
|
Time, in hhmmss, since BGP last received a message from this neighbor.
|
last write
|
Time, in hhmmss, since BGP last sent a message to this neighbor.
|
hold time
|
Time, in seconds, that BGP will maintain the session with this neighbor without receiving a messages.
|
keepalive interval
|
Time interval, in seconds, at which keepalive messages are transmitted to this neighbor.
|
Neighbor capabilities
|
BGP capabilities advertised and received from this neighbor. "advertised and received" is displayed when a capability is successfully exchanged between two routers.
|
Route Refresh
|
Status of the route refresh capability.
|
MPLS Label Capability
|
Indicates that MPLS labels are both sent and received by the eBGP peer.
|
Graceful Restart Capability
|
Status of the graceful restart capability.
|
Address family IPv4 Unicast
|
IP Version 4 unicast-specific properties of this neighbor.
|
Message statistics
|
Statistics organized by message type.
|
InQ depth is
|
Number of messages in the input queue.
|
OutQ depth is
|
Number of messages in the output queue.
|
Sent
|
Total number of transmitted messages.
|
Received
|
Total number of received messages.
|
Opens
|
Number of open messages sent and received.
|
notifications
|
Number of notification (error) messages sent and received.
|
Updates
|
Number of update messages sent and received.
|
Keepalives
|
Number of keepalive messages sent and received.
|
Route Refresh
|
Number of route refresh request messages sent and received.
|
Total
|
Total number of messages sent and received.
|
Default minimum time between...
|
Time, in seconds, between advertisement transmissions.
|
For address family:
|
Address family to which the following fields refer.
|
BGP table version
|
Internal version number of the table. This is the primary routing table with which the neighbor has been updated. The number increments when the table changes.
|
neighbor version
|
Number used by the software to track prefixes that have been sent and those that need to be sent.
|
...update-group
|
Number of update-group member for this address family.
|
Prefix activity
|
Prefix statistics for this address family.
|
Prefixes current
|
Number of prefixes accepted for this address family.
|
Prefixes total
|
Total number of received prefixes.
|
Implicit Withdraw
|
Number of times that a prefix has been withdrawn and readvertised.
|
Explicit Withdraw
|
Number of times that prefix has been withdrawn because it is no longer feasible.
|
Used as bestpath
|
Number of received prefixes installed as bestpaths.
|
Used as multipath
|
Number of received prefixes installed as multipaths.
|
* Saved (soft-reconfig)
|
Number of soft resets performed with a neighbor that supports soft reconfiguration. This field is displayed only if the counter has a nonzero value.
|
* History paths
|
This field is displayed only if the counter has a nonzero value.
|
* Invalid paths
|
Number of invalid paths. This field is displayed only if the counter has a nonzero value.
|
Local Policy Denied Prefixes
|
Prefixes denied due to local policy configuration. Counters are updated for inbound and outbound policy denials. The fields under this heading are displayed only if the counter has a nonzero value.
|
* route-map
|
Displays inbound and outbound route-map policy denials.
|
* filter-list
|
Displays inbound and outbound filter-list policy denials.
|
* prefix-list
|
Displays inbound and outbound prefix-list policy denials.
|
* Ext Community
|
Displays only outbound extended community policy denials.
|
* AS_PATH too long
|
Displays outbound AS-path length policy denials.
|
* AS_PATH loop
|
Displays outbound AS-path loop policy denials.
|
* AS_PATH confed info
|
Displays outbound confederation policy denials.
|
* AS_PATH contains AS 0
|
Displays outbound denials of AS 0.
|
* NEXT_HOP Martian
|
Displays outbound martian denials.
|
* NEXT_HOP non-local
|
Displays outbound non-local next-hop denials.
|
* NEXT_HOP is us
|
Displays outbound next-hop-self denials.
|
* CLUSTER_LIST loop
|
Displays outbound cluster-list loop denials.
|
* ORIGINATOR loop
|
Displays outbound denials of local originated routes.
|
* unsuppress-map
|
Displays inbound denials due to an unsuppress-map.
|
* advertise-map
|
Displays inbound denials due to an advertise-map.
|
* VPN Imported prefix
|
Displays inbound denials of VPN prefixes.
|
* Well-known Community
|
Displays inbound denials of well-known communities.
|
* SOO loop
|
Displays inbound denials due to site-of-origin.
|
* Bestpath from this peer
|
Displays inbound denials because the bestpath came from the local router.
|
* Suppressed due to dampening
|
Displays inbound denials because the neighbor or link is in a dampening state.
|
* Bestpath from iBGP peer
|
Deploys inbound denials because the bestpath came from an iBGP neighbor.
|
* Incorrect RIB for CE
|
Deploys inbound denials due to RIB errors for a CE router.
|
* BGP distribute-list
|
Displays inbound denials due to a distribute list.
|
Number of NLRIs...
|
Number of network layer reachability attributes in updates.
|
Connections established
|
Number of times a TCP and BGP connection has been successfully established.
|
dropped
|
Number of times that a valid session has failed or been taken down.
|
Last reset
|
Time since this peering session was last reset. The reason for the reset is displayed on this line.
|
External BGP neighbor may be... (not shown in the display)
|
Indicates that the BGP TTL security check is enabled. The maximum number of hops that can separate the local and remote peer is displayed on this line.
|
Connection state
|
Connection status of the BGP peer.
|
Connection is ECN Disabled
|
Explicit congestion notification status (enabled or disabled).
|
Local host: 10.108.50.1, Local port: 179
|
IP address of the local BGP speaker. BGP port number 179.
|
Foreign host: 10.108.50.2, Foreign port: 42698
|
Neighbor address and BGP destination port number.
|
Enqueued packets for retransmit:
|
Packets queued for retransmission by TCP.
|
Event Timers
|
TCP event timers. Counters are provided for starts and wakeups (expired timers).
|
Retrans
|
Number of times a packet has been retransmitted.
|
TimeWait
|
Time waiting for the retransmission timers to expire.
|
AckHold
|
Acknowledgment hold timer.
|
SendWnd
|
Transmission (send) window.
|
KeepAlive
|
Number of keepalive packets.
|
GiveUp
|
Number times a packet is dropped due to no acknowledgment.
|
PmtuAger
|
Path MTU discovery timer.
|
DeadWait
|
Expiration timer for dead segments.
|
iss:
|
Initial packet transmission sequence number.
|
snduna:
|
Last transmission sequence number that has not been acknowledged.
|
sndnxt:
|
Next packet sequence number to be transmitted.
|
sndwnd:
|
TCP window size of the remote neighbor.
|
irs:
|
Initial packet receive sequence number.
|
rcvnxt:
|
Last receive sequence number that has been locally acknowledged.
|
rcvwnd:
|
TCP window size of the local host.
|
delrcvwnd:
|
Delayed receive window—data the local host has read from the connection, but has not yet subtracted from the receive window the host has advertised to the remote host. The value in this field gradually increases until it is larger than a full-sized packet, at which point it is applied to the rcvwnd field.
|
SRTT:
|
A calculated smoothed round-trip timeout.
|
RTTO:
|
Round-trip timeout.
|
RTV:
|
Variance of the round-trip time.
|
KRTT:
|
New round-trip timeout (using the Karn algorithm). This field separately tracks the round-trip time of packets that have been re-sent.
|
minRTT:
|
Smallest recorded round-trip timeout (hard-wire value used for calculation).
|
maxRTT:
|
Largest recorded round-trip timeout.
|
ACK hold:
|
Length of time the local host will delay an acknowledgment to carry (piggyback) additional data.
|
IP Precedence value:
|
IP precedence of the BGP packets.
|
Datagrams
|
Number of update packets received from a neighbor.
|
Rcvd:
|
Number of received packets.
|
with data
|
Number of update packets sent with data.
|
total data bytes
|
Total amount of data received, in bytes.
|
Sent
|
Number of update packets sent.
|
Second Congestion
|
Number of update packets with data sent.
|
Datagrams: Rcvd
|
Number of update packets received from a neighbor.
|
out of order:
|
Number of packets received out of sequence.
|
with data
|
Number of update packets received with data.
|
Last reset
|
Elapsed time since this peering session was last reset.
|
unread input bytes
|
Number of bytes of packets still to be processed.
|
retransmit
|
Number of packets retransmitted.
|
fastretransmit
|
Number of duplicate acknowledgments retransmitted for an out of order segment before the retransmission timer expires.
|
partialack
|
Number of retransmissions for partial acknowledgements (transmissions before or without subsequent acknowledgements).
|
Second Congestion
|
Number of second retransmissions sent due to congestion.
|
show ip bgp neighbors (4-Byte Autonomous System Numbers): Example
The following partial example shows output for several external BGP neighbors in autonomous systems with 4-byte autonomous system numbers, 65536 and 65550. This example requires Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, or a later release.
Router# show ip bgp neighbors
BGP neighbor is 192.168.1.2, remote AS 65536, external link
BGP version 4, remote router ID 0.0.0.0
Last read 02:03:38, last write 02:03:38, hold time is 120, keepalive interval is 70
seconds
Configured hold time is 120, keepalive interval is 70 seconds
Minimum holdtime from neighbor is 0 seconds
BGP neighbor is 192.168.3.2, remote AS 65550, external link
BGP version 4, remote router ID 0.0.0.0
Last read 02:03:48, last write 02:03:48, hold time is 120, keepalive interval is 70
seconds
Configured hold time is 120, keepalive interval is 70 seconds
Minimum holdtime from neighbor is 0 seconds
show ip bgp neighbors advertised-routes: Example
The following example displays routes advertised for only the 172.16.232.178 neighbor:
Router# show ip bgp neighbors 172.16.232.178 advertised-routes
BGP table version is 27, local router ID is 172.16.232.181
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
*>i10.0.0.0 172.16.232.179 0 100 0 ?
*> 10.20.2.0 10.0.0.0 0 32768 i
Table 43 describes the significant fields shown in the display.
Table 43 show ip bgp neighbors advertised-routes Field Descriptions
Field
|
Description
|
BGP table version
|
Internal version number of the table. This is the primary routing table with which the neighbor has been updated. The number increments when the table changes.
|
local router ID
|
IP address of the local BGP speaker.
|
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 and will not be advertised to BGP neighbors.
•h—The table entry does not contain the best path based on historical information.
•*—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.
|
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:
•i—Entry originated from Interior Gateway Protocol (IGP) and was advertised with a network router configuration command.
•e—Entry originated from Exterior Gateway Protocol (EGP).
•?—Origin of the path is not clear. Usually, this is a router that is redistributed into BGP from an IGP.
|
Network
|
IP address of a network entity.
|
Next Hop
|
IP address of the next system used to forward a packet to the destination network. An entry of 0.0.0.0 indicates that there are non-BGP routes in the path to the destination network.
|
Metric
|
If shown, this is the value of the inter-autonomous system metric. This field is not used frequently.
|
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.
|
show ip bgp neighbors paths: Example
The following is example output from the show ip bgp neighbors command entered with the paths keyword:
Router# show ip bgp neighbors 172.29.232.178 paths ^10
Address Refcount Metric Path
Table 44 describes the significant fields shown in the display.
Table 44 show ip bgp neighbors paths Field Descriptions
Field
|
Description
|
Address
|
Internal address where the path is stored.
|
Refcount
|
Number of routes using that path.
|
Metric
|
Multi Exit Discriminator (MED) metric for the path. (The name of this metric for BGP versions 2 and 3 is INTER_AS.)
|
Path
|
Autonomous system path for that route, followed by the origin code for that route.
|
show ip bgp neighbors received prefix-filter: Example
The following example shows that a prefix-list that filters all routes in the 10.0.0.0 network has been received from the 192.168.20.72 neighbor:
Router# show ip bgp neighbors 192.168.20.72 received prefix-filter
Address family:IPv4 Unicast
ip prefix-list 192.168.20.72:1 entries
seq 5 deny 10.0.0.0/8 le 32
Table 45 describes the significant fields shown in the display.
Table 45 show ip bgp neighbors received prefix-filter Field Descriptions
Field
|
Description
|
Address family
|
Address family mode in which the prefix filter is received.
|
ip prefix-list
|
Prefix list sent from the specified neighbor.
|
show ip bgp neighbors policy: Example
The following sample output shows the policies applied to the neighbor at 192.168.1.2. The output displays both inherited policies and policies configured on the neighbor device. Inherited polices are policies that the neighbor inherits from a peer-group or a peer-policy template.
Router# show ip bgp neighbors 192.168.1.2 policy
Neighbor: 192.168.1.2, Address-Family: IPv4 Unicast
Locally configured policies:
prefix-list NO-MARKETING in
Cisco IOS Release 12.0(31)S, 12.4(4)T, 12.2(18)SXE, and 12.2(33)SB: Example
The following is sample output from the show ip bgp neighbors command that verifies that Bidirectional Forwarding Detection (BFD) is being used to detect fast fallover for the BGP neighbor that is a BFD peer.
Router# show ip bgp neighbors
BGP neighbor is 172.16.10.2, remote AS 45000, external link
Using BFD to detect fast fallover
Cisco IOS Release 12.2(33)SRA and 12.4(20)T: Example
The following is sample output from the show ip bgp neighbors command that verifies that BGP TCP path maximum transmission unit (MTU) discovery is enabled for the BGP neighbor at 172.16.1.2.
Router# show ip bgp neighbors 172.16.1.2
BGP neighbor is 172.16.1.2, remote AS 45000, internal link
BGP version 4, remote router ID 172.16.1.99
For address family: IPv4 Unicast
BGP table version 5, neighbor version 5/0
Address tracking is enabled, the RIB does have a route to 172.16.1.2
Address tracking requires at least a /24 route to the peer
Connections established 3; dropped 2
Last reset 00:00:35, due to Router ID changed
Transport(tcp) path-mtu-discovery is enabled
SRTT: 146 ms, RTTO: 1283 ms, RTV: 1137 ms, KRTT: 0 ms
minRTT: 8 ms, maxRTT: 300 ms, ACK hold: 200 ms
Flags: higher precedence, retransmission timeout, nagle, path mtu capable
Cisco IOS Release 12.2(33)SXH: Example
The following is sample output from the show ip bgp neighbors command that verifies that the neighbor 192.168.3.2 is a member of the peer group, group192, and belongs to the subnet range group 192.168.0.0/16, which shows that this BGP neighbor was dynamically created.
Router# show ip bgp neighbors 192.168.3.2
BGP neighbor is *192.168.3.2, remote AS 50000, external link
Member of peer-group group192 for session parameters
Belongs to the subnet range group: 192.168.0.0/16
BGP version 4, remote router ID 192.168.3.2
BGP state = Established, up for 00:06:35
Last read 00:00:33, last write 00:00:25, hold time is 180, keepalive intervals
Route refresh: advertised and received(new)
Address family IPv4 Unicast: advertised and received
Default minimum time between advertisement runs is 30 seconds
For address family: IPv4 Unicast
BGP table version 1, neighbor version 1/0
Index 1, Offset 0, Mask 0x2
group192 peer-group member
Cisco IOS Releases 12.2(33)SRC and 12.2(33)SB: Example
The following is partial output from the show ip bgp neighbors command that verifies the status of the BGP graceful restart capability for the external BGP peer at 192.168.3.2. Graceful restart is shown as disabled for this BGP peer.
Router# show ip bgp neighbors 192.168.3.2
BGP neighbor is 192.168.3.2, remote AS 50000, external link
Inherits from template S2 for session parameters
BGP version 4, remote router ID 192.168.3.2
BGP state = Established, up for 00:01:41
Last read 00:00:45, last write 00:00:45, hold time is 180, keepalive intervals
1 active, is multisession capable
Route refresh: advertised and received(new)
Address family IPv4 Unicast: advertised and received
Address tracking is enabled, the RIB does have a route to 192.168.3.2
Connections established 1; dropped 0
Transport(tcp) path-mtu-discovery is enabled
Graceful-Restart is disabled
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Related Commands
Command
|
Description
|
bgp asnotation dot
|
Changes the default display and the regular expression match format of BGP 4-byte autonomous system numbers from asplain (decimal values) to dot notation.
|
neighbor send-label
|
Enables a BGP router to send MPLS labels with BGP routes to a neighboring BGP router.
|
neighbor send-label explicit-null
|
Enables a BGP router to send MPLS labels with explicit-null information for a CSC-CE router and BGP routes to a neighboring CSC-PE router.
|
router bgp
|
Configures the BGP routing process.
|
show ip bgp paths
To display all the BGP paths in the database, use the show ip bgp paths command in EXEC mode.
show ip bgp paths
Cisco 10000 Series Router
show ip bgp paths regexp
Syntax Description
regexp
|
Regular expression to match the BGP autonomous system paths.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show ip bgp paths command in privileged EXEC mode:
Router# show ip bgp paths
Address Hash Refcount Metric Path
Table 46 describes the significant fields shown in the display.
Table 46 show ip bgp paths Field Descriptions
Field
|
Description
|
Address
|
Internal address where the path is stored.
|
Hash
|
Hash bucket where path is stored.
|
Refcount
|
Number of routes using that path.
|
Metric
|
The Multi Exit Discriminator (MED) metric for the path. (The name of this metric for BGP versions 2 and 3 is INTER_AS.)
|
Path
|
The autonomous system path for that route, followed by the origin code for that route.
|
show ip bgp peer-group
To display information about BGP peer groups, use the show ip bgp peer-group command in user EXEC or privileged EXEC mode.
show ip bgp peer-group [peer-group-name] [summary]
Syntax Description
peer-group-name
|
(Optional) Displays information about a specific peer group.
|
summary
|
(Optional) Displays a summary of the status of all the members of a peer group.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH, and the output was modified to support BGP dynamic neighbors.
|
Examples
The following is sample output from the show ip bgp peer-group command for a peer group named internal in privileged EXEC mode:
Router# show ip bgp peer-group internal
BGP peer-group is internal, remote AS 100
Minimum time between advertisement runs is 5 seconds
For address family:IPv4 Unicast
BGP neighbor is internal, peer-group internal, members:
Index 3, Offset 0, Mask 0x8
Incoming update AS path filter list is 53
Outgoing update AS path filter list is 54
Route map for incoming advertisements is MAP193
Route map for outgoing advertisements is MAP194
Update messages formatted 0, replicated 0
The following output from the show ip bgp peer-group command shows information about a configured listen range group, group192. In Cisco IOS Release 12.2(33)SXH and later releases, the BGP dynamic neighbor feature introduced the ability to support the dynamic creation of BGP neighbor peers using a subnet range associated with a peer group (listen range group).
Router# show ip bgp peer-group group192
BGP peer-group is group192, remote AS 40000
BGP peergroup group192 listen range group members:
Default minimum time between advertisement runs is 30 seconds
For address family: IPv4 Unicast
BGP neighbor is group192, peer-group external, members:
Index 0, Offset 0, Mask 0x0
Update messages formatted 0, replicated 0
Number of NLRIs in the update sent: max 0, min 0
show ip bgp quote-regexp
To display routes matching the autonomous system path regular expression, use the show ip bgp quote-regexp command in privileged EXEC mode.
show ip bgp quote-regexp regexp
Syntax Description
regexp
|
The regular expression to match the Border Gateway Protocol (BGP) autonomous system paths.
•In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, 4-byte autonomous system numbers are supported in the range from 65536 to 4294967295 in asplain notation and in the range from 1.0 to 65535.65535 in asdot notation.
•In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, 4-byte autonomous system numbers are supported in the range from 1.0 to 65535.65535 in asdot notation only.
For more details about autonomous system number formats, see the router bgp command.
Note The regular expression has to be an exact match.
|
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(14)SX
|
This command was integrated into Cisco IOS Release 12.2(14)SX.
|
12.0(32)S12
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.0(32)SY8
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.4(24)T
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
Cisco IOS XE Release 2.3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.2(33)SXI1
|
This command was modified. Support for 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.0(33)S3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Cisco IOS XE Release 2.4
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Usage Guidelines
In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538 for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the bgp asnotation dot command followed by the clear ip bgp * command to perform a hard reset of all current BGP sessions.
In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, the Cisco implementation of 4-byte autonomous system numbers uses asdot—1.2 for example—as the only configuration format, regular expression match, and output display, with no asplain support.
Examples
The following is sample output from the show ip bgp quote-regexp command in privileged EXEC mode:
Router# show ip bgp quote-regexp "^10_" | begin 10.40
*> 10.40.0.0/20 10.10.10.10 0 10 2548 1239 10643 i
*> 10.40.16.0/20 10.10.10.10 0 10 2548 6172 i
*> 10.40.32.0/19 10.10.10.10 0 10 2548 6172 i
*> 10.41.0.0/19 10.10.10.10 0 10 2548 3356 3703 ?
*> 10.42.0.0/17 10.10.10.10 0 10 2548 6172 i
Note Although the columns in the above display are not labeled, see Table 47 for detailed information.
Table 47 describes the significant fields shown in the display from left to right.
Table 47 show ip bgp quote-regexp Field Descriptions
Field
|
Description
|
Status codes
|
Status of the table entry; for example, * in the above display. 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 failed to install in the routing table.
S—The table entry is a stale route.
|
Network
|
IP address of a network entity; for example, 24.40.0.0/20 in the above display.
|
Next Hop
|
IP address of the next system that is used when forwarding a packet to the destination network; for example, 10.10.10.10. in the above display. 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.; for example, 0 in the above display.
|
LocPrf
|
Local preference value as set with the set local-preference route-map configuration command; for example, 10 in the above display. The default value is 100.
|
Weight
|
Weight of the route as set via autonomous system filters; for example, 2548 in the above display.
|
Path
|
Autonomous system paths to the destination network; for example, 1239 in the above display. There can be one entry in this field for each autonomous system in the path.
|
Origin codes
|
Origin of the entry; for example, ? in the above display. The origin code is placed at the end of each line in the table. It can be one of the following values:
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.
|
The following output from the show ip bgp quote-regexp command shows routes that match the quoted regular expression for the 4-byte autonomous system number 65550. The 4-byte autonomous system number is displayed in the default asplain format. This example requires Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, or a later release.
Router# show ip bgp quote-regexp "^65550$"
BGP table version is 4, local router ID is 172.17.1.99
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
*> 10.2.2.0/24 192.168.3.2 0 0 65550 i
Related Commands
Command
|
Description
|
bgp asnotation dot
|
Changes the default display and the regular expression match format of BGP 4-byte autonomous system numbers from asplain (decimal values) to dot notation.
|
router bgp
|
Configures the BGP routing process.
|
show ip bgp regexp
|
Displays routes matching the autonomous system path regular expression.
|
show ip bgp regexp
To display routes matching the autonomous system path regular expression, use the show ip bgp regexp command in user EXEC or privileged EXEC mode.
show ip bgp regexp regexp
Syntax Description
regexp
|
Regular expression to match the BGP autonomous system paths.
•In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, 4-byte autonomous system numbers are supported in the range from 65536 to 4294967295 in asplain notation and in the range from 1.0 to 65535.65535 in asdot notation.
•In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, 4-byte autonomous system numbers are supported in the range from 1.0 to 65535.65535 in asdot notation only.
For more details about autonomous system number formats, see the router bgp command.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(14)SX
|
This command was integrated into Cisco IOS Release 12.2(14)SX.
|
12.0(32)S12
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.0(32)SY8
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.4(24)T
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
Cisco IOS XE Release 2.3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.2(33)SXI1
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.0(33)S3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Cisco IOS XE Release 2.4
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Usage Guidelines
In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538 for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the bgp asnotation dot command followed by the clear ip bgp * command to perform a hard reset of all current BGP sessions.
In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, the Cisco implementation of 4-byte autonomous system numbers uses asdot—1.2 for example—as the only configuration format, regular expression match, and output display, with no asplain support.
To ensure a smooth transition we recommend that all BGP speakers within an autonomous system that is identified using a 4-byte autonomous system number, are upgraded to support 4-byte autonomous system numbers.
Examples
The following is sample output from the show ip bgp regexp command in privileged EXEC mode:
Router# show ip bgp regexp 108$
BGP table version is 1738, local router ID is 172.16.72.24
Status codes: s suppressed, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
* 172.16.0.0 172.16.72.30 0 109 108 ?
* 172.16.1.0 172.16.72.30 0 109 108 ?
* 172.16.11.0 172.16.72.30 0 109 108 ?
* 172.16.14.0 172.16.72.30 0 109 108 ?
* 172.16.15.0 172.16.72.30 0 109 108 ?
* 172.16.16.0 172.16.72.30 0 109 108 ?
* 172.16.17.0 172.16.72.30 0 109 108 ?
* 172.16.18.0 172.16.72.30 0 109 108 ?
* 172.16.19.0 172.16.72.30 0 109 108 ?
* 172.16.24.0 172.16.72.30 0 109 108 ?
* 172.16.29.0 172.16.72.30 0 109 108 ?
* 172.16.30.0 172.16.72.30 0 109 108 ?
* 172.16.33.0 172.16.72.30 0 109 108 ?
* 172.16.35.0 172.16.72.30 0 109 108 ?
* 172.16.36.0 172.16.72.30 0 109 108 ?
* 172.16.37.0 172.16.72.30 0 109 108 ?
* 172.16.38.0 172.16.72.30 0 109 108 ?
* 172.16.39.0 172.16.72.30 0 109 108 ?
The following example requires Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, or a later release. After the bgp asnotation dot command is configured, the regular expression match format for 4-byte autonomous system paths is changed to asdot notation format. Although a 4-byte autonomous system number can be configured in a regular expression using either asplain or asdot format, only 4-byte autonomous system numbers configured using the current default format are matched. In the first example, the show ip bgp regexp command is configured with a 4-byte autonomous system number in asplain format. The match fails because the default format is currently asdot format and there is no output. In the second example using asdot format, the match passes and the information about the 4-byte autonomous system path is shown using the asdot notation.
Note The asdot notation uses a period which is a special character in Cisco regular expressions. to remove the special meaning, use a backslash before the period.
Router# show ip bgp regexp ^65536$
Router# show ip bgp regexp ^1\.0$
BGP table version is 2, local router ID is 172.17.1.99
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
*> 10.1.1.0/24 192.168.1.2 0 0 1.0 i
The following is sample output from the show ip bgp regexp command after the bgp asnotation dot command has been entered to display 4-byte autonomous system numbers in asdot notation in Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, or later release. The asdot notation is the only format for 4-byte autonomous system numbers in Cisco IOS Release 12.0(32)S12, 12.4(24)T, or Cisco IOS XE Release 2.3.
Note The asdot notation uses a period which is a special character in Cisco regular expressions. to remove the special meaning, use a backslash before the period.
Router# show ip bgp regexp ^1\.14$
BGP table version is 4, local router ID is 172.17.1.99
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
*> 10.1.1.0/24 192.168.1.2 0 0 1.14 i
Related Commands
Command
|
Description
|
bgp asnotation dot
|
Changes the default display and the regular expression match format of BGP 4-byte autonomous system numbers from asplain (decimal values) to dot notation.
|
router bgp
|
Configures the BGP routing process.
|
show ip bgp quote-regexp
|
Displays routes matching the autonomous system path regular expression.
|
show ip bgp replication
To display update replication statistics for Border Gateway Protocol (BGP) update groups, use the show ip bgp replication command in EXEC mode.
show ip bgp replication [index-group | ip-address]
Syntax Description
index-group
|
(Optional) Displays update replication statistics for the update group with corresponding index number will be displayed. The range of update-group index numbers is from 1 to 4294967295.
|
ip-address
|
(Optional) Displays the IP address of a single neighbor for which update-group statistics will be displayed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
The output of this command displays BGP update-group replication statistics.
When a change to outbound policy occurs, the router automatically recalculates update-group memberships and applies the changes by triggering an outbound soft reset after a 3-minute timer expires. This behavior is designed to provide the network operator with time to change the configuration if a mistake is made. You can manually enable an outbound soft reset before the timer expires by entering the clear ip bgp ip-address soft out command.
Examples
The following sample output from the show ip bgp replication command shows update-group replication information for all neighbors:
Router# show ip bgp replication
BGP Total Messages Formatted/Enqueued : 0/0
Index Type Members Leader MsgFmt MsgRepl Csize Qsize
1 internal 1 10.4.9.21 0 0 0 0
2 internal 2 10.4.9.5 0 0 0 0
The following sample output from the show ip bgp replication command shows update-group statistics for the 10.4.9.5 neighbor:
Router# show ip bgp replication 10.4.9.5
Index Type Members Leader MsgFmt MsgRepl Csize Qsize
2 internal 2 10.4.9.5 0 0 0 0
Table 48 describes the significant fields shown in the display.
Table 48 show ip bgp replication Field Descriptions
Field
|
Description
|
Index
|
Index number of the update group.
|
Type
|
Type of peer (internal or external).
|
Members
|
Number of members in the dynamic update peer group.
|
Leader
|
First member of the dynamic update peer group.
|
Related Commands
Command
|
Description
|
clear ip bgp
|
Resets a BGP connection or session.
|
clear ip bgp update-group
|
Clears BGP update-group member sessions.
|
debug ip bgp groups
|
Displays information related to the processing of BGP update groups.
|
show ip bgp peer-group
|
Displays information about BGP update groups.
|
show ip bgp rib-failure
To display Border Gateway Protocol (BGP) routes that failed to install in the Routing Information Base (RIB) table, use the show ip bgp rib-failure command in privileged EXEC mode.
show ip bgp rib-failure
Syntax Description
This command has no keywords or arguments.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3
|
This command was introduced.
|
12.0(26)S
|
This command was integrated into Cisco IOS Release 12.0(26)S.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Examples
The following is sample output from the show ip bgp rib-failure command:
Router# show ip bgp rib-failure
Network Next Hop RIB-failure RIB-NH Matches
10.1.15.0/24 10.1.35.5 Higher admin distance n/a
10.1.16.0/24 10.1.15.1 Higher admin distance n/a
Table 49 describes the significant fields shown in the display.
Table 49 show ip bgp rib-failure Field Descriptions
Field
|
Description
|
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.
|
RIB-failure
|
Cause of RIB failure. Higher admin distance means that a route with a better (lower) administrative distance such as a static route already exists in the IP routing table.
|
RIB-NH Matches
|
Route status that applies only when Higher admin distance appears in the RIB-failure column and bgp suppress-inactive is configured for the address family being used. There are three choices:
•Yes—Means that the route in the RIB has the same next hop as the BGP route or next hop recurses down to the same adjacency as the BGP nexthop.
•No—Means that the next hop in the RIB recurses down differently from the next hop of the BGP route.
•n/a—Means that bgp suppress-inactive is not configured for the address family being used.
|
Related Commands
Command
|
Description
|
bgp suppress-inactive
|
Configures a router to suppress the advertisement of BGP routes that are not installed in the RIB and FIB tables.
|
clear ip bgp
|
Resets a BGP connection or session.
|
neighbor soft-reconfiguration
|
Configures the Cisco IOS software to start storing updates.
|
show ip bgp summary
To display the status of all Border Gateway Protocol (BGP) connections, use the show ip bgp summary command in user EXEC or privileged EXEC mode.
show ip bgp summary
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0
|
Support for the neighbor maximum-prefix command was added to the output.
|
12.2
|
•The number of networks and paths displayed in the output was split out to two separate lines.
•A field was added to display multipath entries in the routing table.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.4(11)T
|
A line was added to the output to display the advertised bitfield cache entries and associated memory usage.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH, and the output was modified to support BGP dynamic neighbors.
|
12.0(32)S12
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.0(32)SY8
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.4(24)T
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
Cisco IOS XE Release 2.3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asdot notation only was added.
|
12.2(33)SXI1
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain and asdot notation was added.
|
12.0(33)S3
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Cisco IOS XE Release 2.4
|
This command was modified. Support for displaying 4-byte autonomous system numbers in asplain notation was added and the default display format is now asplain.
|
Usage Guidelines
The show ip bgp summary command is used to display BGP path, prefix, and attribute information for all connections to BGP neighbors.
A prefix is an IP address and network mask. It can represent an entire network, a subset of a network, or a single host route. A path is a route to a given destination. By default, BGP will install only a single path for each destination. If multipath routes are configured, BGP will install a path entry for each multipath route, and only one multipath route will be marked as the bestpath.
BGP attribute and cache entries are displayed individually and in combinations that affect the bestpath selection process. The fields for this output are displayed when the related BGP feature is configured or attribute is received. Memory usage is displayed in bytes.
In Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, and later releases, the Cisco implementation of 4-byte autonomous system numbers uses asplain—65538 for example—as the default regular expression match and output display format for autonomous system numbers, but you can configure 4-byte autonomous system numbers in both the asplain format and the asdot format as described in RFC 5396. To change the default regular expression match and output display of 4-byte autonomous system numbers to asdot format, use the bgp asnotation dot command followed by the clear ip bgp * command to perform a hard reset of all current BGP sessions.
In Cisco IOS Release 12.0(32)S12, 12.4(24)T, and Cisco IOS XE Release 2.3, the Cisco implementation of 4-byte autonomous system numbers uses asdot—1.2 for example—as the only configuration format, regular expression match, and output display, with no asplain support.
Examples
The following is sample output from the show ip bgp summary command in privileged EXEC mode:
Router# show ip bgp summary
BGP router identifier 172.16.1.1, local AS number 100
BGP table version is 199, main routing table version 199
37 network entries using 2850 bytes of memory
59 path entries using 5713 bytes of memory
18 BGP path attribute entries using 936 bytes of memory
2 multipath network entries and 4 multipath paths
10 BGP AS-PATH entries using 240 bytes of memory
7 BGP community entries using 168 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
90 BGP advertise-bit cache entries using 1784 bytes of memory
36 received paths for inbound soft reconfiguration
BGP using 34249 total bytes of memory
Dampening enabled. 4 history paths, 0 dampened paths
BGP activity 37/2849 prefixes, 60/1 paths, scan interval 15 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.100.1.1 4 200 26 22 199 0 0 00:14:23 23
10.200.1.1 4 300 21 51 199 0 0 00:13:40 0
Table 50 describes the significant fields shown in the display. Fields that are preceded by the asterisk character (*) are not shown in the above output.
.
Table 50 show ip bgp summary Field Descriptions
Field
|
Description
|
BGP router identifier
|
In order of precedence and availability, the router identifier specified by the bgp router-id command, a loopback address, or the highest IP address.
|
BGP table version
|
Internal version number of BGP database.
|
main routing table version
|
Last version of BGP database that was injected into the main routing table.
|
...network entries
|
Number of unique prefix entries in the BGP database.
|
...using ... bytes of memory
|
Amount of memory, in bytes, that is consumed for the path, prefix, or attribute entry displayed on the same line.
|
...path entries using
|
Number of path entries in the BGP database. Only a single path entry will be installed for a given destination. If multipath routes are configured, a path entry will be installed for each multipath route.
|
...multipath network entries using
|
Number of multipath entries installed for a given destination.
|
* ...BGP path/bestpath attribute entries using
|
Number of unique BGP attribute combinations for which a path is selected as the bestpath.
|
* ...BGP rrinfo entries using
|
Number of unique ORIGINATOR and CLUSTER_LIST attribute combinations.
|
...BGP AS-PATH entries using
|
Number of unique AS_PATH entries.
|
...BGP community entries using
|
Number of unique BGP community attribute combinations.
|
*...BGP extended community entries using
|
Number of unique extended community attribute combinations.
|
BGP route-map cache entries using
|
Number of BGP route-map match and set clause combinations. A value of 0 indicates that the route cache is empty.
|
...BGP filter-list cache entries using
|
Number of filter-list entries that match an AS-path access list permit or deny statements. A value of 0 indicates that the filter-list cache is empty.
|
BGP advertise-bit cache entries using
|
(Cisco IOS Release 12.4(11)T and later releases only) Number of advertised bitfield entries and the associated memory usage. A bitfield entry represents a piece of information (one bit) that is generated when a prefix is advertised to a peer. The advertised bit cache is built dynamically when required.
|
...received paths for inbound soft reconfiguration
|
Number paths received and stored for inbound soft reconfiguration.
|
BGP using...
|
Total amount of memory, in bytes, used by the BGP process.
|
Dampening enabled...
|
Indicates that BGP dampening is enabled. The number of paths that carry an accumulated penalty and the number of dampened paths are displayed on this line.
|
BGP activity...
|
Displays the number of times that memory has been allocated or released for a path or prefix.
|
Neighbor
|
IP address of the neighbor.
|
V
|
BGP version number spoken to the neighbor.
|
AS
|
Autonomous system number.
|
MsgRcvd
|
Number of messages received from the neighbor.
|
MsgSent
|
Number of messages sent to the neighbor.
|
TblVer
|
Last version of the BGP database that was sent to the neighbor.
|
InQ
|
Number of messages queued to be processed from the neighbor.
|
OutQ
|
Number of messages queued to be sent to the neighbor.
|
Up/Down
|
The length of time that the BGP session has been in the Established state, or the current status if not in the Established state.
|
State/PfxRcd
|
Current state of the BGP session, and the number of prefixes that have been received from a neighbor or peer group. When the maximum number (as set by the neighbor maximum-prefix command) is reached, the string "PfxRcd" appears in the entry, the neighbor is shut down, and the connection is set to Idle.
An (Admin) entry with Idle status indicates that the connection has been shut down using the neighbor shutdown command.
|
The following output from the show ip bgp summary command shows that the BGP neighbor 192.168.3.2 was dynamically created and is a member of the listen range group, group192. The output also shows that the IP prefix range of 192.168.0.0/16 is defined for the listen range group named group192. In Cisco IOS Release 12.2(33)SXH and later releases, the BGP dynamic neighbor feature introduced the ability to support the dynamic creation of BGP neighbor peers using a subnet range associated with a peer group (listen range group).
Router# show ip bgp summary
BGP router identifier 192.168.3.1, local AS number 45000
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
*192.168.3.2 4 50000 2 2 0 0 0 00:00:37 0
* Dynamically created based on a listen range command
Dynamically created neighbors: 1/(200 max), Subnet ranges: 1
BGP peergroup group192 listen range group members:
The following output from the show ip bgp summary command shows two BGP neighbors, 192.168.1.2 and 192.168.3.2, in different 4-byte autonomous system numbers, 65536 and 65550. The local autonomous system 65538 is also a 4-byte autonomous system number and the numbers are displayed in the default asplain format. This example requires Cisco IOS Release 12.0(32)SY8, 12.2(33)SXI1, 12.0(33)S3, Cisco IOS XE Release 2.4, or a later release.
Router# show ip bgp summary
BGP router identifier 172.17.1.99, local AS number 65538
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down Statd
192.168.1.2 4 65536 7 7 1 0 0 00:03:04 0
192.168.3.2 4 65550 4 4 1 0 0 00:00:15 0
The following output from the show ip bgp summary command shows the same two BGP neighbors, but the 4-byte autonomous system numbers are displayed in asdot notation format. To change the display format the bgp asnotation dot command must be configured in router configuration mode. This example requires Cisco IOS Release 12.0(32)SY8, 12.0(32)S12, 12.2(33)SXI1, 12.4(24)T, or Cisco IOS XE Release 2.3 or later releases.
Router# show ip bgp summary
BGP router identifier 172.17.1.99, local AS number 1.2
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down Statd
192.168.1.2 4 1.0 9 9 1 0 0 00:04:13 0
192.168.3.2 4 1.14 6 6 1 0 0 00:01:24 0
Related Commands
Command
|
Description
|
bgp asnotation dot
|
Changes the default display and the regular expression match format of BGP 4-byte autonomous system numbers from asplain (decimal values) to dot notation.
|
bgp router-id
|
Configures a fixed router ID for the local BGP routing process.
|
neighbor maximum-prefix
|
Controls how many prefixes can be received from a BGP neighbor.
|
neighbor shutdown
|
Disables a BGP neighbor or peer group.
|
router bgp
|
Configures the BGP routing process.
|
show ip bgp template peer-policy
To display locally configured peer policy templates, use the show ip bgp template peer-policy command in user EXEC or privileged EXEC mode.
show ip bgp template peer-policy [policy-template-name [detail]]
Syntax Description
policy-template-name
|
(Optional) Name of a locally configured peer policy template.
|
detail
|
(Optional) Displays detailed policy information such as route maps, prefix lists, community lists, access control lists (ACLs), and AS-path filter lists.
|
Command Default
If a peer policy template is not specified using the policy-template-name argument, all peer policy templates will be displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.0(25)S
|
The detail keyword was added.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.4(11)T
|
Support for the detail keyword was integrated into Cisco IOS Release 12.4(11)T.
|
12.2(33)SRB
|
This command and support for the detail keyword were integrated into Cisco IOS Release 12.2(33)SRB.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
12.2(33)SB
|
Support for the detail keyword was integrated into Cisco IOS Release 12.2(33)SB.
|
Usage Guidelines
This command is used to display locally configured peer policy templates. The output can be filtered to display a single peer policy template using the policy-template-name argument. This command also supports all standard output modifiers.
When BGP neighbors use multiple levels of peer templates it can be difficult to determine which policies are associated with a specific template. In Cisco IOS Release 12.0(25)S, 12.4(11)T, 12.2(33)SRB, 12.2(33)SB, and later releases, the detail keyword was added to display the detailed configuration of local and inherited policies associated with a specific template. Inherited policies are policies that the template inherits from other peer-policy templates.
Examples
The show ip bgp template peer-policy command is used to verify the configuration of local peer policy templates. The following sample output shows the peer policy templates named GLOBAL and NETWORK1. The output also shows that the GLOBAL template was inherited by the NETWORK1 template.
Router# show ip bgp template peer-policy
Template:GLOBAL, index:1.
Local policies:0x80840, Inherited polices:0x0
*Inherited by Template NETWORK1, index:2
Locally configured policies:
prefix-list NO-MARKETING in
Template:NETWORK1, index:2.
Local policies:0x1, Inherited polices:0x80840
GLOBAL, index:1, seq_no:10, flags:0x1
Locally configured policies:
prefix-list NO-MARKETING in
Table 51 describes the significant fields shown in the display.
Table 51 show ip bgp template peer-policy Field Descriptions
Field
|
Description
|
Template
|
Name of the peer template.
|
index
|
The sequence number in which the displayed template is processed.
|
Local policies
|
Displays the hexadecimal value of locally configured policies.
|
Inherited polices
|
Displays the hexadecimal value of inherited policies. The 0x0 value is displayed when no templates are inherited.
|
Locally configured policies
|
Displays a list of commands that are locally configured in a peer policy template.
|
Inherited policies
|
Displays a list of commands that are inherited from a peer template.
|
The following sample output of the show ip bgp template peer-policy command with the detail keyword displays details of the template named NETWORK1, which includes the inherited template named GLOBAL. The output in this example displays the configuration commands of the locally configured route map and prefix list and the inherited prefix list.
Router# show ip bgp template peer-policy NETWORK1 detail
Template:NETWORK1, index:2.
Local policies:0x1, Inherited polices:0x80840
GLOBAL, index:1, seq_no:10, flags:0x1
Locally configured policies:
prefix-list NO-MARKETING in
Template:NETWORK1 <detail>
Locally configured policies:
route-map ROUTE, permit, sequence 10
ip address prefix-lists: DEFAULT
ip prefix-list DEFAULT: 1 entries
Policy routing matches: 0 packets, 0 bytes
prefix-list NO-MARKETING in
ip prefix-list NO-MARKETING: 1 entries
Related Commands
Command
|
Description
|
inherit peer-policy
|
Configures a peer policy template to inherit the configuration from another peer policy template.
|
template peer-policy
|
Creates a peer policy template and enters policy-template configuration mode.
|
show ip bgp template peer-session
To display peer policy template configurations, use the show ip bgp template peer-session command in user EXEC and privileged EXEC mode.
show ip bgp template peer-session [session-template-name]
Syntax Description
session-template-name
|
(Optional) Name of a locally configured peer session template.
|
Defaults
If a peer session template is not specified with the session-template-name argument, all peer session templates will be displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(31)SB
|
This command was integrated into Cisco IOS Release 12.2(31)SB.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command is used to display locally configured peer session templates. The output can be filtered to display a single peer session template with the peer-session-name argument. This command also supports all standard output modifiers.
Examples
The show ip bgp template peer-session command is used to verify the configuration of local peer session templates. The following example shows the peer session templates named INTERNAL-BGP and CORE1. The output also shows that INTERNAL-BGP is inherited by CORE1.
Router# show ip bgp template peer-session
Template:INTERNAL-BGP, index:1
Local policies:0x21, Inherited polices:0x0
*Inherited by Template CORE1, index= 2
Locally configured session commands:
Inherited session commands:
Local policies:0x180, Inherited polices:0x21
INTERNAL-BGP index:1 flags:0x0
Locally configured session commands:
Inherited session commands:
Table 52 describes the significant fields shown in the display.
Table 52 show ip bgp template peer-session Field Descriptions
Field
|
Description
|
Template:
|
Name of the peer template.
|
index:
|
The sequence number in which the displayed template is processed.
|
Local policies:
|
Displays the hexadecimal value of locally configured policies.
|
Inherited polices:
|
Displays the hexadecimal value of inherited policies. The 0x0 value is displayed when no templates are inherited.
|
Locally configured session commands:
|
Displays a list of commands that are locally configured in a peer template.
|
Inherited session commands:
|
Displays a list of commands that are inherited from a peer session template.
|
Related Commands
Command
|
Description
|
inherit peer-session
|
Configures a peer session template to inherit the configuration from another peer session template.
|
template peer-session
|
Creates a peer session template and enters session-template configuration mode.
|
show ip bgp update-group
To display information about BGP update groups, use the show ip bgp update-group command in user EXEC or privileged EXEC mode.
show ip bgp update-group [index-group | ip-address] [summary]
Syntax Description
index-group
|
(Optional) Displays the update group with its corresponding index number. The range of update-group index numbers is from 1 to 4294967295.
|
ip-address
|
(Optional) Displays the IP address of a single neighbor who is a member of an update group.
|
summary
|
(Optional) Displays a summary of update-group member information. The output can be filtered to show information for a single index group or peer with the index-group or ip-address argument.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.2(18)S
|
This command was integrated into Cisco IOS Release 12.2(18)S.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Use this command to display information about BGP update groups. When a change to BGP outbound policy occurs, the router automatically recalculates update group memberships and applies the changes by triggering an outbound soft reset after a 1-minute timer expires. This behavior is designed to provide the network operator with time to change the configuration if a mistake is made. You can manually enable an outbound soft reset before the timer expires by entering the clear ip bgp ip-address soft out command.
Note In Cisco IOS Release 12.0(25)S, 12.3(2)T, and prior releases, the update group recalculation delay timer is set to 3 minutes.
Examples
The following sample output from the show ip bgp update-group command shows update group information for all neighbors:
Router# show ip bgp update-group
BGP version 4 update-group 1, internal, Address Family: IPv4 Unicast
BGP Update version : 0, messages 0/0
Route map for outgoing advertisements is COST1
Update messages formatted 0, replicated 0
Number of NLRIs in the update sent: max 0, min 0
Minimum time between advertisement runs is 5 seconds
BGP version 4 update-group 2, internal, Address Family: IPv4 Unicast
BGP Update version : 0, messages 0/0
Update messages formatted 0, replicated 0
Number of NLRIs in the update sent: max 0, min 0
Minimum time between advertisement runs is 5 seconds
Table 53 describes the significant fields shown in the display.
Table 53 show ip bgp update group Field Descriptions
Field
|
Description
|
BGP version
|
BGP version.
|
update-group
|
Update-group number and type (internal or external).
|
Update messages formatted..., replicated...
|
Number of update messages that have been formatted and replicated.
|
Number of NLRIs...
|
NLRI information sent in update.
|
Minimum time between...
|
Minimum time, in seconds, between update advertisements.
|
Has...
|
Number of member listed by IP address in the update group.
|
The following sample output from the show ip bgp update-group command shows a summary of update-group information for the 10.4.9.8 neighbor:
Router# show ip bgp update-group 10.4.9.8 summary
Summary for Update-group 2 :
------------------------------
BGP router identifier 10.4.9.4, local AS number 101
BGP table version is 1, main routing table version 1
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
10.4.9.5 4 101 35 35 1 0 0 00:26:22 0
10.4.9.8 4 101 39 39 1 0 0 00:26:21 0
Table 54 describes the significant fields shown in the display.
Table 54 show ip bgp-update group summary Field Descriptions
Field
|
Description
|
Summary for Update-group...
|
Update-group number.
|
BGP router identifier...
|
IP address and AS number for specified peer.
|
update messages formatted..., replicated...
|
Number of update messages that have been formatted and replicated.
|
BGP table version...
|
Displays incremental changes in the BGP routing table.
|
Neighbor...
|
Specific peer information and statistics, including IP address and AS number.
|
Related Commands
Command
|
Description
|
clear ip bgp
|
Resets a BGP connection or session.
|
clear ip bgp update-group
|
Clears BGP update-group member sessions.
|
debug ip bgp groups
|
Displays information related to the processing of BGP update groups.
|
show ip bgp replication
|
Displays BGP update-group replication statistics.
|
show ip bgp vpnv4
To display Virtual Private Network Version 4 (VPNv4) address information from the Border Gateway Protocol (BGP) table, use the show ip bgp vpnv4 command in user EXEC or privileged EXEC mode.
show ip bgp vpnv4 {all | rd route-distinguisher | vrf vrf-name} [rib-failure] [ip-prefix/length
[longer-prefixes]] [network-address [mask] [longer-prefixes]] [cidr-only] [community]
[community-list] [dampened-paths] [filter-list] [flap-statistics] [inconsistent-as]
[neighbors] [paths [line]] [peer-group] [quote-regexp] [regexp] [summary] [labels]
Syntax Description
all
|
Displays the complete VPNv4 database.
|
rd route-distinguisher
|
Displays Network Layer Reachability Information (NLRI) prefixes that match the named route distinguisher.
|
vrf vrf-name
|
Displays NLRI prefixes associated with the named VPN routing and forwarding (VRF) instance.
|
rib-failure
|
(Optional) Displays BGP routes that failed to install in the VRF table.
|
ip-prefix/length
|
(Optional) IP prefix address (in dotted decimal format) and the length of the mask (0 to 32). The slash mark must be included.
|
longer-prefixes
|
(Optional) Displays the entry, if any, that exactly matches the specified prefix parameter and all entries that match the prefix in a "longest-match" sense. That is, prefixes for which the specified prefix is an initial substring.
|
network-address
|
(Optional) IP address of a network in the BGP routing table.
|
mask
|
(Optional) Mask of the network address, in dotted decimal format.
|
cidr-only
|
(Optional) Displays only routes that have nonclassful net masks.
|
community
|
(Optional) Displays routes that match this community.
|
community-list
|
(Optional) Displays routes that match this community list.
|
dampened-paths
|
(Optional) Displays paths suppressed because of dampening (BGP route from peer is up and down).
|
filter-list
|
(Optional) Displays routes that conform to the filter list.
|
flap-statistics
|
(Optional) Displays flap statistics of routes.
|
inconsistent-as
|
(Optional) Displays only routes that have inconsistent autonomous systems of origin.
|
neighbors
|
(Optional) Displays details about TCP and BGP neighbor connections.
|
paths
|
(Optional) Displays path information.
|
line
|
(Optional) A regular expression to match the BGP autonomous system paths.
|
peer-group
|
(Optional) Displays information about peer groups.
|
quote-regexp
|
(Optional) Displays routes that match the autonomous system path regular expression.
|
regexp
|
(Optional) Displays routes that match the autonomous system path regular expression.
|
summary
|
(Optional) Displays BGP neighbor status.
|
labels
|
(Optional) Displays incoming and outgoing BGP labels for each NLRI prefix.
|
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.2(2)T
|
The output of the show ip bgp vpnv4 all ip-prefix command was enhanced to display attributes including multipaths and a best path to the specified network.
|
12.0(21)ST
|
The tags keyword was replaced by the labels keyword to conform to the MPLS guidelines. This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.0(27)S
|
The output of the show ip bgp vpnv4 all labels command was enhanced to display explicit-null label information.
|
12.3
|
The rib-failure keyword was added for VRFs.
|
12.2(22)S
|
The output of the show ip bgp vpnv4 vrf vrf-name labels command was modified so that directly connected VRF networks no longer display as aggregate; no label appears instead.
|
12.2(25)S
|
This command was updated to display MPLS VPN nonstop forwarding information.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB and implemented on the Cisco 10000 series router. The display output was modified to indicate whether BGP Nonstop Routing (NSR) with stateful switchover (SSO) is enabled and the reason the last BGP lost SSO capability.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA, and the output was modified to support per-VRF assignment of the BGP router ID.
|
12.2(31)SB2
|
The output was modified to support per-VRF assignment of the BGP router ID.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH, and the output was modified to support per-VRF assignment of the BGP router ID.
Note In Cisco IOS Release 12.2(33)SXH, the command output does not display on the standby route processor in NSF/SSO mode.
|
12.4(20)T
|
The output was modified to support per-VRF assignment of the BGP router ID.
|
Usage Guidelines
Use this command to display VPNv4 information from the BGP database. The show ip bgp vpnv4 all command displays all available VPNv4 information. The show ip bgp vpnv4 all summary command displays BGP neighbor status. The show ip bgp vpnv4 all labels command displays explicit-null label information.
Examples
The following example shows all available VPNv4 information in a BGP routing table:
Router# show ip bgp vpnv4 all
BGP table version is 18, local router ID is 10.14.14.14
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
Route Distinguisher: 1:101 (default for vrf vpn1)
*>i10.6.6.6/32 10.0.0.21 11 100 0 ?
*> 10.7.7.7/32 10.150.0.2 11 32768 ?
*>i10.69.0.0/30 10.0.0.21 0 100 0 ?
*> 10.150.0.0/24 0.0.0.0 0 32768 ?
Table 55 describes the significant fields shown in the display.
Table 55 show ip bgp vpnv4 all Field Descriptions
Field
|
Description
|
Network
|
Displays the network address from the BGP table.
|
Next Hop
|
Displays the address of the BGP next hop.
|
Metric
|
Displays the BGP metric.
|
LocPrf
|
Displays the local preference.
|
Weight
|
Displays the BGP weight.
|
Path
|
Displays the BGP path per route.
|
The following example shows how to display a table of labels for NLRI prefixes that have a route distinguisher value of 100:1.
Router# show ip bgp vpnv4 rd 100:1 labels
Network Next Hop In label/Out label
Route Distinguisher: 100:1 (vrf1)
10.0.0.0 10.20.0.60 34/nolabel
10.0.0.0 10.20.0.60 35/nolabel
10.0.0.0 10.20.0.60 26/nolabel
10.0.0.0 10.15.0.15 nolabel/26
Table 56 describes the significant fields shown in the display.
Table 56 show ip bgp vpnv4 rd labels Field Descriptions
Field
|
Description
|
Network
|
Displays the network address from the BGP table.
|
Next Hop
|
Specifies the BGP next hop address.
|
In label
|
Displays the label (if any) assigned by this router.
|
Out label
|
Displays the label assigned by the BGP next-hop router.
|
The following example shows VPNv4 routing entries for the VRF named vpn1:
Router# show ip bgp vpnv4 vrf vpn1
BGP table version is 18, local router ID is 10.14.14.14
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
Route Distinguisher: 1:101 (default for vrf vpn1)
*>i10.6.6.6/32 10.0.0.21 11 100 0 ?
*> 10.7.7.7/32 10.150.0.2 11 32768 ?
*>i10.69.0.0/30 10.0.0.21 0 100 0 ?
*> 10.150.0.0/24 0.0.0.0 0 32768 ?
*> 10.0.0.1/32 10.150.0.2 11 32768 ?
*>i10.0.0.3/32 10.0.0.21 11 100 0 ?
Table 57 describes the significant fields shown in the display.
Table 57 show ip bgp vpnv4 vrf Field Descriptions
Field
|
Description
|
Network
|
Displays the network address from the BGP table.
|
Next Hop
|
Displays the address of the BGP next hop.
|
Metric
|
Displays the BGP metric.
|
LocPrf
|
Displays the local preference.
|
Weight
|
Displays the BGP weight.
|
Path
|
Displays the BGP path per route.
|
The following example shows attributes for network 10.22.22.0 that include multipaths and a best path:
Router# show ip bgp vpnv4 all 10.22.22.0
BGP routing table entry for 10:1:10.22.22.0/24, version 50
Paths:(6 available, best #1)
Advertised to non peer-group peers:
10.22.7.8 (metric 11) from 10.11.3.4 (10.0.0.8)
Origin IGP, metric 0, localpref 100, valid, internal, multipath, best
Extended Community:RT:100:1
Originator:10.0.0.8, Cluster list:10.1.1.44
10.22.1.9 (metric 11) from 10.11.1.2 (10.0.0.9)
Origin IGP, metric 0, localpref 100, valid, internal, multipath
Extended Community:RT:100:1
Originator:10.0.0.9, Cluster list:10.1.1.22
Table 58 describes the significant fields shown in the display.
Table 58 show ip bgp vpnv4 all network-address Field Descriptions
Field
|
Description
|
BGP routing table entry for ... version
|
Internal version number of the table. This number is incremented whenever the table changes.
|
Paths
|
Number of autonomous system paths to the specified network. If multiple paths exist, one of the multipaths is designated the best path.
|
Multipath
|
Indicates the maximum paths configured (iBGP or eBGP).
|
Advertised to non peer-group peers
|
IP address of the BGP peers to which the specified route is advertised.
|
10.22.7.8 (metric 11) from 10.11.3.4 (10.0.0.8)
|
Indicates the next hop address and the address of the gateway that sent the update.
|
Origin
|
Indicates the origin of the entry. It can be one of the following values:
•IGP—Entry originated from Interior Gateway Protocol (IGP) and was advertised with a network router configuration command.
•incomplete—Entry originated from other than an IGP or Exterior Gateway Protocol (EGP) and was advertised with the redistribute router configuration command.
•EGP—Entry originated from an EGP.
|
metric
|
If shown, the value of the interautonomous system metric.
|
localpref
|
Local preference value as set with the set local-preference route-map configuration command. The default value is 100.
|
valid
|
Indicates that the route is usable and has a valid set of attributes.
|
internal/external
|
The field is internal if the path is learned via iBGP. The field is external if the path is learned via eBGP.
|
multipath
|
One of multiple paths to the specified network.
|
best
|
If multiple paths exist, one of the multipaths is designated the best path and this path is advertised to neighbors.
|
Extended Community
|
Route Target value associated with the specified route.
|
Originator
|
The router ID of the router from which the route originated when route reflector is used.
|
Cluster list
|
The router ID of all the route reflectors that the specified route has passed through.
|
The following example shows routes that BGP could not install in the VRF table:
Router# show ip bgp vpnv4 vrf xyz rib-failure
Network Next Hop RIB-failure RIB-NH Matches
Route Distinguisher: 2:2 (default for vrf bar)
10.1.1.2/32 10.100.100.100 Higher admin distance No
10.111.111.112/32 10.9.9.9 Higher admin distance Yes
Table 59 describes the significant fields shown in the display.
Table 59 show ip bgp vpnv4 vrf rib-failure Field Descriptions
Field
|
Description
|
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.
|
RIB-failure
|
Cause of the Routing Information Base (RIB) failure. Higher admin distance means that a route with a better (lower) administrative distance, such as a static route, already exists in the IP routing table.
|
RIB-NH Matches
|
Route status that applies only when Higher admin distance appears in the RIB-failure column and the bgp suppress-inactive command is configured for the address family being used. There are three choices:
•Yes—Means that the route in the RIB has the same next hop as the BGP route or that the next hop recurses down to the same adjacency as the BGP next hop.
•No—Means that the next hop in the RIB recurses down differently from the next hop of the BGP route.
•n/a—Means that the bgp suppress-inactive command is not configured for the address family being used.
|
The following example shows the information displayed on the active and standby Route Processors when they are configured for NSF/SSO: MPLS VPN.
Note In Cisco IOS Release 12.2(33)SXH, the Cisco IOS Software Modularity: MPLS Layer 3 VPNs feature incurred various infrastructure changes. The result of those changes affects the output of this command on the standby Route Processor (RP). In Cisco IOS Release 12.2(33)SXH, the standby RP does not display any output from the show ip bgp vpnv4 command.
Active Route Processor
Router# show ip bgp vpnv4 all labels
Network Next Hop In label/Out label
Route Distinguisher: 100:1 (vpn1)
10.12.12.12/32 0.0.0.0 16/aggregate(vpn1)
10.0.0.0/8 0.0.0.0 17/aggregate(vpn1)
Route Distinguisher: 609:1 (vpn0)
10.13.13.13/32 0.0.0.0 18/aggregate(vpn0)
Router# show ip bgp vpnv4 vrf vpn1 labels
Network Next Hop In label/Out label
Route Distinguisher: 100:1 (vpn1)
10.12.12.12/32 0.0.0.0 16/aggregate(vpn1)
10.0.0.0/8 0.0.0.0 17/aggregate(vpn1)
Standby Route Processor
Router# show ip bgp vpnv4 all labels
Route Distinguisher: 100:1
Route Distinguisher: 609:1
Router# show ip bgp vpnv4 vrf vpn1 labels
Route Distinguisher: 100:1
Table 60 describes the significant fields shown in the display.
Table 60 show ip bgp vpn4 labels Field Descriptions
Field
|
Description
|
Network
|
The network address from the BGP table.
|
Next Hop
|
The BGP next-hop address.
|
In label
|
The label (if any) assigned by this router.
|
Out label
|
The label assigned by the BGP next-hop router.
|
Masklen
|
The mask length of the network address.
|
The following example displays output, including the explicit-null label, from the show ip bgp vpnv4 all labels command on a CSC-PE router:
Router# show ip bgp vpnv4 all labels
Network Next Hop In label/Out label
Route Distinguisher: 100:1 (v1)
10.0.0.0/24 10.0.0.0 19/aggregate(v1)
10.0.0.1/32 10.0.0.0 20/nolabel
10.1.1.1/32 10.0.0.0 21/aggregate(v1)
10.10.10.10/32 10.0.0.1 25/exp-null
Table 61 describes the significant fields shown in the display.
Table 61 show ip bgp vpnv4 all labels Field Descriptions
Field
|
Description
|
Network
|
Displays the network address from the BGP table.
|
Next Hop
|
Displays the address of the BGP next hop.
|
In label
|
Displays the label (if any) assigned by this router.
|
Out label
|
Displays the label assigned by the BGP next-hop router.
|
Route Distinguisher
|
Displays an 8-byte value added to an IPv4 prefix to create a VPN IPv4 prefix.
|
The following example displays separate router IDs for each VRF in the output from an image in Cisco IOS Release 12.2(33)SRA, 12.2(31)SB2, 12.2(33)SXH, 12.4(20)T, and later releases with the Per-VRF Assignment of BGP Router ID feature configured. The router ID is shown next to the VRF name.
Router# show ip bgp vpnv4 all
BGP table version is 5, local router ID is 172.17.1.99
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
Route Distinguisher: 1:1 (default for vrf vrf_trans) VRF Router ID 10.99.1.2
*> 192.168.4.0 0.0.0.0 0 32768 ?
Route Distinguisher: 42:1 (default for vrf vrf_user) VRF Router ID 10.99.1.1
*> 192.168.5.0 0.0.0.0 0 32768 ?
Table 62 describes the significant fields shown in the display.
Table 62 show ip bgp vpnv4 all (VRF Router ID) Field Descriptions
Field
|
Description
|
Route Distinguisher
|
Displays an 8-byte value added to an IPv4 prefix to create a VPN IPv4 prefix.
|
vrf
|
Name of the VRF.
|
VRF Router ID
|
Router ID for the VRF.
|
Related Commands
Command
|
Description
|
show ip vrf
|
Displays the set of defined VRFs and associated interfaces.
|
show ip community-list
To display configured community lists, use the show ip community-list command in user or privileged EXEC mode.
show ip community-list [community-list-number | community-list-name] [exact-match]
Syntax Description
community-list-number
|
(Optional) A standard or expanded community list number in the range from 1 to 500.
|
community-list-name
|
(Optional) Community list name. The community list name can be standard or expanded.
|
exact-match
|
(Optional) Displays only routes that have an exact match.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.0(10)S
|
Named community list support was added.
|
12.0(16)ST
|
Named community lists support was integrated into Cisco IOS Release 12.0(16)ST.
|
12.1(9)E
|
Named community lists support was integrated into Cisco IOS Release 12.1(9)E.
|
12.2(8)T
|
Named community lists support was integrated into Cisco IOS Release 12.2(8)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command can be used without any arguments or keywords. If no arguments are specified, this command will display all community lists. However, the community list name or number can be specified when entering the show ip community-list command. This option can be useful for filtering the output of this command and verifying a single named or numbered community list.
Examples
The following sample output is similar to the output that will be displayed when the
