BGP Commands

Use the commands in this chapter to configure and monitor Border Gateway Protocol (BGP). For BGP configuration information and examples, refer to the Configuring BGP chapter of the Network Protocols Configuration Guide, Part 1.

Network Protocols Command Reference, Part 1

P1R-355

BGP Commands aggregate-address

aggregate-address
To create an aggregate entry in a Border Gateway Protocol (BGP) routing table, use the aggregate-address command in router configuration mode. To disable this function, use the no form of this command. aggregate-address address mask [as-set] [summary-only] [suppress-map map-name] [advertise-map map-name] [attribute-map map-name] no aggregate-address address mask [as-set] [summary-only] [suppress-map map-name] [advertise-map map-name] [attribute-map map-name]

Syntax Description

address mask as-set summary-only suppress-map map-name advertise-map map-name attribute-map map-name

Aggregate address. Aggregate mask. (Optional) Generates autonomous system set path information. (Optional) Filters all more specific routes from updates. (Optional) Name of route map used to select the routes to be suppressed. (Optional) Name of route map used to select the routes to create AS-SET origin communities. (Optional) Name of the route map used to set the attribute of the aggregate route.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

You can implement aggregate routing in BGP either by redistributing an aggregate route into BGP or by using this conditional aggregate routing feature. Using the aggregate-address command with no keywords will create an aggregate entry in the BGP routing table if there are any more-specific BGP routes available that fall in the specified range. The aggregate route will be advertised as coming from your autonomous system and has the atomic aggregate attribute set to show that information might be missing. (By default, the atomic aggregate attribute is set unless you specify the as-set keyword.)

Network Protocols Command Reference, Part 1

P1R-356

BGP Commands aggregate-address

Using the as-set keyword creates an aggregate entry using the same rules that the command follows without this keyword, but the path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized. Do not use this form of aggregate-address when aggregating many paths, because this route must be continually withdrawn and re-updated as autonomous system path reachability information for the summarized routes changes. Using the summary-only keyword not only creates the aggregate route (for example, 193.*.*.*) but will also suppress advertisements of more-specific routes to all neighbors. If you want to suppress only advertisements to certain neighbors, you may use the neighbor distribute-list command, with caution. If a more specific route leaks out, all BGP speakers will prefer that route over the less-specific aggregate you are generating (using longest-match routing). Using the suppress-map keyword creates the aggregate route but suppresses advertisement of specified routes. You can use the match clauses of route maps to selectively suppress some more specific routes of the aggregate and leave others unsuppressed. IP access lists and autonomous system path access lists match clauses are supported. Using the advertise-map keyword selects specific routes that will be used to build different components of the aggregate route, such as AS_SET or community. This form of the aggregate-address command is useful when the components of an aggregate are in separate autonomous systems and you want to create an aggregate with AS_SET, and advertise it back to some of the same autonomous systems. You must remember to omit the specific autonomous system numbers from the AS_SET to prevent the aggregate from being dropped by the BGP loop detection mechanism at the receiving router. IP access lists and autonomous system path access lists match clauses are supported. Using the attribute-map keyword allows attributes of the aggregate route to be changed. This form of the aggregate-address command is useful when one of the routes forming the AS_SET is configured with an attribute such as the community no-export attribute, which would prevent the aggregate route from being exported. An attribute map route map can be created to change the aggregate attributes.

Examples

The following example creates an aggregate address. The path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized.
router bgp 65000 aggregate-address 10.0.0.0 255.0.0.0 as-set

In the following example, a route map called map-one is created matching on an as-path access list. The path advertised for this route will be an AS_SET consisting of elements contained in paths that are matched in the route map.
ip as-path access-list 1 deny ^1234_ ip as-path access-list 1 permit .* ! route-map map-one match ip as-path 1 ! router bgp 65000 aggregate-address 10.0.0.0 255.0.0.0 as-set advertise-map map-one

Network Protocols Command Reference, Part 1

P1R-357

BGP Commands aggregate-address

Related Commands

Command match as-path match ip address

Description Matches a BGP autonomous system path access list. Distributes any routers that have a destination network number address that is permitted by a standard or extended access list. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing.

route-map (IP)

Network Protocols Command Reference, Part 1

P1R-358

BGP Commands auto-summary (BGP)

auto-summary (BGP)
To restore the default behavior of automatic summarization of subnet routes into network-level routes, use the auto-summary command in router configuration mode. To disable this feature and transmit subprefix routing information across classful network boundaries, use the no form of this command. auto-summary no auto-summary

Syntax Description

This command has no arguments or keywords.

Defaults

The behavior of this command is enabled by default (the software summarizes subprefixes to the classful network boundary when crossing classful network boundaries).

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

Route summarization reduces the amount of routing information in the routing tables. By default, BGP does not accept subnets redistributed from an IGP. To advertise and carry subnet routes in BGP, use an explicit network command or the no auto-summary command. If you disable auto-summarization and have not entered a network command, you will not advertise network routes for networks with subnet routes unless they contain a summary route. In the following example, network numbers are not summarized automatically:
router bgp 6 no auto-summary

Network Protocols Command Reference, Part 1

P1R-359

BGP Commands bgp always-compare-med

bgp always-compare-med
To allow the comparison of the Multi Exit Discriminator (MED) for paths from neighbors in different autonomous systems, use the bgp always-compare-med command in router configuration mode. To disallow the comparison, use the no form of this command. bgp always-compare-med no bgp always-compare-med

Syntax Description

This command has no arguments or keywords.

Defaults

The Cisco IOS software does not compare MEDs for paths from neighbors in different autonomous systems.

Command Modes

Router configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

The MED is one of the parameters that is considered when selecting the best path among many alternative paths. The path with a lower MED is preferred over a path with a higher MED. By default, during the best-path selection process, MED comparison is done only among paths from the same autonomous system. This command changes the default behavior by allowing comparison of MEDs among paths regardless of the autonomous system from which the paths are received.

Examples

The following example configures the BGP speaker in autonomous system 100 to compare MEDs among alternative paths, regardless of the autonomous system from which the paths are received:
router bgp 109 bgp always-compare-med

Network Protocols Command Reference, Part 1

P1R-360

BGP Commands bgp bestpath as-path ignore

bgp bestpath as-path ignore

To prevent the router from considering as-path as a factor in the algorithm for choosing a route, use the bgp bestpath as-path ignore command in router configuration mode. To allow the router to consider as-path in choosing a route, use the no form of this command. bgp bestpath as-path ignore no bgp bestpath as-path ignore

Syntax Description

This command has no arguments or keywords.

Defaults

The router considers as-path in choosing a route.

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Examples

The following example prevents the BGP router from considering as-path as a factor in choosing a route.
router bgp 210 bgp bestpath as-path ignore

Related Commands

Command show ip bgp neighbors

Description
Displays information about the TCP and BGP connections to neighbors.

Network Protocols Command Reference, Part 1

P1R-361

BGP Commands bgp bestpath compare-routerid

bgp bestpath compare-routerid

To compare similar routes received from external Border Gateway Protocol (eBGP) peers during the best path selection process and switch the bestpath to the route with the lowest router ID, use the bgp bestpath compare-routerid command in router configuration mode. To return the router to the default, use the no form of this command. bgp bestpath compare-routerid no bgp bestpath compare-routerid

Syntax Description

This command has no arguments or keywords.

Defaults

BGP does not compare similar paths received from eBGP peers during the best path selection process and switch the bestpath to the route with the lowest router ID.

Command Modes

Router configuration

Command History

Release 12.0 12.0S 12.0ST

Modification This command was introduced. This command was introduced. This command was introduced.

Usage Guidelines

By default, during the best path selection process, when BGP receives similar routes from eBGP peers (all the attributes are the same except for the router ID), the best path is not switched to the route with the lowest router ID if that route was not the first route received. If the bgp bestpath compare-routerid command is enabled, then similar routes are compared and the best path is switched to the route with the lowest router ID.

Examples

The following example shows the BGP speaker in autonomous system 500 configured to compare the router IDs of similar paths, regardless of the autonomous system from which the paths are received:
router bgp 500 bgp bestpath compare-routerid

Related Commands

Command show ip bgp

Description Displays entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-362

BGP Commands bgp bestpath med-confed

bgp bestpath med-confed

To enable MED comparison among paths learned from confederation peers, use the bgp bestpath med-confed command in router configuration mode. To prevent the software from considering the MED attribute in comparing paths, use the no form of this command. bgp bestpath med-confed no bgp bestpath med-confed

Syntax Description

This command has no arguments or keywords.

Defaults

The software does not consider the MED attribute when choosing among paths learned from confederation peers.

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Usage Guidelines

The comparison between MEDs is only made if there are no external ASs in the path (an external AS is an AS that is not within the confederation). If there is an external AS in the path, then the external MED is passed transparently through the confederation, and the comparison is not made. For example, assume that AS 65000, 65001, 65002, and 65004 are part of the confederation; AS1 is not; and we are comparing route A with four paths. If bgp bestpath med-confed is enabled, path 1 would be chosen. The fourth path has a lower MED, but it is not involved in the MED comparison because there is an external AS in this path. path= 65000 65004, med=2 path= 65001 65004, med=3 path= 65002 65004, med=4 path= 65003 1, med=1

Examples

The following command enables the BGP router to compare MED values for paths learned from confederation peers.
router bgp 210 bgp bestpath med-confed

Network Protocols Command Reference, Part 1

P1R-363

BGP Commands bgp bestpath med-confed

Related Commands

Command show ip bgp show ip bgp neighbors

Description Display entries in the BGP routing table. Displays information about the TCP and BGP connections to neighbors.

Network Protocols Command Reference, Part 1

P1R-364

BGP Commands bgp bestpath missing-as-worst

bgp bestpath missing-as-worst

To have Cisco IOS software consider a missing MED attribute in a path as having a value of infinity, making the path without a MED value the least desirable path, use the bgp bestpath missing-as-worst command in router configuration mode. To return the router to the default (assign a value of 0 to the missing MED), use the no form of this command. bgp bestpath missing-as-worst no bgp bestpath missing-as-worst

Syntax Description

This command has no arguments or keywords.

Defaults

The software assigns a value of 0 to the missing MED, causing the path with the missing MED attribute to be considered the best path.

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Examples

The following command specifies that the BGP router to consider a missing MED attribute in a path as having a value of infinity, making this path the least desirable path.
router bgp 210 bgp bestpath missing-as-worst

Related Commands

Command show ip bgp show ip bgp neighbors

Description Display entries in the BGP routing table. Displays information about the TCP and BGP connections to neighbors.

Network Protocols Command Reference, Part 1

P1R-365

BGP Commands bgp client-to-client reflection

bgp client-to-client reflection

To restore route reflection from a BGP route reflector to clients, use the bgp client-to-client reflection command in router configuration mode. To disable client-to-client reflection, use the no form of this command. bgp client-to-client reflection no bgp client-to-client reflection

Syntax Description

This command has no arguments or keywords.

Defaults

When a route reflector is configured, the route reflector reflects routes from a client to other clients.

Command Modes

Router configuration

Command History

Release 11.1

Modification This command was introduced.

Usage Guidelines

By default, the clients of a route reflector are not required to be fully meshed and the routes from a client are reflected to other clients. However, if the clients are fully meshed, route reflection is not required. Use the no bgp client-to-client reflection command to disable client-to-client reflection.

Examples

In the following example, the local router is a route reflector. The three neighbors are fully meshed, so client-to-client reflection is disabled.
router bgp 5 neighbor 10.24.95.22 route-reflector-client neighbor 10.24.95.23 route-reflector-client neighbor 10.24.95.24 route-reflector-client no bgp client-to-client reflection

Related Commands

Command bgp cluster-id neighbor route-reflector-client show ip bgp

Description Configures the cluster ID if the BGP cluster has more than one route reflector. Configures the router as a BGP route reflector and configure the specified neighbor as its client. Display entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-366

BGP Commands bgp cluster-id

bgp cluster-id
To configure the cluster ID if the BGP cluster has more than one route reflector, use the bgp cluster-id command in router configuration mode. To remove the cluster ID, use the no form of this command. bgp cluster-id cluster-id no bgp cluster-id cluster-id

Syntax Description

cluster-id

Cluster ID of this router acting as a route reflector; maximum of 4 bytes.

Defaults

The router ID of the single route reflector in a cluster

Command Modes

Router configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

Together, a route reflector and its clients form a cluster. Usually a cluster of clients will have a single route reflector. In that case, the cluster is identified by the router ID of the route reflector. In order to increase redundancy and avoid a single point of failure, a cluster might have more than one route reflector. In this case, all route reflectors in the cluster must be configured with the 4-byte cluster ID so that a route reflector can recognize updates from route reflectors in the same cluster. If the cluster has more than one route reflector, use this command to configure the cluster ID.

Examples

In the following example, the local router is one of the route reflectors serving the cluster. It is configured with the cluster ID to identify the cluster.
router bgp 5 neighbor 172.16.70.24 route-reflector-client bgp cluster-id 50000

Related Commands

Command bgp client-to-client reflection neighbor route-reflector-client show ip bgp

Description Restores route reflection from a BGP route reflector to clients. Configures the router as a BGP route reflector and configure the specified neighbor as its client. Display entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-367

BGP Commands bgp confederation identifier

bgp confederation identifier

To specify a BGP confederation identifier, use the bgp confederation identifier command in router configuration mode. To remove the confederation identifier, use the no form of this command. bgp confederation identifier autonomous-system no bgp confederation identifier autonomous-system

Syntax Description

autonomous-system

Autonomous system number that internally includes multiple autonomous systems.

Defaults

No confederation identifier is configured.

Command Modes

Router configuration

Command History

Release 10.3

Modification This command was introduced.

Usage Guidelines

One way to reduce the IBGP mesh is to divide an autonomous system into multiple autonomous systems and group them into a single confederation. Each autonomous system is fully meshed within itself, and has a few connections to another autonomous system in the same confederation. Even though the peers in different autonomous systems have EBGP sessions, they exchange routing information as if they are IBGP peers. Specifically, the next-hop and local preference information is preserved. This enables to you to retain a single Interior Gateway Protocol (IGP) for all the autonomous systems. To the outside world, the confederation looks like a single autonomous system.

Examples

In the following example, the autonomous system is divided into autonomous systems 4001, 4002, 4003, 4004, 4005, 4006, and 4007 and identified by the confederation identifier 5. Neighbor 10.2.3.4 is someone inside your routing domain confederation. Neighbor 10.4.5.6 is someone outside your routing domain confederation. To the outside world, there appears to be a single autonomous system with the number 5.
router bgp 4001 bgp confederation bgp confederation neighbor 10.2.3.4 neighbor 10.4.5.6 identifier 5 peers 4002 4003 4004 4005 4006 4007 remote-as 4002 remote-as 510

Related Commands

Command bgp confederation peers

Description Configures the autonomous systems that belong to the confederation.

Network Protocols Command Reference, Part 1

P1R-368

BGP Commands bgp confederation peers

bgp confederation peers

To configure the autonomous systems that belong to the confederation, use the bgp confederation peers command in router configuration mode. To remove an autonomous system from the confederation, use the no form of this command. bgp confederation peers autonomous-system [autonomous-system] no bgp confederation peers autonomous-system [autonomous-system]

Syntax Description

autonomous-system

Autonomous system number.

Defaults

No confederation peers are configured.

Command Modes

Router configuration

Command History

Release 10.3

Modification This command was introduced.

Usage Guidelines

The autonomous systems specified in this command are visible internally to a confederation. Each autonomous system is fully meshed within itself. The bgp confederation identifier command specifies the confederation to which the autonomous systems belong.

Examples

The following example specifies that autonomous systems 1090, 1091, 1092, and 1093 belong to a single confederation:
router bgp 1090 bgp confederation peers 1091 1092 1093

Related Commands

Command bgp confederation identifier

Description Specifies a BGP confederation identifier.

Network Protocols Command Reference, Part 1

P1R-369

BGP Commands bgp dampening

bgp dampening
To enable BGP route dampening or change various BGP route dampening factors, use the bgp dampening command in global configuration mode. To disable the function or restore the default values, use the no form of this command. bgp dampening [half-life reuse suppress max-suppress-time] [route-map map] no bgp dampening [half-life reuse suppress max-suppress-time] [route-map map]

Syntax Description

half-life

(Optional) Time (in minutes) after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period (which is 15 minutes by default). 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 15 minutes. (Optional) Reuse values based on accumulated penalties. If the penalty for a flapping route decreases enough to fall below this value, the route is unsuppressed. The process of unsuppressing routes occurs at 10-second increments. The range of the reuse value is 1 to 20000; the default is 750. (Optional) A route is suppressed when its penalty exceeds this limit. The range is 1 to 20000; the default is 2000. (Optional) Maximum time (in minutes) a route can be suppressed. The range is from 1 to 20000; the default is 4 times the half-life. If the half-life value is allowed to default, the maximum suppress time defaults to 60 minutes. When the max-suppress-time is configured, the maximum penalty will never be exceeded, regardless of the number of times that the prefix dampens. The maximum penalty is computed with the following formula: Max penalty = reuse-limit *2^(maximum suppress time/half time) (Optional) Name of route map that controls where BGP route dampening is enabled.

reuse

suppress max-suppress-time

route-map map

Defaults

This command is disabled by default. half-life is 15 minutes reuse is 750 suppress is 2000 max-suppress-time is 4 times half-life

Command Modes

Global configuration

Command History

Release 11.0

Modification This command was introduced.

Network Protocols Command Reference, Part 1

P1R-370

BGP Commands bgp dampening

Usage Guidelines

If this command is used with no arguments, it enables BGP route dampening. The arguments half-life, reuse, suppress, and max-suppress-time are position-dependent. Therefore, if any of them are used, they must all be specified. When BGP dampening is configured and a prefix is withdrawn, BGP considers the withdrawn prefix as a flap and increases the penalty by a 1000. If BGP receives an attribute change, BGP increases the penalty by 500. If then the prefix has been withdrawn, BGP keeps the prefix in the BGP table as a history entry. If the prefix has not been withdrawn by the neighbor and BGP is not using this prefix, the prefix is marked as dampened. Dampened prefixes are not used in the BGP decision process and not installed to the routing table.

Examples

The following example sets the half-life to 30 minutes, the reuse value to 1500, the suppress value to 10000, and the maximum suppress time to 120 minutes:
bgp dampening 30 1500 10000 120

Related Commands

Command clear ip bgp dampening clear ip bgp flap-statistics show ip bgp dampened-paths show ip bgp flap-statistics

Description Clears BGP route dampening information and unsuppress the suppressed routes. Clears BGP flap statistics. Display BGP dampened routes. Specifies a BGP Display BGP flap statistics.

Network Protocols Command Reference, Part 1

P1R-371

BGP Commands bgp default local-preference

bgp default local-preference

To change the default local preference value, use the bgp default local-preference command in router configuration mode. To return to the default setting, use the no form of this command. bgp default local-preference value no bgp default local-preference value

Syntax Description

value

Local preference value from 0 to 4294967295. Higher is more preferred.

Defaults

Local preference value of 100

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

Generally, the default value of 100 allows you to easily define a particular path as less preferable than paths with no local preference attribute. The preference is sent to all routers and access servers in the local autonomous system.

Examples

The following example raises the default local preference value from the default of 100 to 200:
router bgp 200 bgp default local-preference 200

Related Commands

Command set local-preference

Description Specifies a preference value for the autonomous system path.

Network Protocols Command Reference, Part 1

P1R-372

BGP Commands bgp deterministic-med

bgp deterministic-med
To have Cisco IOS software enforce the deterministic comparison of the Multi Exit Discriminator (MED) variable between all paths received from the same autonomous system, use the bgp deterministic-med command in router configuration mode. To disable the comparison, use the no form of this command. bgp deterministic med no bgp deterministic med

Syntax Description

This command has no arguments or keywords.

Defaults

The software does not enforce the deterministic comparison of the MED variable between all paths received from the same autonomous system.

Command Modes

Router configuration Address-family configuration

Command History

Release 11.1

Modification This command was introduced.

Usage Guidelines

After the bgp always-compare-med command is configured, all paths for the same prefix that are received from different neighbors, which are in the same autonomous system, will be grouped together and sorted by the ascending MED value (received-only paths are ignored and not grouped or sorted). The best path selection algorithm will then pick the best paths using the existing rules; the comparison is made on a per neighbor autonomous system basis and then global basis. The grouping and sorting of paths occurs immediately after this command is entered. For correct results, all routers in the local autonomous system must have this command enabled (or disabled).

Examples

The following example specifies that the BGP router compare MED variables when choosing among routes advertised by the same subautonomous system within a confederation:
Router(config)# router bgp 204 Router(config-router)# bgp deterministic-med

The following example show ip bgp command output illustrates how route selection is affected by the configuration of the bgp deterministic-med command. The order in which routes are received affects how routes are selected for best path selection when the bgp deterministic-med command is not enabled.

Network Protocols Command Reference, Part 1

P1R-373

BGP Commands bgp deterministic-med

The following sample output from the show ip bgp command shows three paths that are received for the same prefix (10.100.0.0), and the bgp deterministic-med command is not enabled:
router# show ip bgp 10.100.0.0 BGP routing table entry for 10.100.0.0/16, version 40 Paths: (3 available, best #3, advertised over IBGP, EBGP) 109 192.168.43.10 from 192.168.43.10 (192.168.43.1) Origin IGP, metric 0, localpref 100, valid, internal 2051 192.168.43.22 from 192.168.43.22 (192.168.43.2) Origin IGP, metric 20, localpref 100, valid, internal 2051 192.168.43.3 from 192.168.43.3 (10.4.1.1) Origin IGP, metric 30, valid, external, best

If the bgp deterministic-med command is not enabled on the router, the route selection can be affected by the order in which the routes are received. Consider the following scenario in which a router received three paths for the same prefix: The clear ip bgp * command is entered to clear all routes in the local routing table.
Router# clear ip bgp *

The show ip bgp command is issued again after the routing table has been repopulated. Note that the order of the paths changed after clearing the BGP session. The results of the selection algorithm also changed. This occurred because the order in which the paths were received was different for the second session.
Router# show ip bgp 10.100.0.0 BGP routing table entry for 10.100.0.0/16, version 2 Paths: (3 available, best #3, advertised over EBGP) 109 192.168.43.10 from 192.168.43.10 (192.168.43.1) Origin IGP, metric 0, localpref 100, valid, internal 2051 192.168.43.3 from 192.168.43.3 (10.4.1.1) Origin IGP, metric 30, valid, external 2051 192.168.43.22 from 192.168.43.22 (192.168.43.2) Origin IGP, metric 20, localpref 100, valid, internal, best

If the bgp deterministic-med command is enabled, then the result of the selection algorithm will always be the same, regardless of the order in which the paths are received by the local router. The following output is always generated when the bgp deterministic-med command is entered on the local router in this scenario:
Router# show ip bgp 10.100.0.0 BGP routing table entry for 10.100.0.0/16, version 15 Paths: (3 available, best #1, advertised over EBGP) 109 192.168.43.10 from 192.168.43.10 (192.168.43.1) Origin IGP, metric 0, localpref 100, valid, internal, best 3 192.168.43.22 from 192.168.43.22 (192.168.43.2) Origin IGP, metric 20, localpref 100, valid, internal 3 192.168.43.3 from 192.168.43.3 (10.4.1.1) Origin IGP, metric 30, valid, external

Related Commands

Command clear ip bgp

Description Resets a BGP connection or session.

Network Protocols Command Reference, Part 1

P1R-374

BGP Commands bgp deterministic-med

show ip bgp show ip bgp neighbors

Displays entries in the BGP routing table. Displays information about the TCP and BGP connections to neighbors.

Network Protocols Command Reference, Part 1

P1R-375

BGP Commands bgp log-neighbor-changes

bgp log-neighbor-changes
To enable logging of BGP neighbor resets, use the bgp log-neighbor-changes command in router configuration mode. To disable the logging of changes in BGP neighbor adjacencies, use the no form of this command. bgp log-neighbor-changes no bgp log-neighbor-changes

Syntax Description

This command has no arguments or keywords.

Defaults

No BGP neighbor changes are logged.

Command Modes

Router configuration

Command History

Release 11.1CC and 12.0

Modification This command was introduced.

Usage Guidelines

The bgp log-neighbor-changes command enables logging of BGP neighbor status changes (up or down) and resets for troubleshooting network connectivity problems and measuring network stability. Unexpected neighbor resets might indicate high error rates or high packet loss in the network and should be investigated. Using the bgp log-neighbor-changes command to enable status change message logging does not cause a substantial performance impact, unlike, for example, enabling per BGP update debugging. If the UNIX syslog facility is enabled, messages are sent to the UNIX host running the syslog daemon so that the messages can be stored and archived. If the UNIX syslog facility is not enabled, the status change messages are retained in the routers internal buffer, and are not stored to disk. You can set the size of this buffer, which is dependent upon the available RAM, using the logging buffered command. The neighbor status change messages are not tracked if bgp log-neighbor changes is not enabled, except for the reset reason, which is always available as output of the show ip bgp neighbor command. The log messages display the following reasons for changes in a neighbors status:
BGP protocol initialization No memory for path entry No memory for attribute entry No memory for prefix entry No memory for aggregate entry No memory for dampening info No memory for BGP updates BGP Notification received Erroneous BGP Update received User reset request

Network Protocols Command Reference, Part 1

P1R-376

BGP Commands bgp log-neighbor-changes

Peer timeout Password change Error during connection collision Peer closing down the session Peer exceeding maximum prefix limit Interface flap Router ID changed Neighbor deleted Member added to peergroup Administratively shutdown Remote AS changed RR client configuration modification Soft reconfiguration modification

The eigrp log-neighbor-changes command enables logging of Enhanced IGRP neighbor adjacencies, but messages for BGP neighbors are logged only if they are specifically enabled with the bgp log-neighbor-changes command. Use the show logging command to display the log for the BGP neighbor changes.

Examples

The following configuration will log neighbor changes for BGP:

bgp router 100 bgp log-neighbor-changes

Related Commands

Command logging buffered show ip bgp neighbors show logging

Description Enables logging of message to an internal buffer. Displays information about the TCP and BGP connections to neighbors. Displays the state of logging (syslog).

Network Protocols Command Reference, Part 1

P1R-377

BGP Commands bgp fast-external-fallover

bgp fast-external-fallover
To immediately reset the BGP sessions of any directly adjacent external peers if the link used to reach them goes down, use the bgp fast-external-fallover command in router configuration mode. To disable this function, use the no form of this command. bgp fast-external-fallover no bgp fast-external-fallover

Syntax Description

This command has no arguments or keywords.

Defaults

The behavior of this command is enabled by default.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Examples

The following example disables the automatic resetting of BGP sessions:

router bgp 109 no bgp fast-external-fallover

Network Protocols Command Reference, Part 1

P1R-378

BGP Commands bgp router-id

bgp router-id
To configure a fixed router ID for a BGP-speaking router, use the bgp router-id command in router configuration mode. To remove the bgp router-id command from the configuration file and restore the default value of the router ID, use the no form of this command. bgp router-id ip-address no bgp router-id ip-address

Syntax Description

ip-address

IP address of the router.

Defaults

The router ID is set to the IP address of a loopback interface if one is configured. If no virtual interfaces are configured, the highest IP address is configured for a physical interface on that router. Peering sessions will be reset if the router ID is changed.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

Use this command to configure a fixed router ID as an identifier of the router running BGP. A loopback interface, if one is configured, is more effective than a fixed interface as an identifier because there is no physical link to go down.

Examples

The following example shows the local router configured with the router ID of 192.168.70.24:
router bgp 100 no synchronization bgp router-id 192.168.70.24

Related Commands

Command show ip bgp

Description Displays entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-379

BGP Commands clear ip bgp

clear ip bgp
To reset a BGP connection using BGP soft reconfiguration, use the clear ip bgp command in privileged EXEC mode at the system prompt. clear ip bgp {* | address | peer-group name} [soft [in | out]]

Syntax Description

* address peer-group-name soft in | out

Specifies that all current BGP sessions will be reset. Specifies that only the identified BGP neighbor will be reset. Specifies that the specified BGP peer group will be reset. (Optional) Soft reset. Does not reset the session. (Optional) Triggers inbound or outbound soft reconfiguration. If the in or out option is not specified, both inbound and outbound soft reset is triggered.

Defaults

No reset is initiated.

Command Modes

Privileged EXEC

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

If you specify BGP soft reconfiguration, by including the soft keyword, the sessions are not reset and the router sends all routing updates again. To generate new inbound updates without resetting the BGP session, the local BGP speaker should store all received updates without modification regardless of whether it is accepted by the inbound policy, using the neighbor soft-reconfiguration command. This process is memory intensive and should be avoided if possible. Outbound BGP soft configuration does not have any memory overhead. You can trigger an outbound reconfiguration on the other side of the BGP session to make the new inbound policy take effect. Use this command whenever any of the following conditions occur:

Additions or changes to the BGP-related access lists Changes to BGP-related weights Changes to BGP-related distribution lists Changes in the BGP timers specifications Changes to the BGP administrative distance Changes to BGP-related route maps

Examples

The following example resets all current BGP sessions:

clear ip bgp *

Network Protocols Command Reference, Part 1

P1R-380

BGP Commands clear ip bgp

Related Commands

Command clear ip bgp neighbor soft-reconfiguration show ip bgp timers bgp

Description Resets a BGP connection using BGP soft reconfiguration. Configures the Cisco IOS software to start storing updates. Display entries in the BGP routing table. Adjusts BGP network timers.

Network Protocols Command Reference, Part 1

P1R-381

BGP Commands clear ip bgp dampening

clear ip bgp dampening

To clear BGP route dampening information and unsuppress the suppressed routes, use the clear ip bgp dampening command in privileged EXEC mode. clear ip bgp dampening [address mask]

Syntax Description

address mask

(Optional) IP address of the network about which to clear dampening information. (Optional) Network mask applied to the address.

Command Modes

Privileged EXEC

Command History

Release 11.0

Modification This command was introduced.

Examples

The following example clears route dampening information about the route to network 192.168.0.0 and unsuppresses its suppressed routes:
clear ip bgp dampening 192.168.0.0 255.255.0.0

Related Commands

Command bgp dampening show ip bgp dampened-paths

Description Enables BGP route dampening or change various BGP route dampening factors. Display BGP dampened routes.

Network Protocols Command Reference, Part 1

P1R-382

BGP Commands clear ip bgp flap-statistics

clear ip bgp flap-statistics

To clear BGP flap statistics, use the clear ip bgp flap-statistics command in privileged EXEC mode. clear ip bgp flap-statistics [{regexp regexp} | {filter-list list} | {address mask}] clear ip bgp [address] flap-statistics

Syntax Description

address

(Optional) Clears flap statistics for a single entry at this IP address. If this argument is placed before flap-statistics, the router clears flap statistics for all paths from the neighbor at this address. (Optional) Clears flap statistics for all the paths that match the regular expression. (Optional) Clears flap statistics for all the paths that pass the access list. (Optional) Network mask applied to the address.

regexp regexp filter-list list mask

Defaults

No statistics are cleared.

Command Modes

Privileged EXEC

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

If no arguments or keywords are specified, the router will clear BGP flap statistics for all routes. The flap statistics for a route are also cleared when a BGP peer is reset. Although the reset withdraws the route, there is no penalty applied in this instance even though route flap dampening is enabled.

Examples

The following example clears all of the flap statistics for paths that pass access list 3:
clear ip bgp flap-statistics filter-list 3

Related Commands

Command bgp dampening

Description Enables BGP route dampening or change various BGP route dampening factors.

Network Protocols Command Reference, Part 1

P1R-383

BGP Commands clear ip bgp peer-group

clear ip bgp peer-group

To remove all the members of a BGP peer group, use the clear ip bgp peer-group command in privileged EXEC mode. clear ip bgp peer-group tag

Syntax Description

tag

Name of the BGP peer group to clear.

Defaults

No BGP peer group members are cleared.

Command Modes

Privileged EXEC

Command History

Release 11.0

Modification This command was introduced.

Examples

The following example removes all members from the BGP peer group internal:
clear ip bgp peer-group internal

Related Commands

Command neighbor peer-group (assigning members)

Description Configures a BGP neighbor to be a member of a peer group.

Network Protocols Command Reference, Part 1

P1R-384

BGP Commands default-information originate (BGP)

default-information originate (BGP)

To control the redistribution of a protocol or network into the BGP, use the default-information originate command in router configuration mode. To disable this function, use the no form of this command. default-information originate no default-information originate

Syntax Description

This command has no arguments or keywords.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

The default-information originate command should be used if the network operator needs to control the redistribution of default routes. Using the default-information originate command in BGP is similar to using the network command. However, to achieve the same result as configuring the network command with the route 0.0.0.0, the default-information originate command requires an explicit redistribution of the route 0.0.0.0. The network command requires only that route 0.0.0.0 is specified in the Interior Gateway Protocol (IGP) routing table. For this reason, the network command is preferred for redistributing default routes and protocols into BGP.

Examples

The following router configuration mode example configures BGP to redistribute OSPF into BGP:
router bgp 164 default-information originate redistribute ospf 109

Related Commands

Command neighbor ebgp-multihop network (BGP) redistribute (IP)

Description Accepts and attempt BGP connections to external peers residing on networks that are not directly connected. Specifies the list of networks for the BGP routing process. Redistributes routes from one routing domain into another routing domain.

Network Protocols Command Reference, Part 1

P1R-385

BGP Commands default-metric (BGP)

default-metric (BGP)
To set default metric values for the BGP routing protocol, use this form of the default-metric command in router configuration mode. To return to the default state, use the no form of this command. default-metric number no default-metric number

Syntax Description

number

Default metric value appropriate for the specified routing protocol.

Defaults

Built-in, automatic metric translations, as appropriate for each routing protocol

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

The default-metric command is used in conjunction with the redistribute router configuration command to cause the current routing protocol to use the same metric value for all redistributed routes. A default metric helps solve the problem of redistributing routes with incompatible metrics. Whenever metrics do not convert, using a default metric provides a reasonable substitute and enables the redistribution to proceed. In BGP, this command sets the Multi Exit Discriminator (MED) metric. (The name of this metric for BGP Versions 2 and 3 is INTER_AS.)

Examples

The following example shows a router in autonomous system 109 using both the RIP and the OSPF routing protocols. The example advertises OSPF-derived routes using the RIP protocol and assigns the IGRP-derived routes a RIP metric of 10.
router rip default-metric 10 redistribute ospf 109

Related Commands

Command redistribute

Description Redistributes routes from one routing domain into another routing domain.

Network Protocols Command Reference, Part 1

P1R-386

BGP Commands distance bgp

distance bgp
To allow the use of external, internal, and local administrative distances that could be a better route to a node, use the distance bgp command in router configuration mode. To return to the default values, use the no form of this command. distance bgp external-distance internal-distance local-distance no distance bgp

Syntax Description

external-distance

Administrative distance for BGP external routes. External routes are routes for which the best path is learned from a neighbor external to the autonomous system. Acceptable values are from 1 to 255. The default is 20. Routes with a distance of 255 are not installed in the routing table. Administrative distance for BGP internal routes. Internal routes are those routes that are learned from another BGP entity within the same autonomous system. Acceptable values are from 1 to 255. The default is 200. Routes with a distance of 255 are not installed in the routing table. Administrative distance for BGP local routes. Local routes are those networks listed with a network router configuration command, often as back doors, for that router or for networks that are being redistributed from another process. Acceptable values are from 1 to 255. The default is 200. Routes with a distance of 255 are not installed in the routing table.

internal-distance

local-distance

Defaults

external-distance: 20 internal-distance: 200 local-distance: 200

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

An administrative distance is a rating of the trustworthiness of a routing information source, such as an individual router or a group of routers. Numerically, an administrative distance is an integer between 0 and 255. In general, the higher the value, the lower the trust rating. An administrative distance of 255 means the routing information source cannot be trusted at all and should be ignored. Use this command if another protocol is known to be able to provide a better route to a node than was actually learned via external BGP, or if some internal routes should really be preferred by BGP.

Network Protocols Command Reference, Part 1

P1R-387

BGP Commands distance bgp

Note

Changing the administrative distance of BGP internal routes is considered dangerous and is not recommended. One problem that can arise is the accumulation of routing table inconsistencies, which can break routing.

Examples

In the following example, internal routes are known to be preferable to those learned through the IGP, so the administrative distance values are set accordingly:
router bgp 109 network 10.108.0.0 neighbor 192.168.6.6 remote-as 123 neighbor 172.16.1.1 remote-as 47 distance bgp 20 20 200

Network Protocols Command Reference, Part 1

P1R-388

BGP Commands ip as-path access-list

ip as-path access-list
To define a BGP-related access list, use the ip as-path access-list command in global configuration mode. To disable use of the access list, use the no form of this command. ip as-path access-list access-list-number {permit | deny} as-regular-expression no ip as-path access-list access-list-number {permit | deny} as-regular-expression

Syntax Description

access-list-number permit deny as-regular-expression

Integer from 1 to 199 that indicates the regular expression access list number. Permits access for matching conditions. Denies access to matching conditions. Autonomous system in the access list using a regular expression. See the Regular Expressions appendix in the Dial Solutions Command Reference for information about forming regular expressions.

Defaults

No access lists are defined.

Command Modes

Global configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

You can specify an access list filter on both inbound and outbound BGP routes. In addition, you can assign weights based on a set of filters. Each filter is an access list based on regular expressions. If the regular expression matches the representation of the autonomous system path of the route as an ASCII string, then the permit or deny condition applies. The autonomous system path does not contain the local autonomous system number. Use the ip as-path access-list global configuration command to define an BGP access list, and the neighbor router configuration command to apply a specific access list.

Examples

The following example specifies that the BGP neighbor with IP address 172.16.1.1 is not sent advertisements about any path through or from the adjacent autonomous system 123:
ip as-path access-list 1 deny _123_ ip as-path access-list 1 deny ^123$ router bgp 109 network 10.108.0.0 neighbor 192.168.6.6 remote-as 123 neighbor 172.16.1.1 remote-as 47 neighbor 172.16.1.1 filter-list 1 out

Network Protocols Command Reference, Part 1

P1R-389

BGP Commands ip as-path access-list

Related Commands

Command neighbor distribute-list neighbor filter-list

Description Distributes BGP neighbor information as specified in an access list. Sets up a BGP filter.

Network Protocols Command Reference, Part 1

P1R-390

BGP Commands ip bgp-community new-format

ip bgp-community new-format
To display BGP communities in the format AA:NN (AS-community number/2-byte number), use the ip bgp-community new-format command in global configuration mode.To re-enable the previous display format for BGP communities (NN:AA), use the no form of this command. ip bgp-community new-format no ip bgp-community new-format

Syntax Description

This command has no argument or keywords.

Command History

Release 12.0

Modification This command was introduced.

Usage Guidelines

RFC 1997, BGP Communities Attribute specifies that a BGP community is made up of two parts that are 2 bytes long. The first part is the autonomous system number and the second part is a 2-byte number. In the most recent version of the RFC, a community is of the form AA:NN. The Cisco default community format is one 32-bit number. The ip bgp-community new-format command changes the community format to AA:NN to conform to RFC 1997.

Examples

The following example upgrades a router that uses the 32-bit number community format to the AA:NN format:
Router(config)# ip bgp-community new-format

The following example shows how BGP community numbers are displayed when the ip bgp-community new-format command is enabled:
Router# show ip bgp 10.0.0.0 BGP routing table entry for 10.0.0.0/8, version 4 Paths: (2 available, best #2, table Default-IP-Routing-Table) Advertised to non peer-group peers: 10.0.33.35 35 10.0.33.35 from 10.0.33.35 (192.168.3.3) Origin incomplete, metric 10, localpref 100, valid, external Community: 1:1 Local 0.0.0.0 from 0.0.0.0 (10.0.33.34) Origin incomplete, metric 0, localpref 100, weight 32768, valid, sourced, best

Related Commands

Command show ip bgp

Description Display entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-391

BGP Commands ip bgp fast-external-fallover

ip bgp fast-external-fallover
To enable per-interface fast external fallover, enter the ip bgp fast-external-fallover command in interface configuration mode. To revert back to the current behavior, use the no format of this command. ip bgp fast-external-fallover [permit | deny] no ip bgp fast-external-fallover [permit | deny]

Syntax Description

permit deny

Allows per-interface fast external fallover. Prevents per-interface fast external fallover.

Defaults

Global fast external fallover.

Command Modes

Interface configuration

Command History

Release 12.0ST

Modification This command was introduced.

Usage Guidelines

When you specify the ip bgp fast-external-fallover command with the permit or deny keyword, it overrides the global setting. If you enter the no format of the command, the global setting is in effect for this interface.

Examples

The following example enables per-interface fast-external-fallover on interface Ethernet 0/0:

Router(config)# interface ethernet 0/0 Router(config-if)# ip bgp fast-external-fallover permit

Network Protocols Command Reference, Part 1

P1R-392

BGP Commands ip community-list

ip community-list
To create a community list for BGP and control access to it, use the ip community-list command in global configuration mode. To delete the community list, use the no form of this command. ip community-list community-list-number {permit | deny} community-number no ip community-list community-list-number

Syntax Description

community-list-number permit deny community-list-number

Integer from 1 to 99 that identifies one or more permit or deny groups of communities. Permits access for a matching condition. Denies access for a matching condition. Community number configured by a set community command. Valid value is one of the following: A number from 1 to 4294967200. You can specify a single number or multiple numbers separated by a space. internetThe Internet community. no-exportRoutes with this community are sent to peers in other sub-autonomous systems within a confederation. Do not advertise this route to an EBGP peer. External systems are those outside the confederation. If there is no confederation, an external system is any EBGP peer. local-as Do not advertise this route to peers outside the local autonomous system. This route will not be advertised to other autonomous systems or sub-autonomous systems when confederations are configured. no-advertiseDo not advertise this route to any peer (internal or external).

Defaults

Once you permit a value for the community number, the community list defaults to an implicit deny for everything else that has not been permitted.

Command Modes

Global configuration

Command History

Release 10.3 12.0

Modification This command was introduced. The local-as attribute was added.

Network Protocols Command Reference, Part 1

P1R-393

BGP Commands ip community-list

Examples

In the following example, Cisco IOS software permits all routes except the routes with the communities 5 and 10 or 10 and 15:
ip community-list 1 deny 5 10 ip community-list 1 deny 10 15 ip community-list 1 permit internet

The following example permits all routes within the local autonomous system:
ip community-list 1 permit local-as

Related Commands

Command set community show ip bgp community

Description Sets the BGP COMMUNITIES attribute. Displays routes that belong to specified BGP communities.

Network Protocols Command Reference, Part 1

P1R-394

BGP Commands match as-path

match as-path
To match a BGP autonomous system path access list, use the match as-path command in route-map configuration mode. To remove a path list entry, use the no form of this command. match as-path path-list-number no match as-path path-list-number

Syntax Description

path-list-number

Autonomous system path access list. An integer from 1 to 199.

Defaults

No path lists are defined.

Command Modes

Route-map configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

The values set by the match as-path and set weight commands override global values. For example, the weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands. A route map can have several parts. Any route that does not match at least one match clause relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route-map section with an explicit match specified. The implemented weight is based on the first matched autonomous system path.

Examples

The following example sets the autonomous system path to match BGP autonomous system path access list 20:
route-map igp2bgp match as-path 20

Network Protocols Command Reference, Part 1

P1R-395

BGP Commands match as-path

Related Commands

Command match interface match ip address

Description Distributes routes that have their next hop out one of the interfaces specified. Distributes any routes that have a destination network number address permitted by a standard or extended access list, or performs policy routing on packets. Redistributes any routes that have a next-hop router address passed by one of the access lists specified.

match community-list Matches a BGP community.

match ip next-hop

match ip route-source Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. match metric match route-type match tag route-map set as-path set automatic-tag set community set level set local-preference set metric set metric-type set next-hop set origin set tag set weight Redistributes routes with the metric specified. Redistributes routes of the specified type. Redistributes routes in the routing table that match the specified tags. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Modifies an autonomous system path for BGP routes. Automatically computes the tag value in a route map configuration. Sets the BGP COMMUNITIES attribute. Indicates where to import routes. Specifies a preference value for the autonomous system path. Sets the metric value for a routing protocol. Sets the metric type for the destination routing protocol. Specifies the address of the next hop. Sets the BGP origin code. Sets the value of the destination routing protocol. Specifies the BGP weight for the routing table.

Network Protocols Command Reference, Part 1

P1R-396

BGP Commands match community

match community
To match a Border Gateway Protocol (BGP) community, use the match community command in route-map configuration mode. To remove the match community command from the configuration file and restore the system to its default condition where the software removes the BGP community list entry, use the no form of this command. match community{standard-list-number | expanded-list-number | community-list-name [exact-match]} no match community {standard-list-number | expanded-list-number | community-list-name [exact-match]}

Syntax Description

standard-list-number expanded-list-number community-list-name exact-match

Specifies a standard community list number from 1 to 99 that identifies one or more permit or deny groups of communities. Specifies an expanded community list number from 100 to 199 that identifies one or more permit or deny groups of communities. The community list name. (Optional) Indicates that an exact match is required. All of the communities and only those communities specified must be present.

Defaults

No community list is matched by the route map.

Command Modes

Route-map configuration

Command History

Release 10.3

Modification This command was introduced.

Usage Guidelines

A route map can have several parts. Any route that does not match at least one match command relating to a route-map command will be ignored; that is, the route will not be advertised for outbound route maps and will not be accepted for inbound route maps. If you want to modify only some data, you must configure a second route-map section with an explicit match specified. Matching based on community list number or name is one of the types of match commands applicable to BGP.

Network Protocols Command Reference, Part 1

P1R-397

BGP Commands match community

Examples

The following example shows that the routes matching community list 1 will have the weight set to 100. Any route that has community 109 will have the weight set to 100.
Router(config)# ip community-list 1 permit 109 Router(config)# ! Router(config)# route-map set_weight Router(config-route-map)# match community 1 Router(config-route-map)# set weight 100

The following example shows that the routes matching community list 1 will have the weight set to 200. Any route that has community 109 alone will have the weight set to 200.
Router(config)# ip community-list 1 permit 109 Router(config)# ! Router(config)# route-map set_weight Router(config-route-map)# match community 1 exact Router(config-route-map)# set weight 200

In the following example, the routes that match community list LIST_NAME will have the weight set to 100. Any route that has community 101 alone will have the weight set to 100.
Router(config)# ip community-list 1 permit 101 Router(config)# ! Router(config)# route-map set_weight Router(config-route-map)# match community LIST_NAME Router(config-route-map)# set weight 100

Related Commands

Command ip community-list route-map (IP) set weight

Description Creates a community list for BGP and controls access to it. Defines the conditions for redistributing routes from one routing protocol into another. Specifies the BGP weight for the routing table.

Network Protocols Command Reference, Part 1

P1R-398

BGP Commands neighbor advertisement-interval

neighbor advertisement-interval
To set the minimum interval between the sending of BGP routing updates, use the neighbor advertisement-interval command in router configuration mode. To remove an entry, use the no form of this command. neighbor {ip-address | peer-group-name} advertisement-interval seconds no neighbor {ip-address | peer-group-name} advertisement-interval seconds

Syntax Description

ip-address peer-group-name seconds

Neighbors IP address. Name of a BGP peer group. Time in seconds. Integer from 0 to 600.

Defaults

30 seconds for external peers and 5 seconds for internal peers.

Command Modes

Router configuration

Command History

Release 10.3

Modification This command was introduced.

Usage Guidelines

If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

The following example sets the minimum time between sending BGP routing updates to 10 seconds:
router bgp 5 neighbor 4.4.4.4 advertisement-interval 10

Related Commands

Command neighbor peer-group (creating)

Description Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-399

BGP Commands neighbor advertise-map non-exist-map

neighbor advertise-map non-exist-map

To install a Border Gateway Protocol (BGP) route as a locally originated route into a BGP routing table for conditional advertisement, use the neighbor advertise-map non-exist-map command in router configuration mode. To disable conditional advertisement, use the no form of this command. neighbor{ip-address} advertise-map {map1-name} non-exist-map {map2-name} no neighbor{ip-address} advertise-map {map1-name} non-exist-map {map2-name}

Syntax Description

ip-address map-name

Specifies the IP address of the router that should receive conditional advertisements for a given set of routes. Specifies the name of the advertise-map and the non-exist-map.

Defaults

The BGP Conditional Advertisement feature is not enabled by default.

Command Modes

Router configuration

Command History

Release 11.1CC 11.2

Modification This command was introduced. This command was integrated into Cisco IOS Release 11.2.

Usage Guidelines

Use the neighbor advertise-map non-exist-map router configuration command to conditionally advertise selected routes. The route map associated with the non-exist-map specifies the prefix that the BGP speaker will track. The route map associated with the advertise-map specifies the prefix that will be advertised when the prefix in the non-exist-map no longer exists. Any BGP route that is matched by the advertise-map route map will be advertised to the neighbor if the non-exist-map route map does not match any route in the BGP routing table. If the non-exist-map route map matches any route in the BGP routing table, any BGP routes that are matched by the advertise-map route map will not be advertised to the neighbor. All routes that may be dynamically advertised or not advertised need to exist in the BGP routing table for conditional advertisement to take place. The prefix tracked by the BGP speaker must be present in the IP routing table for the conditional advertisement not to take place.

Examples

The following example configures a router to conditionally advertise routes to 10.1.1.1:

neighbor 10.1.1.1 advertise-map map1 non-exist-map map2

Network Protocols Command Reference, Part 1

P1R-400

BGP Commands neighbor default-originate

neighbor default-originate
To allow a BGP speaker (the local router) to send the default route 0.0.0.0 to a neighbor for use as a default route, use the neighbor default-originate command in router configuration mode. To send no route as a default, use the no form of this command. neighbor {ip-address | peer-group-name} default-originate [route-map map-name] no neighbor {ip-address | peer-group-name} default-originate [route-map map-name]

Syntax Description

ip-address peer-group-name route-map map-name

IP address of the neighbor. Name of a BGP peer group. (Optional) Name of the route map. The route map allows route 0.0.0.0 to be injected conditionally.

Defaults

No default route is sent to the neighbor.

Command Modes

Router configuration

Command History

Release 11.0 12.0

Modification This command was introduced. Modifications were added to permit extended access lists.

Usage Guidelines

This command does not require the presence of 0.0.0.0 in the local router. When used with a route map, the default route 0.0.0.0 is injected if the route map contains a match ip address clause and there is a route that matches the IP access list exactly. The route map can contain other match clauses also. You can use standard or extended access lists with the neighbor default-originate command.

Examples

In the following example, the local router injects route 0.0.0.0 to the neighbor 172.16.2.3 unconditionally:
router bgp 109 network 172.16.0.0 neighbor 172.16.2.3 remote-as 200 neighbor 172.16.2.3 default-originate

Network Protocols Command Reference, Part 1

P1R-401

BGP Commands neighbor default-originate

In the following example, the local router injects route 0.0.0.0 to the neighbor 172.16.2.3 only if there is a route to 172.16.68.0 (that is, if a route with any mask exists, such as 255.255.255.0 or 255.255.0.0):
router bgp 109 network 172.16.0.0 neighbor 172.16.2.3 remote-as 200 neighbor 172.16.2.3 default-originate route-map default-map ! route-map default-map 10 permit match ip address 1 ! access-list 1 permit 172.16.68.0

In the following example, the last line of the configuration has been changed to show the use of an extended access list. The local router injects route 0.0.0.0 to the neighbor 172.16.2.3 only if there is a route to 172.16.68.0 with a mask of 255.255.0.0:
router bgp 109 network 172.16.0.0 neighbor 172.16.2.3 remote-as 200 neighbor 172.16.2.3 default-originate route-map default-map ! route-map default-map 10 permit match ip address 1 ! access-list 100 permit ip host 172.16.68.0 host 255.255.255.0

Related Commands

Command neighbor ebgp-multihop

Description Accepts and attempt BGP connections to external peers residing on networks that are not directly connected.

Network Protocols Command Reference, Part 1

P1R-402

BGP Commands neighbor description

neighbor description
To associate a description with a neighbor, use the neighbor description command in router configuration mode. To remove the description, use the no form of this command. neighbor {ip-address | peer-group-name} description text no neighbor {ip-address | peer-group-name} description [text]

Syntax Description

ip-address peer-group-name text

Neighbors IP address. Name of a BGP peer group. Text (up to 80 characters) that describes the neighbor.

Defaults

There is no description of the neighbor.

Command Modes

Router configuration

Command History

Release 11.3

Modification This command was introduced.

Examples

In the following example, the description of the neighbor is peer with xyz.com:
router bgp 109 network 172.16.0.0 neighbor 172.16.2.3 description peer with xyz.com

Network Protocols Command Reference, Part 1

P1R-403

BGP Commands neighbor distribute-list

neighbor distribute-list
To distribute BGP neighbor information as specified in an access list, use the neighbor distribute-list command in router configuration mode. To remove an entry, use the no form of this command. neighbor {ip-address | peer-group-name} distribute-list {access-list-number | expanded-list-number | access-list-name| prefix-list-name} {in | out} no neighbor {ip-address | peer-group-name} distribute-list {access-list-number | expanded-list-number | access-list-name| prefix-list-name} {in | out}

Syntax Description

ip-address peer-group-name access-list-number

IP address of the neighbor. Name of a BGP peer group. Number of a standard or extended access list. The range of a standard access list number is from 1 to 99. The range of an extended access list number is from 100 to 199.

expanded-list-number Number of an expanded access list number. The range of an expanded access list is from 1300 to 2699. access-list-name prefix-list-name in out Name of a standard or extended access list. Name of a BGP prefix list. Access list is applied to incoming advertisements to that neighbor. Access list is applied to outgoing advertisements to that neighbor.

Defaults

No BGP neighbor is specified.

Command Modes

Router configuration

Command History

Release 10.0 11.0 11.2

Modification This command was introduced. The peer-group-name argument was added. The access-list-name argument was added.

Usage Guidelines

If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. Specifying the command for a neighbor overrides the inbound policy that is inherited from the peer group. Using a distribute list is one of several ways to filter advertisements. Advertisements can also be filtered by using the following methods:

Autonomous system path filters can be configured with the ip as-path access-list and neighbor filter-list commands. The access-list (IP standard) and access-list (IP extended) commands can be used to configure standard and extended access lists for the filtering of advertisement.

Network Protocols Command Reference, Part 1

P1R-404

BGP Commands neighbor distribute-list

The route map command can be used to filter advertisements. Route maps may be configured with autonomous system filters, prefix filters, access lists and distribute lists.

Standard access lists may be used to filter routing updates. However, in the case of route filtering when using classless interdomain routing (CIDR), standard access lists do not provide the level of granularity that is necessary to configure advanced filtering of network addresses and masks. Extended access lists, configured with the access-list (IP extended) command, should be used to configure route filtering when using CIDR because extended access lists allow the network operator to use wild card bits to filter the relevant prefixes and masks. Wild card bits are similar to the bit masks that are used with normal access lists; prefix and mask bits that correspond to wild card bits that are set to 0 are used in the comparison of addresses or prefixes and wild card bits that are set to 1 are ignored during any comparisons. This function of extended access list configuration can also be used to filter addresses or prefixes based on the prefix length.

Examples

The following router configuration mode example applies list 39 to incoming advertisements from neighbor 192.168.4.1. List 39 permits the advertisement of network 10.109.0.0.
router bgp 109 network 10.108.0.0 neighbor 192.168.4.1 distribute-list 39 in

The following three examples show different scenarios for using an extended access list with a distribute list. The three examples are labeled Example A, Example B, and Example C. Each of the example extended access list configurations are used with the neighbor distribute-list command configuration example below.
router bgp 109 network 10.108.0.0 neighbor 192.168.4.1 distribute-list 101 in

Example A

The following extended access list example will permit route 192.108.0.0 255.255.0.0 but deny any more specific routes of 192.108.0.0 (including 192.108.0.0 255.255.255.0):
access-list 101 permit ip 192.108.0.0 0.0.0.0 255.255.0.0 0.0.0.0 access-list 101 deny ip 192.108.0.0 0.0.255.255 255.255.0.0 0.0.255.255

Example B

The following extended access list example will permit route 10.108.0/24 but deny 131.108/16 and all other subnets of 10.108.0.0:
access-list 101 permit ip 10.108.0.0 0.0.0.0 255.255.255.0 0.0.0.0 access-list 101 deny ip 10.108.0.0 0.0.255.255 255.255.0.0 0.0.255.255

Example C

The following extended access list example will deny all prefixes that are longer than 24 bits and permit all of the shorter prefixes:
access-list 101 deny ip 0.0.0.0 255.255.255.255 255.255.255.0 0.0.0.255 access-list 101 permit ip 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255

Network Protocols Command Reference, Part 1

P1R-405

BGP Commands neighbor distribute-list

Related Commands

Command access-list (IP extended) access-list (IP standard) ip as-path access-list neighbor filter-list neighbor peer-group (creating)

Description Defines an extended IP access list. Defines a standard IP access list. Defines a BGP-related access list. Sets up a BGP filter. Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-406

BGP Commands neighbor ebgp-multihop

neighbor ebgp-multihop
To accept and attempt BGP connections to external peers residing on networks that are not directly connected, use the neighbor ebgp-multihop command in router configuration mode. To return to the default, use the no form of this command. neighbor {ip-address | peer-group-name} ebgp-multihop [ttl] no neighbor {ip-address | peer-group-name} ebgp-multihop

Syntax Description

ip-address peer-group-name ttl

IP address of the BGP-speaking neighbor. Name of a BGP peer group. (Optional) Time-to-live in the range 1 to 255 hops.

Defaults

Only directly connected neighbors are allowed.

Command Modes

Router configuration

Command History

Release 10.0 11.0

Modification This command was introduced. The peer-group-name argument was added.

Usage Guidelines

This feature should be used only under the guidance of technical support staff. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. To prevent the creation of loops through oscillating routes,, the multihop will not be established if the only route to the multihop peer is the default route (0.0.0.0).

Examples

The following example allows connections to or from neighbor 10.108.1.1, which resides on a network that is not directly connected:
router bgp 109 neighbor 10.108.1.1 ebgp-multihop

Related Commands

Command neighbor default-originate neighbor peer-group (creating) network (BGP)

Description Allows a BGP speaker (the local router) to send the default route 0.0.0.0 to a neighbor for use as a default route. Creates a BGP peer group. Specifies the list of networks for the BGP routing process.

Network Protocols Command Reference, Part 1

P1R-407

BGP Commands neighbor filter-list

neighbor filter-list
To set up a BGP filter, use the neighbor filter-list command in router configuration mode. To disable this function, use the no form of this command. neighbor {ip-address | peer-group-name} filter-list access-list-number {in | out | weight weight} no neighbor {ip-address | peer-group-name} filter-list access-list-number {in | out | weight weight}

Syntax Description

ip-address peer-group-name access-list-number in out weight weight

IP address of the neighbor. Name of a BGP peer group. Number of an autonomous system path access list. You define this access list with the ip as-path access-list command. Access list to incoming routes. Access list to outgoing routes. Assigns a relative importance to incoming routes matching autonomous system paths. Acceptable values are 0 to 65535.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

This command establishes filters on both inbound and outbound BGP routes. Any number of weight filters are allowed on a per-neighbor basis, but only one in or out filter is allowed. The weight of a route affects BGPs route-selection rules. The implemented weight is based on the first matched autonomous system path. Weights indicated when an autonomous system path is matched override the weights assigned by global neighbor commands. In other words, the weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands. See the Regular Expressions appendix in the Dial Solutions Command Reference for information on forming regular expressions. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.

Network Protocols Command Reference, Part 1

P1R-408

BGP Commands neighbor filter-list

Examples

In the following example, the BGP neighbor with IP address 172.16.1.1 is not sent advertisements about any path through or from the adjacent autonomous system 123:
ip as-path access-list 1 deny _123_ ip as-path access-list 1 deny ^123$ router bgp 109 network 10.108.0.0 neighbor 192.168.6.6 remote-as 123 neighbor 172.16.1.1 remote-as 47 neighbor 172.16.1.1 filter-list 1 out

Related Commands

Command ip as-path access-list neighbor distribute-list neighbor peer-group (creating) neighbor weight

Description Defines a BGP-related access list. Distributes BGP neighbor information as specified in an access list. Creates a BGP peer group. Assigns a weight to a neighbor connection.

Network Protocols Command Reference, Part 1

P1R-409

BGP Commands neighbor maximum-prefix

neighbor maximum-prefix
To control how many prefixes can be received from a neighbor, use the neighbor maximum-prefix command in router configuration mode. To disable this function, use the no form of this command. neighbor {ip-address | peer-group-name} maximum-prefix maximum [threshold][warning-only] no neighbor {ip-address | peer-group-name} maximum-prefix maximum

Syntax Description

ip-address peer-group-name maximum threshold

IP address of the neighbor. Name of a BGP peer group. Maximum number of prefixes allowed from this neighbor. (Optional) Integer specifying at what percentage of maximum the router starts to generate a warning message. The range 1 to 100; the default is 75 (percent). (Optional) Allows the router to generate log message when the maximum is exceeded, instead of terminating the peering.

warning-only

Defaults

This command is disabled by default. There is no limit on the number of prefixes.

Command Modes

Router configuration

Command History

Release 11.3

Modification This command was introduced.

Usage Guidelines

This command allows you to configure a maximum number of prefixes a BGP router is allowed to receive from a peer. It adds another mechanism (in addition to distribute lists, filter lists, and route maps) to control prefixes received from a peer. When the number of received prefixes exceeds the maximum number configured, the router terminates the peering (by default). However, if the keyword warning-only is configured, the router instead only sends a log message, but continues peering with the sender. If the peer is terminated, the peer stays down until the clear ip bgp command is issued.

Examples

The following example sets the maximum number of prefixes allowed from the neighbor at 192.168.6.6 to 1000:
router bgp 109 network 10.108.0.0 neighbor 192.168.6.6 maximum-prefix 1000

Network Protocols Command Reference, Part 1

P1R-410

BGP Commands neighbor maximum-prefix

Related Commands

Command clear ip bgp

Description Resets a BGP connection using BGP soft reconfiguration.

Network Protocols Command Reference, Part 1

P1R-411

BGP Commands neighbor next-hop-self

neighbor next-hop-self
To disable next-hop processing of BGP updates on the router, use the neighbor next-hop-self command in router configuration mode. To disable this feature, use the no form of this command. neighbor {ip-address | peer-group-name} next-hop-self no neighbor {ip-address | peer-group-name} next-hop-self

Syntax Description

ip-address peer-group-name

IP address of the BGP-speaking neighbor. Name of a BGP peer group.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 10.0 11.0

Modification This command was introduced. The peer-group-name argument was added.

Usage Guidelines

This command is useful in nonmeshed networks (such as Frame Relay or X.25) where BGP neighbors may not have direct access to all other neighbors on the same IP subnet. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group. For a finer granularity of control, see the set ip next-hop command.

Examples

The following example forces all updates destined for 10.108.1.1 to advertise this router as the next hop:
router bgp 109 neighbor 10.108.1.1 next-hop-self

Related Commands

Command neighbor peer-group (creating) set ip next-hop (BGP)

Description Creates a BGP peer group. Indicates where to output packets that pass a match clause of a route map for policy routing.

Network Protocols Command Reference, Part 1

P1R-412

BGP Commands neighbor password

neighbor password
To enable MD5 authentication on a TCP connection between two BGP peers, use the neighbor password command in router configuration mode. To disable this function, use the no form of this command. neighbor {ip-address | peer-group-name} password string no neighbor {ip-address | peer-group-name} password

Syntax Description

ip-address peer-group-name string

IP address of the BGP-speaking neighbor. Name of a BGP peer group. Case-sensitive password of up to 25 characters. The string can contain any alphanumeric characters, including spaces. You cannot specify a password in the format number-space-anything. The space after the number causes problems.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

You can invoke authentication between two BGP peers, causing each segment sent on the TCP connection between them to be verified. This feature must be configured with the same password on both BGP peers; otherwise, the connection between them will not be made. The authentication feature uses the MD5 algorithm. Specifying this command causes the generation and checking of the MD5 digest on every segment sent on the TCP connection. Configuring a password for a neighbor will cause an existing session to be torn down and a new one established. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. If a router has a password configured for a neighbor, but the neighbor router does not, a message such as the following will appear on the console while the routers attempt to establish a BGP session between them:
%TCP-6-BADAUTH: No MD5 digest from [peers IP address]:11003 to [local routers IP address]:179

Similarly, if the two routers have different passwords configured, a message such as the following will appear on the screen:
%TCP-6-BADAUTH: Invalid MD5 digest from [peers IP address]:11004 to [local routers IP address]:179

Network Protocols Command Reference, Part 1

P1R-413

BGP Commands neighbor password

Examples

The following example enables the authentication feature between this router and the BGP neighbor at 10.108.1.1. The password that must also be configured for the neighbor is bla4u00=2nkq.
router bgp 109 neighbor 10.108.1.1 password bla4u00=2nkq

Related Commands

Command neighbor peer-group (creating)

Description Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-414

BGP Commands neighbor peer-group (assigning members)

neighbor peer-group (assigning members)

To configure a BGP neighbor to be a member of a peer group, use the neighbor peer-group command in router configuration mode. To remove the neighbor from the peer group, use the no form of this command. neighbor ip-address peer-group peer-group-name no neighbor ip-address peer-group peer-group-name

Syntax Description

ip-address peer-group-name

IP address of the BGP neighbor who belongs to the peer group specified by the tag. Name of the BGP peer group to which this neighbor belongs.

Defaults

There are no BGP neighbors in a peer group.

Command Modes

Router configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

The neighbor at the IP address indicated inherits all the configured options of the peer group.

Examples

The following example assigns three neighbors to the peer group named internal:
router bgp 100 neighbor internal peer-group neighbor internal remote-as 100 neighbor internal update-source loopback 0 neighbor internal route-map set-med out neighbor internal filter-list 1 out neighbor internal filter-list 2 in neighbor 172.16.232.53 peer-group internal neighbor 172.16.232.54 peer-group internal neighbor 172.16.232.55 peer-group internal neighbor 172.16.232.55 filter-list 3 in

Related Commands

Command neighbor peer-group (creating) neighbor shutdown

Description Creates a BGP peer group. Disables a neighbor or peer group.

Network Protocols Command Reference, Part 1

P1R-415

BGP Commands neighbor peer-group (creating)

neighbor peer-group (creating)

To create a BGP peer group, use the neighbor peer-group command in router configuration mode. To remove the peer group and all of its members, use the no form of this command. neighbor peer-group-name peer-group no neighbor peer-group-name peer-group

Syntax Description

peer-group-name

Name of the BGP peer group.

Defaults

There is no BGP peer group.

Command Modes

Router configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

Often in a BGP speaker, there are many neighbors configured with the same update policies (that is, same outbound route maps, distribute lists, filter lists, update source, and so on). Neighbors with the same update policies can be grouped into peer groups to simplify configuration and make update calculation more efficient. Peer group members can spanned multiple logical IP subnets, and can transit, or pass along, routes from one peer group member to another. Once a peer group is created with the neighbor peer-group command, it can be configured with the neighbor commands. By default, members of the peer group inherit all the configuration options of the peer group. Members can also be configured to override the options that do not affect outbound updates. Peer group members will always inherit the following configuration options: remote-as (if configured), version, update-source, out-route-map, out-filter-list, out-dist-list, minimum-advertisement-interval, and next-hop-self. All the peer group members will inherit changes made to the peer group. If a peer group is not configured with a remote-as, the members can be configured with the neighbor {ip-address | peer-group-name} remote-as command. This command allows you to create peer groups containing EBGP neighbors.
Example for an IBGP Peer Group

In the following example, the peer group named internal configures the members of the peer group to be IBGP neighbors. By definition, this is an IBGP peer group because the router bgp command and the neighbor remote-as command indicate the same autonomous system (in this case, AS 100). All the

Network Protocols Command Reference, Part 1

P1R-416

BGP Commands neighbor peer-group (creating)

peer group members use loopback 0 as the update source and use set-med as the outbound route-map. The neighbor internal filter-list 2 in command shows that, except for 172.16.232.55, all the neighbors have filter-list 2 as the inbound filter list.
router bgp 100 neighbor internal peer-group neighbor internal remote-as 100 neighbor internal update-source loopback 0 neighbor internal route-map set-med out neighbor internal filter-list 1 out neighbor internal filter-list 2 in neighbor 172.16.232.53 peer-group internal neighbor 172.16.232.54 peer-group internal neighbor 172.16.232.55 peer-group internal neighbor 172.16.232.55 filter-list 3 in

Example for an EBGP Peer Group

The following example defines the peer group named external-peers without the neighbor remote-as command. This is what makes it an EBGP peer group. Each individual member of the peer group is configured with its respective AS-number separately. Thus the peer group consists of members from autonomous systems 200, 300, and 400. All the peer group members have set-metric route map as an outbound route map and filter-list 99 as an outbound filter list. Except for neighbor 172.16.232.110, all of them have 101 as the inbound filter list.
router bgp 100 neighbor external-peers peer-group neighbor external-peers route-map set-metric out neighbor external-peers filter-list 99 out neighbor external-peers filter-list 101 in neighbor 172.16.232.90 remote-as 200 neighbor 172.16.232.90 peer-group external-peers neighbor 172.16.232.100 remote-as 300 neighbor 172.16.232.100 peer-group external-peers neighbor 172.16.232.110 remote-as 400 neighbor 172.16.232.110 peer-group external-peers neighbor 172.16.232.110 filter-list 400 in

Related Commands

Command clear ip bgp peer-group neighbor peer-group (creating) show ip bgp peer-group

Description Removes all the members of a BGP peer group. Creates a BGP peer group. Display information about BGP peer groups.

Network Protocols Command Reference, Part 1

P1R-417

BGP Commands neighbor prefix-list

neighbor prefix-list
To distribute BGP neighbor information as specified in a prefix list, use the neighbor access-list command in router configuration mode. To remove an entry, use the no form of this command. neighbor {ip-address | peer-group-name} prefix-list prefix-listname {in | out} no neighbor {ip-address | peer-group-name} prefix-list prefix-listname {in |out}

Syntax Description

ip-address peer-group-name prefix-list prefix-listname in out

Neighbors IP address. Name of a BGP peer group. Applies a prefix list to the route to be matched. Name of a prefix list. Access list is applied to incoming advertisements to that neighbor. Access list is applied to outgoing advertisements to that neighbor.

Defaults

No BGP neighbor is specified.

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Usage Guidelines

Using prefix lists is one of two ways to filter BGP advertisements. The other way is to use AS-path filters, as with the ip as-path access-list global configuration command and the neighbor filter-list command, and access or prefix lists, as with the neighbor distribute-list command. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.

Note

Do not use both neighbor access-list and neighbor prefix-list commands for a single BGP peer. Do not apply both a neighbor distribute-list and a neighbor prefix-list command to the same neighbor.

Examples

The following example applies prefix list abc to incoming advertisements to neighbor 192.168.4.1:
router bgp 109 network 10.108.0.0 neighbor 192.168.4.1 prefix-list abc in

Network Protocols Command Reference, Part 1

P1R-418

BGP Commands neighbor prefix-list

The following example applies prefix list CustomerA to incoming advertisements to neighbor 192.168.4.1:
router bgp 109 network 10.108.0.0 neighbor 192.168.4.1 prefix-list CustomerA in

Related Commands

Command clear ip prefix-list ip as-path access-list ip prefix-list ip prefix-list description ip prefix-list sequence-number neighbor filter-list neighbor peer-group (creating) show ip bgp peer-group show ip prefix-list

Description Resets the hit count of the prefix list entries. Defines a BGP-related access list. Creates an entry in a prefix list and assigns a sequence number to the entry. Adds a text description of a prefix list. Enables the generation of sequence numbers for entries in a prefix list. Sets up a BGP filter. Creates a BGP peer group. Display information about BGP peer groups. Displays information about a prefix list or prefix list entries.

Network Protocols Command Reference, Part 1

P1R-419

BGP Commands neighbor remote-as

neighbor remote-as
To add an entry to the BGP neighbor table, use the neighbor remote-as command in router configuration mode. To remove an entry from the table, use the no form of this command. neighbor {ip-address | peer-group-name} remote-as number no neighbor {ip-address | peer-group-name} remote-as number

Syntax Description

ip-address peer-group-name number

Neighbors IP address. Name of a BGP peer group. Autonomous system to which the neighbor belongs.

Defaults

There are no BGP neighbor peers.

Command Modes

Router configuration

Command History

Release 10.0 11.0

Modification This command was introduced. The peer-group-name argument was added.

Usage Guidelines

Specifying a neighbor with an autonomous system number that matches the autonomous system number specified in the router bgp global configuration command identifies the neighbor as internal to the local autonomous system. Otherwise, the neighbor is considered external. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

The following example specifies that a router at the address 10.108.1.2 is a neighbor in autonomous system number 109:
router bgp 110 network 10.108.0.0 neighbor 10.108.1.2 remote-as 109

The following example assigns a BGP router to autonomous system 109, and two networks are listed as originating in the autonomous system. Then the addresses of three remote routers (and their autonomous systems) are listed. The router being configured will share information about networks 10.108.0.0 and 192.31.7.0 with the neighbor routers. The first router listed is in the same Class B

Network Protocols Command Reference, Part 1

P1R-420

BGP Commands neighbor remote-as

network address space, but in a different autonomous system; the second neighborremote-as command illustrates specification of an internal neighbor (with the same autonomous system number) at address 10.108.234.2; and the last neighborremote-as command specifies a neighbor on a different network.
router bgp 109 network 10.108.0.0 network 192.31.7.0 neighbor 10.108.200.1 remote-as 167 neighbor 10.108.234.2 remote-as 109 neighbor 150.136.64.19 remote-as 99

Related Commands

Command neighbor peer-group (creating)

Description Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-421

BGP Commands neighbor remove-private-as

neighbor remove-private-as
To remove private autonomous system numbers from the AS-path, a list of autonomous system numbers that a route passes through to reach a BGP peer, in outbound routing updates, use the neighbor remove-private-as command in router configuration mode. To disable this function, use the no form of this command. neighbor {ip-address | peer-group-name} remove-private-as no neighbor {ip-address | peer-group-name} remove-private-as

Syntax Description

ip-address peer-group-name

IP address of the BGP-speaking neighbor. Name of a BGP peer group.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 10.3 11.0

Modification This command was introduced. The peer-group-name argument was added.

Usage Guidelines

This feature is available for external BGP (EBGP) neighbors only. When an update is passed to the external neighbor, if the AS-path includes private autonomous system numbers, the software will drop the private autonomous system numbers. If the AS-path includes both private and public autonomous system numbers, the software considers this to be a configuration error and does not remove the private autonomous system numbers. If the AS-path contains the autonomous system number of the EBGP neighbor, the private autonomous system numbers will not be removed. If this feature is used with confederation, it will work as long as the private autonomous system numbers follow the confederation portion of the AS-path. The private autonomous system values are from 64512 to 65535.

Network Protocols Command Reference, Part 1

P1R-422

BGP Commands neighbor remove-private-as

Examples

The following example shows a configuration that will remove the private autonomous system number from the updates sent to 172.16.2.33. The result is that the AS_path for the paths advertised by 10.108.1.1 through autonomous system 100 will just contain 100 (as seen by autonomous system 2051).
router bgp 100 neighbor 10.108.1.1 description peer with private-as neighbor 10.108.1.1 remote-as 65001 neighbor 172.16.2.33 description eBGP peer neighbor 172.16.2.33 remote-as 2051 neighbor 172.16.2.33 remove-private-as router-in-AS100# show ip bgp 10.0.0.0 BGP routing table entry for 10.0.0.0/8, version 15 Paths: (1 available, best #1) Advertised to non peer-group peers: 172.16.2.33 65001 10.108.1.1 from 10.108.1.1 Origin IGP, metric 0, localpref 100, valid, external, best router-in-AS2501# show ip bgp 10.0.0.0 BGP routing table entry for 10.0.0.0/8, version 3 Paths: (1 available, best #1) Not advertised to any peer 2 172.16.2.32 from 172.16.2.32 Origin IGP, metric 0, localpref 100, valid, external, best

Related Commands

Command neighbor remote-as show ip bgp

Description Allows entries to the BGP neighbor table. Displays entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-423

BGP Commands neighbor route-map

neighbor route-map
To apply a route map to incoming or outgoing routes, use the neighbor route-map command in router configuration mode. To remove a route map, use the no form of this command. neighbor {ip-address | peer-group-name} route-map map-name {in | out} no neighbor {ip-address | peer-group-name} route-map map-name {in | out}

Syntax Description

ip-address peer-group-name map-name in out

Neighbors IP address. Name of a BGP peer group. Name of route map. Apply to incoming routes. Apply to outgoing routes.

Defaults

No route maps are applied to a peer.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

If an outbound route map is specified, it is proper behavior to only advertise routes that match at least one section of the route map. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command. Specifying the command with an IP address will override the value inherited from the peer group.

Examples

The following example applies a route map named internal-map to incoming route from 172.16.70.24:
router bgp 5 neighbor 172.16.70.24 route-map internal-map in ! route-map internal-map match as-path 1 set local-preference 100

Related Commands

Command neighbor peer-group (creating)

Description Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-424

BGP Commands neighbor route-reflector-client

neighbor route-reflector-client
To configure the router as a BGP route reflector and configure the specified neighbor as its client, use the neighbor route-reflector-client command in router configuration mode. To indicate that the neighbor is not a client, use the no form of this command. When all the clients are disabled, the local router is no longer a route reflector. neighbor ip-address route-reflector-client no neighbor ip-address route-reflector-client

Syntax Description

ip-address

IP address of the BGP neighbor being identified as a client.

Defaults

There is no route reflector in the autonomous system.

Command Modes

Router configuration

Command History

Release 11.1

Modification This command was introduced.

Usage Guidelines

By default, all IBGP speakers in an autonomous system must be fully meshed, and neighbors do not readvertise IBGP learned routes to neighbors, thus preventing a routing information loop. If you use route reflectors, all IBGP speakers need not be fully meshed. In the route reflector model, an internal BGP peer is configured to be a route reflector responsible for passing IBGP learned routes to IBGP neighbors. This scheme eliminates the need for each router to talk to every other router. Use the neighbor route-reflector-client command to configure the local router as the route reflector and the specified neighbor as one of its clients. All the neighbors configured with this command will be members of the client group and the remaining IBGP peers will be members of the nonclient group for the local route reflector. The bgp client-to-client reflection command controls client-to-client reflection.

Examples

In the following example, the local router is a route reflector. It passes learned IBGP routes to the neighbor at 172.16.70.24.
router bgp 5 neighbor 172.16.70.24 route-reflector-client

Network Protocols Command Reference, Part 1

P1R-425

BGP Commands neighbor route-reflector-client

Related Commands

Command bgp client-to-client reflection bgp cluster-id show ip bgp

Description Restores route reflection from a BGP route reflector to clients. Configures the cluster ID if the BGP cluster has more than one route reflector. Display entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-426

BGP Commands neighbor send-community

neighbor send-community
To specify that a COMMUNITIES attribute should be sent to a BGP neighbor, use the neighbor send-community command in router configuration mode. To remove the entry, use the no form of this command. neighbor {ip-address | peer-group-name} send-community [both | standard | extended] no neighbor {ip-address | peer-group-name} send-community

Syntax Description

ip-address peer-group-name both standard extended

IP address of the neighbor. Name of a BGP peer group. (Optional) Specifies that both standard and extended communities will be sent. (Optional) Specifies that only standard communities will be sent. (Optional) Specifies that only extended communities will be sent.

No COMMUNITIES attribute is sent to any neighbor.

Command Modes

Router configuration

Command History

Release 10.3 11.0

Modification This command was introduced. The peer-group-name argument was added.

Usage Guidelines

If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

In the following example, the router belongs to autonomous system 109 and is configured to send the COMMUNITIES attribute to its neighbor at IP address 172.16.70.23:
router bgp 109 neighbor 172.16.70.23 send-community

Related Commands

Command match community-list neighbor peer-group (creating) set community

Description Matches a BGP community. Creates a BGP peer group. Sets the BGP COMMUNITIES attribute.

Network Protocols Command Reference, Part 1

P1R-427

BGP Commands neighbor shutdown

neighbor shutdown
To disable a neighbor or peer group, use the neighbor shutdown command in router configuration mode.To re-enable the neighbor or peer group, use the no form of this command. neighbor {ip-address | peer-group-name} shutdown no neighbor {ip-address | peer-group-name} shutdown

Syntax Description

ip-address peer-group-name

Neighbors IP address. Name of a BGP peer group.

Defaults

No change is made to the status of any BGP neighbor or peer group.

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Usage Guidelines

The neighbor shutdown command terminates any active session for the specified neighbor or peer group, and removes all associated routing information. In the case of a peer group, this could mean a large number of peering sessions are suddenly terminated. To display a summary of BGP neighbors and peer-group connections, use the show ip bgp summary command. Those neighbors with an Idle status and the Admin entry have been disabled by the neighbor shutdown command. State/PfxRcd shows the current state of the BGP session/the number of prefixes the router has 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 Idle.

Related Commands

Command neighbor maximum-prefix show ip bgp summary

Description Controls how many prefixes can be received from a neighbor. Display the status of all BGP connections.

Network Protocols Command Reference, Part 1

P1R-428

BGP Commands neighbor soft-reconfiguration

neighbor soft-reconfiguration
To configure the Cisco IOS software to start storing updates, use the neighbor soft-reconfiguration command in router configuration mode. To not store received updates, use the no form of this command. neighbor {ip-address | peer-group-name} soft-reconfiguration [inbound] no neighbor {ip-address | peer-group-name} soft-reconfiguration [inbound]

Syntax Description

ip-address peer-group-name inbound

IP address of the BGP-speaking neighbor. Name of a BGP peer group. Keyword indicating that the update to be stored is an incoming update. Inbound is currently required with this command, since a keyword is required and no other keywords are available.

Defaults

Soft reconfiguration is not enabled

Command Modes

Router configuration

Command History

Release 11.2

Modification This command was introduced.

Usage Guidelines

This command requires at least one keyword. Currently the only keyword available is inbound, so the use of inbound is not optional. Entering this command starts the storage of updates, required to do inbound soft reconfiguration. Outbound BGP soft reconfiguration does not require inbound soft reconfiguration to be enabled. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

The following example enables inbound soft-reconfiguration for the neighbor 10.108.1.1. All the updates received from this neighbor will be stored unmodified, regardless of the inbound policy. When inbound soft reconfiguration is done later, the stored information will be used to generate a new set of inbound updates.
router bgp 100 neighbor 10.108.1.1 remote-as 200 neighbor 10.108.1.1 soft-reconfiguration inbound

Network Protocols Command Reference, Part 1

P1R-429

BGP Commands neighbor soft-reconfiguration

Related Commands

Command clear ip bgp neighbor peer-group (creating)

Description Resets a BGP connection using BGP soft reconfiguration. Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-430

BGP Commands neighbor timers

neighbor timers
To set the timers for a specific BGP peer or peer group, use the neighbor timers command in router configuration mode. To clear the timers for a specific BGP peer or peer group, use the no form of this command. neighbor [ip-address | peer-group-name] timers keepalive holdtime no neighbor [ip-address | peer-group-name] timers keepalive holdtime

Syntax Description

ip-address peer-group-name keepalive

(Optional) A BGP peer or peer group IP address. (Optional) Name of the BGP peer group. Frequency, in seconds, with which the Cisco IOS software sends keepalive messages to its peer. The default is 60 seconds. Interval, in seconds, after not receiving a keepalive message that the software declares a peer dead. The default is 180 seconds.

holdtime

Defaults

keepalive: 60 seconds holdtime: 180 seconds

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Usage Guidelines

The timers configured for a specific neighbor or peer group override the timers configured for all BGP neighbors using the command timers bgp.

Examples

The following example changes the keepalive timer to 70 seconds and the holdtime timer to 210 seconds for the BGP peer 192.98.47.0:
router bgp 109 neighbor 192.98.47.0 timers 70 210

Network Protocols Command Reference, Part 1

P1R-431

BGP Commands neighbor update-source

neighbor update-source
To have the Cisco IOS software allow Border Gateway Protocol (BGP) sessions to use a specific operational interface for TCP connections, use the neighbor update-source command in router configuration mode. To restore the interface assignment to the closest interface, which is called the best local address, use the no form of this command. neighbor {ip-address | peer-group-name} update-source interface no neighbor {ip-address | peer-group-name} update-source interface

Syntax Description

ip-address peer-group-name interface-type

IP address of the BGP-speaking neighbor. Name of a BGP peer group. Interface to be used as the source.

Defaults

Best local address

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

This command works in conjunction with any specified interface on the router. The loopback interface is the interface that is most commonly used with this feature. For more information, refer to the loopback interface feature described in the Interface Configuration Overview chapter of the Cisco IOS Interface Configuration Guide. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

The following example sources BGP TCP connections for the specified neighbor with loopback interfaces IP address rather than the best local address:
router bgp 110 network 172.16.0.0 neighbor 172.16.2.3 remote-as 110 neighbor 172.16.2.3 update-source Loopback0

Related Commands

Command neighbor peer-group (creating)

Description Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-432

BGP Commands neighbor version

neighbor version
To configure the Cisco IOS software to accept only a particular BGP version, use the neighbor version command in router configuration mode. To use the default version level of a neighbor, use the no form of this command. neighbor {ip-address | peer-group-name} version value no neighbor {ip-address | peer-group-name} version value

Syntax Description

ip-address peer-group-name value

IP address of the BGP-speaking neighbor. Name of a BGP peer group. BGP version number. The version can be set to 2 to force the software to use only Version 2 with the specified neighbor. The default is to use Version 4 and dynamically negotiate down to Version 2 if requested.

Defaults

BGP Version 4

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

Entering this command disables dynamic version negotiation. Our implementation of BGP supports BGP Versions 2, 3, and 4. If the neighbor does not accept default Version 4, dynamic version negotiation is implemented to negotiate down to Version 2. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

The following example locks down to Version 4 of the BGP protocol:

router bgp 109 neighbor 131.104.27.2 version 4

Related Commands

Command neighbor peer-group (creating)

Description Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-433

BGP Commands neighbor weight

neighbor weight
To assign a weight to a neighbor connection, use the neighbor weight command in router configuration mode. To remove a weight assignment, use the no form of this command. neighbor {ip-address | peer-group-name} weight weight no neighbor {ip-address | peer-group-name} weight weight

Syntax Description

ip-address peer-group-name weight

Neighbors IP address. Name of a BGP peer group. Weight to assign. Acceptable values are 0 to 65535.

Defaults

Routes learned through another BGP peer have a default weight of 0 and routes sourced by the local router have a default weight of 32768.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

All routes learned from this neighbor will have the assigned weight initially. The route with the highest weight will be chosen as the preferred route when multiple routes are available to a particular network. The weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands.

Note

For weight changes to take effect, it may be necessary to use clear ip bgp peer-group *. If you specify a BGP peer group by using the peer-group-name argument, all the members of the peer group will inherit the characteristic configured with this command.

Examples

The following example sets the weight of all routes learned via 172.16.12.1 to 50:
router bgp 109 neighbor 172.16.12.1 weight 50

Network Protocols Command Reference, Part 1

P1R-434

BGP Commands neighbor weight

Related Commands

Command neighbor distribute-list neighbor filter-list neighbor peer-group (creating)

Description Distributes BGP neighbor information as specified in an access list. Sets up a BGP filter. Creates a BGP peer group.

Network Protocols Command Reference, Part 1

P1R-435

BGP Commands network (BGP)

network (BGP)
To specify the list of networks for the Border Gateway Protocol (BGP) routing process, use this form of the network command in router configuration mode. To remove an entry, use the no form of this command. network network-number [mask network-mask] [route-map map-name] no network network-number [mask network-mask] [route-map map-name]

Syntax Description

network-number mask

Network that BGP will advertise. Network or subnetwork mask. If the mask keyword is configured, then an exact match must exist in the routing table. (Optional) Network mask address. (Optional) Name of a route map.

network-mask route-map map-name

Defaults

No networks are specified.

Command Modes

Router configuration

Command History

Release 10.0 12.0

Modification This command was introduced. The limit of 200 network commands per BGP router was removed.

Usage Guidelines

This command first appeared in Cisco IOS Release 10.0. The limit of 200 network commands per BGP router was removed in Cisco IOS Release 12.0. The maximum number of network commands you can use is now determined by the resources of the router, such as the amount of configured NVRAM or RAM. For the information to be advertised by BGP or multiprotocol BGP, a route to the network specified must be present in the routing table. The routing information may be learned from connected routes, dynamic routing, and from static route sources. Use the route-map keyword to apply a route map to a network to be advertised by the BGP and multiprotocol BGP routing processes. The specified route map can be used in filtering the network, or in setting attributes on the routes advertised by the network command.

Examples

The following example sets up network 10.108.0.0 to be included in the BGP updates:
router bgp 65000 network 10.108.0.0

Network Protocols Command Reference, Part 1

P1R-436

BGP Commands network (BGP)

The following example shows the use of the mask keyword:

router bgp 65001 network 10.0.0.0 mask 255.0.0.0 ! ip route 10.0.0.0 255.0.0.0 null0

Note

This configuration will advertise a supernet 10.0.0.0/8. It is necessary to use a static route to provide the information because this summary route may not be learned through dynamic routing or from a connected interface. Specifying the null 0 interface with the ip route command guarantees that the routing information will always be present in the routing table.

Related Commands

Command network backdoor router bgps

Description Specifies a backdoor route to a BGP border router that will provide better information about the network. Configures the Border Gateway Protocol (BGP) routing process.

Network Protocols Command Reference, Part 1

P1R-437

BGP Commands network backdoor

network backdoor
To specify a backdoor route to a BGP-learned prefix that provides better information about the network, use the network backdoor command in router configuration mode. To remove an address from the list, use the no form of this command. network address backdoor no network address backdoor

Syntax Description

address

IP address of the network to which you want a backdoor route.

Defaults

No network is advertised.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

A backdoor network is assigned an administrative distance of 200. The objective is to make Interior Gateway Protocol (IGP) learned routes preferred. A backdoor network is treated as a local network, except that it is not advertised. A network that is marked as a back door is not sourced by the local router, but should be learned from external neighbors. The BGP best path selection algorithm does not change when a network is configured as a back door.

Examples

The following example configures network 10.108.0.0 as a local network and network 192.31.7.0 as a backdoor network:
router bgp 109 network 10.108.0.0 network 192.31.7.0 backdoor

Network Protocols Command Reference, Part 1

P1R-438

BGP Commands router bgp

router bgp
To configure the Border Gateway Protocol (BGP) routing process, use the router bgp command in global configuration mode. To remove a routing process, use the no form of this command. router bgp autonomous-system no router bgp autonomous-system

Syntax Description

autonomous-system

Number of an autonomous system that identifies the router to other BGP routers and tags the routing information passed along.

Defaults

No BGP routing process is enabled by default.

Command Modes

Global configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

This command allows you to set up a distributed routing core that automatically guarantees the loop-free exchange of routing information between autonomous systems.

Examples

The following example configures a BGP process for autonomous system 120:
router bgp 120

Related Commands

Command network (BGP) timers bgp

Description Specifies the list of networks for the BGP routing process. Adjusts BGP network timers.

Network Protocols Command Reference, Part 1

P1R-439

BGP Commands set as-path

set as-path
To modify an autonomous system path for BGP routes, use the set as-path route map configuration command. To not modify the autonomous system path, use the no form of this command. set as-path {tag | prepend as-path-string} no set as-path {tag | prepend as-path-string}

Syntax Description

tag prepend as-path-string

Converts the tag of a route into an autonomous system path. Applies only when redistributing routes into BGP. Appends the string following the keyword prepend to the as-path of the route that is matched by the route map. Applies to inbound and outbound BGP route maps.

Defaults

Autonomous system path is not modified.

Command Modes

Route map configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

The only global BGP metric available to influence the best path selection is the AS-PATH length. By varying the length of the AS-PATH, a BGP speaker can influence the best path selection by a peer further away. By allowing you to convert the tag into an autonomous system path, the set as-path tag variation of this command modifies the autonomous system length. The set as-path prepend variation allows you to prepend an arbitrary autonomous system path string to BGP routes. Usually the local autonomous system number is prepended multiple times. This increases the autonomous system path length.

Examples

The following example converts the tag of a redistributed route into an autonomous system path:
route-map set-as-path-from-tag match as-path 2 set as-path prepend 100 100 100 ! router bgp 100 redistribute ospf 109 route-map set-as-path-from-tag

Network Protocols Command Reference, Part 1

P1R-440

BGP Commands set as-path

The following example prepends 100 100 100 to all the routes advertised to 10.108.1.1:
route-map set-as-path match as-path 1 set as-path prepend 100 100 100 ! router bgp 100 neighbor 10.108.1.1 route-map set-as-path out

Related Commands

Command match as-path match community-list match interface match ip address

Description Matches a BGP autonomous system path access list. Matches a BGP community. Distributes routes that have their next hop out one of the interfaces specified. Distributes any routes that have a destination network number address permitted by a standard or extended access list, or performs policy routing on packets. Redistributes any routes that have a next-hop router address passed by one of the access lists specified. Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. Redistributes routes with the metric specified. Redistributes routes of the specified type. Redistributes routes in the routing table that match the specified tags. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Automatically computes the tag value in a route map configuration. Sets the BGP COMMUNITIES attribute. Indicates where to import routes. Specifies a preference value for the autonomous system path. Sets the metric value for a routing protocol. Sets the metric type for the destination routing protocol. Specifies the address of the next hop. Sets the BGP origin code. Sets the value of the destination routing protocol. Specifies the BGP weight for the routing table.

match ip next-hop match ip route-source match metric match route-type match tag route-map set automatic-tag set community set level set local-preference set metric set metric-type set next-hop set origin set tag set weight

Network Protocols Command Reference, Part 1

P1R-441

BGP Commands set comm-list delete

set comm-list delete

To remove communities from the community attribute of an inbound or outbound update, use the set comm-list delete configuration command. To negate a previous set comm-list delete command, use the no form of this command. set comm-list list-num delete no set comm-list list-num delete

Syntax Description

list-num

A standard or extended community list number.

Defaults

No communities are removed.

Command Modes

Router configuration

Command History

Release 12.0

Modification This command was introduced.

Usage Guidelines

This route-map set command removes communities from the community attribute of an inbound or outbound update using a route map to filter and determine the communities to be deleted. Depending upon whether the route map is applied to the inbound or outbound update for a neighbor, each community that passes the route map permit clause and matches the given community list will be removed from the community attribute being received from or sent to the BGP neighbor. Each entry of a standard community list should list only one community when used with the set comm-list delete command. For example, in order to be able to delete communities 10:10 and 10:20, you must use the following format to create the entries:
ip community-list 5 permit 10:10 ip community-list 5 permit 10:20

The following format for a community list entry, while acceptable otherwise, does not work with the set comm-list delete command:
config ip community-list 5 permit 10:10 10:20

When both the set community comm and set comm-list delete commands are configured in the same sequence of a route-map attribute, the deletion operation (set comm-list delete) is performed before the set operation (set community comm).

Network Protocols Command Reference, Part 1

P1R-442

BGP Commands set comm-list delete

Examples

In the following example, the communities 100:10 and 100:20 (if present) will be deleted from updates received from 172.16.233.33. Also, except for 100:50, all communities beginning with 100: will be deleted from updates sent to 172.16.233.33.
router bgp 100 neighbor 172.16.233.33 remote-as 120 neighbor 172.16.233.33 route-map ROUTEMAPIN in neighbor 172.16.233.33 route-map ROUTEMAPOUT out ! ip community-list 1 permit 100:10 ip community-list 1 permit 100:20 ! ip community-list 120 deny 100:50 ip community-list 120 permit 100:.* ! route-map ROUTEMAPIN permit 10 set comm-list 1 delete ! route-map ROUTEMAPOUT permit 10 set comm-list 120 delete

Related Commands

Command set community

Description
Sets the BGP COMMUNITIES attribute.

Network Protocols Command Reference, Part 1

P1R-443

BGP Commands set community

set community
To set the BGP COMMUNITIES attribute, use the set community command in route-map configuration mode. To delete the entry, use the no form of this command. set community {community-number [additive]} | none no set community {community-number [additive]} | none

Syntax Description

community-number additive none

Specifies that community number. Valid values are 1 to 4294967200, no-export, or no-advertise. (Optional) Adds the community to the already existing communities. (Optional) Removes the COMMUNITY attribute from the prefixes that pass the route-map.

Defaults

No BGP COMMUNITIES attributes exist.

Command Modes

Route-map configuration

Command History

Release 10.3

Modification This command was introduced.

Usage Guidelines

You must have a match clause (even if it points to a permit everything list) if you want to set tags. Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actionsthe particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map. The set route-map configuration commands specify the redistribution set actions to be performed when all of a route maps match criteria are met. When all match criteria are met, all set actions are performed.

Network Protocols Command Reference, Part 1

P1R-444

BGP Commands set community

Examples

In the following example, routes that pass the autonomous system path access list 1 have the community set to 109. Routes that pass the autonomous system path access list 2 have the community set to no-export (these routes will not be advertised to any EBGP peers).
route-map set_community 10 permit match as-path 1 set community 109 route-map set_community 20 permit match as-path 2 set community no-export

In the following similar example, routes that pass the autonomous system path access list 1 have the community set to 109. Routes that pass the autonomous system path access list 2 have the community set to local-as (the router will not advertise this route to an EBGP peer outside the local autonomous system.
route-map set_community 10 permit match as-path 1 set community 109 route-map set_community 20 permit match as-path 2 set community local-as

Related Commands

Command ip community-list match community-list route-map set comm-list delete show ip bgp community

Description Creates a community list for BGP and control access to it. Matches a BGP community. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Removes communities from the community attribute of an inbound or outbound update. Displays routes that belong to specified BGP communities.

Network Protocols Command Reference, Part 1

P1R-445

BGP Commands set dampening

set dampening
To set the BGP route dampening factors, use the set dampening command in route-map configuration mode. To disable this function, use the no form of this command. set dampening half-life reuse suppress max-suppress-time no set dampening

Syntax Description

half-life

Time (in minutes) after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period (which is 15 minutes by default). 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 15 minutes. If the penalty for a flapping route decreases enough to fall below this value, the route is unsuppressed. The process of unsuppressing routes occurs at 10-second increments. The range of the reuse value is 1 to 20000; the default is 750. A route is suppressed when its penalty exceeds this limit. The range is 1 to 20000; the default is 2000. Maximum time (in minutes) a route can be suppressed. The range is 1 to 20000; the default is 4 times the half-life. If the half-life value is allowed to default, the maximum suppress time defaults to 60 minutes.

reuse

suppress max-suppress-time

Defaults

This command is disabled by default.

Command Modes

Route-map configuration

Command History

Release 11.0

Modification This command was introduced.

Usage Guidelines

You must have a match clause (even if it points to a permit everything list) if you want to set tags. Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actionsthe particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map. The set route-map configuration commands specify the redistribution set actions to be performed when all of a route maps match criteria are met. When all match criteria are met, all set actions are performed.

Network Protocols Command Reference, Part 1

P1R-446

BGP Commands set dampening

When a BGP peer is reset, the route is withdrawn and the flap statistics cleared. In this instance, the withdrawal does not incur a penalty even though route flap dampening is enabled.

Examples

The following example sets the half-life to 30 minutes, the reuse value to 1500, the suppress value to 10000; and the maximum suppress time to 120 minutes:
route-map tag match as path 10 set dampening 30 1500 10000 120 ! router bgp 100 neighbor 172.16.233.52 route-map tag in

Related Commands

Command match as-path match community-list match interface match ip address

Description Matches a BGP autonomous system path access list. Matches a BGP community. Distributes routes that have their next hop out one of the interfaces specified. Distributes any routes that have a destination network number address permitted by a standard or extended access list, or performs policy routing on packets. Redistributes any routes that have a next-hop router address passed by one of the access lists specified. Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. Redistributes routes with the metric specified. Redistributes routes of the specified type. Redistributes routes in the routing table that match the specified tags. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Automatically computes the tag value in a route map configuration. Sets the BGP COMMUNITIES attribute. Indicates where to import routes. Specifies a preference value for the autonomous system path. Sets the metric value for a routing protocol. Sets the metric type for the destination routing protocol. Specifies the address of the next hop. Sets the BGP origin code. Sets the value of the destination routing protocol. Specifies the BGP weight for the routing table. Displays configured route maps.

match ip next-hop match ip route-source match metric match route-type match tag route-map set automatic-tag set community set level set local-preference set metric set metric-type set next-hop set origin set tag set weight show route-map

Network Protocols Command Reference, Part 1

P1R-447

BGP Commands set ip next-hop (BGP)

set ip next-hop (BGP)

To indicate where to output packets that pass a match clause of a route map for policy routing, use the set ip next-hop route map configuration command. To delete an entry, use the no form of this command. set ip next-hop ip-address [...ip-address] [peer-address] no set ip next-hop ip-address [...ip-address] [peer-address]

Syntax Description

ip-address peer-address

IP address of the next hop to which packets are output. The next hop must be an adjacent router. (Optional) Sets the next hop to be the BGP peering address.

Defaults

This command is disabled by default.

Command Modes

Route map configuration

Command History

Release 11.0 12.0

Modification This command was introduced. The keyword peer-address was added.

Usage Guidelines

Use the ip policy route-map interface configuration command, the route-map global configuration command, and the match and set route map configuration commands, to define the conditions for policy routing packets. The ip policy route-map command identifies a route map by name. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which policy routing occurs. The set commands specify the set actionsthe particular routing actions to perform if the criteria enforced by the match commands are met. If the interface associated with the first next hop specified with the set ip next-hop command is down, the optionally specified IP addresses are tried in turn. When set ip next-hop is used with the peer-address keyword in an inbound route map of a BGP peer, the next hop of the received matching routes will be set to be the neighbor peering address, overriding any third-party next hops. This means that the same route map can be applied to multiple BGP peers to override third-party next hops. When set ip next-hop is used with the peer-address keyword in an outbound route map of a BGP peer, the next hop of the advertised matching routes will be set to be the peering address of the local router, thus disabling the next hop calculation. This command has finer granularity than the per-neighbor neighbor next-hop-self command, since you can set the next hop for some routes, but not others. The neighbor next-hop-self sets the next hop for all routes sent to that neighbor

Network Protocols Command Reference, Part 1

P1R-448

BGP Commands set ip next-hop (BGP)

The set clauses can be used in conjunction with one another. They are evaluated in the following order: set ip next-hop set interface set ip default next-hop set default interface

Examples

In the following example, packets with a Level 3 length of 3 to 50 bytes are output to the router at IP address 172.16.2.2:
interface serial 0 ip policy route-map thataway ! route-map thataway match length 3 50 set ip next-hop 172.16.2.2

In the following example, three routers are on the same FDDI LAN (with IP addresses 10.1.1.1, 10.1.1.2, and 10.1.1.3). Each is in a different autonomous system. The set ip next-hop peer-address command specifies that traffic from the router (10.1.1.3) in remote AS 300 for the router (10.1.1.1) in remote AS 100 that matches the route map is passed through the router bgp 200, rather than sent directly to the router (10.1.1.1) in AS 100 over their mutual connection to the LAN:
router bgp 200 neighbor 10.1.1.3 remote-as 100 neighbor 10.1.1.3 route-map set-peer-address out neighbor 10.1.1.1 remote-as 100 route-map set-peer-address permit 10 set ip next-hop peer-address

Related Commands

Command ip policy route-map match ip address

Description Identifies a route map to use for local policy routing. Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, or performs policy routing on packets. Bases policy routing on the Level 2 length of a packet. Disables next-hop processing of BGP updates on the router. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Indicates where to output packets that pass a match clause of a route map for policy routing and that have no explicit route to the destination. Indicates where to output packets that pass a match clause of a route map for policy routing. Indicates where to output packets that pass a match clause of a route map for policy routing and for which the Cisco IOS software has no explicit route to a destination.

match length neighbor next-hop-self route-map set default interface

set interface set ip default next-hop

Network Protocols Command Reference, Part 1

P1R-449

BGP Commands set metric-type internal

set metric-type internal

To set the MED value on prefixes advertised to EBGP neighbors to match the IGP metric of the next hop, use the set metric internal command in route-map configuration mode. To return to the default, use the no form of this command. set metric-type internal no set metric-type internal no set ip next-hop ip-address [...ip-address] [peer-address]

Syntax Description

This command has no arguments or keywords.

Defaults

This command is disabled by default.

Command Modes

Route-map configuration

Command History

Release 10.3

Modification This command was introduced.

Usage Guidelines

This command will cause BGP to advertise a MED that corresponds to the IGP metric associated with the NEXT HOP of the route. This command applies to generated, iBGP-, and eBGP-derived routes. If this command is used, multiple BGP speakers in a common AS can advertise different MEDs for a particular prefix. Also, note that if the IGP metric changes, BGP will not readvertise the route. You must have a match clause (even if it points to a permit everything list) if you want to set tags. Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actionsthe particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map. The set route-map configuration commands specify the redistribution set actions to be performed when all of a route maps match criteria are met. When all match criteria are met, all set actions are performed.

Network Protocols Command Reference, Part 1

P1R-450

BGP Commands set metric-type internal

Examples

In the following example, the MED for all the advertised routes to neighbor 172.16.2.3 is set to the corresponding IGP metric of the nexthop:
router bgp 109 network 172.16.0.0 neighbor 172.16.2.3 remote-as 200 neighbor 172.16.2.3 route-map setMED out ! route-map setMED permit 10 match as-path 1 set metric-type internal ! ip as-path access-list 1 permit .*

Related Commands

Command route-map

Description Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing.

Network Protocols Command Reference, Part 1

P1R-451

BGP Commands set origin

set origin
To set the BGP origin code, use the set origin command in route-map configuration mode. To delete an entry, use the no form of this command. set origin {igp | egp autonomous-system | incomplete} no set origin {igp | egp autonomous-system | incomplete}

Syntax Description

igp egp autonomous-system incomplete

Remote IGP. Local EGP. Remote autonomous system. This is an integer from 0 to 65535. Unknown heritage.

Defaults

Default origin, based on route in main IP routing table.

Command Modes

Route-map configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

You must have a match clause (even if it points to a permit everything list) if you want to set tags. Use the route-map global configuration command, and the match and set route-map configuration commands, to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteriathe conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actionsthe particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map. The set route-map configuration commands specify the redistribution set actions to be performed when all of a route maps match criteria are met. When all match criteria are met, all set actions are performed.

Examples

The following example sets the origin of routes that pass the route map to IGP:
route-map set_origin match as-path 10 set origin igp

Network Protocols Command Reference, Part 1

P1R-452

BGP Commands set origin

Related Commands

Command match as-path match community-list match interface match ip address

Description Matches a BGP autonomous system path access list. Matches a BGP community. Distributes routes that have their next hop out one of the interfaces specified. Distributes any routes that have a destination network number address permitted by a standard or extended access list, or performs policy routing on packets. Redistributes any routes that have a next-hop router address passed by one of the access lists specified. Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. Redistributes routes with the metric specified. Redistributes routes of the specified type. Redistributes routes in the routing table that match the specified tags. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Modifies an autonomous system path for BGP routes. Automatically computes the tag value in a route map configuration. Sets the BGP COMMUNITIES attribute. Indicates where to import routes. Specifies a preference value for the autonomous system path. Sets the metric value for a routing protocol. Sets the metric type for the destination routing protocol. Specifies the address of the next hop. Sets the value of the destination routing protocol. Specifies the BGP weight for the routing table.

match ip next-hop match ip route-source match metric match route-type match tag route-map set as-path set automatic-tag set community set level set local-preference set metric set metric-type set next-hop set tag set weight

Network Protocols Command Reference, Part 1

P1R-453

BGP Commands set weight

set weight
To specify the BGP weight for the routing table, use the set weight command in route-map configuration mode. To delete an entry, use the no form of this command. set weight weight no set weight weight

Syntax Description

weight

Weight value. It can be an integer from 0 to 65535.

Defaults

The weight is not changed by the specified route map.

Command Modes

Route-map configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

You must have a match clause (even if it points to a permit everything list) if you want to set tags. The implemented weight is based on the first matched autonomous system path. Weights indicated when an autonomous system path is matched override the weights assigned by global neighbor commands. In other words, the weights assigned with the match as-path and set weight route-map commands override the weights assigned using the neighbor weight and neighbor filter-list commands.

Examples

The following example sets the BGP weight for the routes matching the autonomous system path access list to 200:
route-map set-weight match as-path 10 set weight 200

Network Protocols Command Reference, Part 1

P1R-454

BGP Commands set weight

Related Commands

Command match as-path match community-list match interface match ip address

Description Matches a BGP autonomous system path access list. Matches a BGP community. Distributes routes that have their next hop out one of the interfaces specified. Distributes any routes that have a destination network number address permitted by a standard or extended access list, or performs policy routing on packets. Redistributes any routes that have a next-hop router address passed by one of the access lists specified. Redistributes routes that have been advertised by routers and access servers at the address specified by the access lists. Redistributes routes with the metric specified. Redistributes routes of the specified type. Redistributes routes in the routing table that match the specified tags. Defines the conditions for redistributing routes from one routing protocol to another, or enables policy routing. Modifies an autonomous system path for BGP routes. Automatically computes the tag value in a route map configuration. Sets the BGP COMMUNITIES attribute. Indicates where to import routes. Specifies a preference value for the autonomous system path. Sets the metric value for a routing protocol. Sets the metric type for the destination routing protocol. Specifies the address of the next hop. Sets the BGP origin code. Sets the value of the destination routing protocol.

match ip next-hop match ip route-source match metric match route-type match tag route-map set as-path set automatic-tag set community set level set local-preference set metric set metric-type set next-hop set origin set tag

Network Protocols Command Reference, Part 1

P1R-455

BGP Commands show ip bgp

show ip bgp
To display entries in the BGP routing table, use the show ip bgp command in EXEC mode. show ip bgp [network] [network-mask] [longer-prefixes]

Syntax Description

network network-mask longer-prefixes

(Optional) Network number, entered to display a particular network in the BGP routing table. (Optional) Displays all BGP routes matching the address/mask pair. (Optional) Displays route and more specific routes.

Command Modes

EXEC

Command History

Release 10.0 12.0

Modification This command was introduced. The display of prefix advertisement statistics was added.

Examples

The following is sample output from the show ip bgp command:

Router# show ip bgp BGP table version is 716977, local router ID is 193.0.32.1 Status codes: s suppressed, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network * i3.0.0.0 *>i * i6.0.0.0 *>i * i7.0.0.0 *>i * * i8.0.0.0 *>i * * i13.0.0.0 *>i * * i15.0.0.0 *>i * i16.0.0.0 *>i * Next Hop 193.0.22.1 193.0.16.1 193.0.22.1 193.0.16.1 193.0.22.1 193.0.16.1 172.16.72.24 193.0.22.1 193.0.16.1 172.16.72.24 193.0.22.1 193.0.16.1 172.16.72.24 193.0.22.1 193.0.16.1 193.0.22.1 193.0.16.1 172.16.72.24 Metric LocPrf Weight Path 0 100 0 1800 1239 ? 0 100 0 1800 1239 ? 0 100 0 1800 690 568 ? 0 100 0 1800 690 568 ? 0 100 0 1800 701 35 ? 0 100 0 1800 701 35 ? 0 1878 704 701 35 ? 0 100 0 1800 690 560 ? 0 100 0 1800 690 560 ? 0 1878 704 701 560 ? 0 100 0 1800 690 200 ? 0 100 0 1800 690 200 ? 0 1878 704 701 200 ? 0 100 0 1800 174 ? 0 100 0 1800 174 ? 0 100 0 1800 701 i 0 100 0 1800 701 i 0 1878 704 701 i

Table 39 describes significant fields shown in the display.

Network Protocols Command Reference, Part 1

P1R-456

BGP Commands show ip bgp

Table 39

show ip bgp Field Descriptions

Field BGP table version local router ID Status codes

Description Internal version number of the table. This number is incremented whenever the table changes. IP address of the router. 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: sThe table entry is suppressed. *The table entry is valid. >The table entry is the best entry to use for that network. iThe table entry was learned via an internal BGP session.

Origin codes

Indicates the 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: iEntry originated from IGP and was advertised with a network router configuration command. eEntry originated from EGP. ?Origin of the path is not clear Usually, this is a router that is redistributed into BGP from an IGP.

Network Next Hop

IP address of a network entity. 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. If shown, this is the value of the interautonomous system metric. This field is frequently not used. Local preference value as set with the set local-preference route-map configuration command. The default value is 100. Weight of the route as set via autonomous system filters. Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path.

Metric LocPrf Weight Path

Network Protocols Command Reference, Part 1

P1R-457

BGP Commands show ip bgp

The following is sample output from the show ip bgp command when you specify longer-prefixes:
Router# show ip bgp 172.16.0.0 255.255.0.0 longer-prefixes 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 172.16.0.0 172.16.1.0 172.16.11.0 172.16.14.0 172.16.15.0 172.16.16.0 172.16.17.0 172.16.18.0 172.16.19.0 Next Hop 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 Metric LocPrf Weight Path 8896 32768 ? 0 109 108 8796 32768 ? 0 109 108 42482 32768 ? 0 109 108 8796 32768 ? 0 109 108 8696 32768 ? 0 109 108 1400 32768 ? 0 109 108 1400 32768 ? 0 109 108 8876 32768 ? 0 109 108 8876 32768 ? 0 109 108

*> * *> * *> * *> * *> * *> * *> * *> * *> *

? ? ? ? ? ? ? ? ?

The following is sample output from the show ip bgp command, showing information for prefix 3.0.0.0:
show ip bgp 3.0.0.0 BGP routing table entry for 3.0.0.0/8, version 628 Paths: (1 available, best #1) Advertised to peer-groups: ebgp Advertised to non peer-group peers: 172.16.232.162 109 65000 297 701 80 172.16.233.56 from 172.16.233.56 (172.19.185.32) Origin incomplete, localpref 100, valid, external, best, ref 2

Note

If a prefix has not been advertised to any peer, the display shows Not advertised to any peer.

Network Protocols Command Reference, Part 1

P1R-458

BGP Commands show ip bgp cidr-only

show ip bgp cidr-only

To display routes with nonnatural network masks (that is, classless interdomain routing, or CIDR), use the show ip bgp cidr-only privileged command in EXEC mode. show ip bgp cidr-only

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release 10.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp cidr-only command:
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 *> 192.168.0.0/8 *> 172.16.0.0/16 Next Hop 172.16.72.24 172.16.72.30 Metric LocPrf Weight Path 0 1878 ? 0 108 ?

Table 40 describes significant fields shown in the display.

Table 40 show ip bgp cidr-only Field Descriptions

Field BGP table version is 220 local router ID Status codes

Description Internal version number of the table. This number is incremented any time the table changes. An Internet address of the router. sThe table entry is suppressed. *The table entry is valid. >The table entry is the best entry to use for that network. iThe table entry was learned via an internal BGP session.

Network Protocols Command Reference, Part 1

P1R-459

BGP Commands show ip bgp cidr-only

Table 40

show ip bgp cidr-only Field Descriptions (continued)

Field Origin codes

Description Indicates the 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: iEntry originated from IGP and was advertised with a network router configuration command. eEntry originated from EGP. ?Origin of the path is not clear Usually, this is a router that is redistributed into BGP from an IGP.

Network Next Hop

Internet address of the network the entry describes. 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. If shown, this is the value of the interautonomous system metric. This field is frequently not used. Local preference value. Default is 100. Weight of the route as set via autonomous system filters. 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. iThe entry was originated with the IGP and advertised with a network router configuration command. eThe 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.

Metric LocPrf Weight Path

Network Protocols Command Reference, Part 1

P1R-460

BGP Commands show ip bgp community

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 community number in the range 1 to 4294967200, internet, no-export, local-as, or no-advertise. You must enter the numerical communities before the well-known communities. For example, the following does not work: router#sh ip b community local-as 111:12345 Use the following instead: router#sh ip b community 111:12345 local-as

exact

(Optional) Displays only routes that have exactly the same specified communities.

Command Modes

EXEC

Command History

Release 10.3 12.0

Modification This command was introduced. The local-as community was added.

Examples

The following is sample output from the show ip bgp community command:
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 172.16.2.2/32 10.0.0.0 172.43.0.0 172.43.44.44/32 172.43.222.0/24 172.17.240.0/21 192.168.212.0 172.39.1.0 Next Hop 172.43.222.2 172.43.222.2 172.43.222.2 172.43.222.2 172.43.222.2 172.43.222.2 172.43.222.2 172.43.222.2 Metric LocPrf Weight Path 0 0 222 ? 0 0 222 ? 0 0 222 ? 0 0 222 ? 0 0 222 i 0 0 222 ? 0 0 222 i 0 0 222 ?

*> *> *> *> * *> *> *>

Network Protocols Command Reference, Part 1

P1R-461

BGP Commands show ip bgp community

Table 41 describes significant fields shown in the display.

Table 41 show ip bgp community Field Descriptions

Field BGP table version local router ID Status codes

Description Internal version number of the table. This number is incremented whenever the table changes. IP address of the router. 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: sThe table entry is suppressed. *The table entry is valid. >The table entry is the best entry to use for that network. iThe table entry was learned via an internal BGP session.

Origin codes

Indicates the 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: iEntry originated from IGP and was advertised with a network router configuration command. eEntry originated from EGP. ?Origin of the path is not clear Usually, this is a router that is redistributed into BGP from an IGP.

Network Next Hop

IP address of a network entity. 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. If shown, this is the value of the interautonomous system metric. This field is frequently not used. Local preference value as set with the set local-preference route-map configuration command. The default value is 100. Weight of the route as set via autonomous system filters. Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path.

Metric LocPrf Weight Path

Network Protocols Command Reference, Part 1

P1R-462

BGP Commands show ip bgp community-list

show ip bgp community-list

To display routes that are permitted by the BGP community list, use the show ip bgp community-list command in EXEC mode. show ip bgp community-list community-list-number [exact]

Syntax Description

community-list-number exact

Community list number in the range 1 to 99. (Optional) Displays only routes that have an exact match.

Command Modes

EXEC

Command History

Release 10.3

Modification This command was introduced.

Examples

The following is sample output of the show ip bgp community-list command:

Router# show ip bgp community-list 20 BGP table version is 716977, local router ID is 193.0.32.1 Status codes: s suppressed, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network * i3.0.0.0 *>i * i6.0.0.0 *>i * i7.0.0.0 *>i * * i8.0.0.0 *>i * * i13.0.0.0 *>i * * i15.0.0.0 *>i * i16.0.0.0 *>i * Next Hop 193.0.22.1 193.0.16.1 193.0.22.1 193.0.16.1 193.0.22.1 193.0.16.1 172.16.72.24 193.0.22.1 193.0.16.1 172.16.72.24 193.0.22.1 193.0.16.1 172.16.72.24 193.0.22.1 193.0.16.1 193.0.22.1 193.0.16.1 172.16.72.24 Metric LocPrf Weight Path 0 100 0 1800 1239 ? 0 100 0 1800 1239 ? 0 100 0 1800 690 568 ? 0 100 0 1800 690 568 ? 0 100 0 1800 701 35 ? 0 100 0 1800 701 35 ? 0 1878 704 701 35 ? 0 100 0 1800 690 560 ? 0 100 0 1800 690 560 ? 0 1878 704 701 560 ? 0 100 0 1800 690 200 ? 0 100 0 1800 690 200 ? 0 1878 704 701 200 ? 0 100 0 1800 174 ? 0 100 0 1800 174 ? 0 100 0 1800 701 i 0 100 0 1800 701 i 0 1878 704 701 i

Network Protocols Command Reference, Part 1

P1R-463

BGP Commands show ip bgp community-list

Table 42 describes significant fields shown in the display.

Table 42 show ip bgp community-list Field Descriptions

Field BGP table version local router ID Status codes

Description Internal version number of the table. This number is incremented whenever the table changes. IP address of the router. 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: sThe table entry is suppressed. *The table entry is valid. >The table entry is the best entry to use for that network. iThe table entry was learned via an internal BGP session.

Origin codes

Indicates the 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: iEntry originated from IGP and was advertised with a network router configuration command. eEntry originated from EGP. ?Origin of the path is not clear Usually, this is a router that is redistributed into BGP from an IGP.

Network Next Hop

IP address of a network entity. 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. If shown, this is the value of the interautonomous system metric. This field is frequently not used. Local preference value as set with the set local-preference route-map configuration command. The default value is 100. Weight of the route as set via autonomous system filters. Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path.

Metric LocPrf Weight Path

Network Protocols Command Reference, Part 1

P1R-464

BGP Commands show ip bgp dampened-paths

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 11.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp dampened-paths command:
Router# show ip bgp dampened-paths BGP table version is 10, local router ID is 172.16.232.182 Status codes: s suppressed, d damped, h history, * valid, > best, i internal Origin codes: i - IGP, e - EGP, ? - incomplete Network *d 10.0.0.0 *d 12.0.0.0 From 172.16.232.177 172.16.232.177 Reuse Path 00:18:4 100 ? 00:28:5 100 ?

Table 43 describes the fields in the display.

Table 43 show ip bgp dampened-paths Field Descriptions

Field BGP table version local router *d Network From Reuse Path

Description Internal version number of the table. This number is incremented any time the table changes. IP address of the router where route dampening is enabled. Route to the network indicated is dampened. IP address of the peer that advertised this path. Time (in hours:minutes:seconds) after which the path will be made available. AS-path of the route that is being dampened.

Related Commands

Command bgp dampening clear ip bgp dampening

Description Enables BGP route dampening or change various BGP route dampening factors. Clears BGP route dampening information and unsuppress the suppressed routes.

Network Protocols Command Reference, Part 1

P1R-465

BGP Commands show ip bgp filter-list

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.

Command Modes

EXEC

Command History

Release 10.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp filter-list command:
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 172.16.0.0 172.16.1.0 172.16.11.0 172.16.14.0 172.16.15.0 172.16.16.0 172.16.17.0 172.16.18.0 172.16.19.0 172.16.24.0 172.16.29.0 172.16.30.0 172.16.33.0 172.16.35.0 172.16.36.0 172.16.37.0 172.16.38.0 172.16.39.0 Next Hop 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 Metric LocPrf Weight 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Path 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108

* * * * * * * * * * * * * * * * * *

? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

Network Protocols Command Reference, Part 1

P1R-466

BGP Commands show ip bgp filter-list

Table 44 describes significant fields shown in the display.

Table 44 show ip bgp lter-List Field Descriptions

Field BGP table version local router ID Status codes

Description Internal version number of the table. This number is incremented any time the table changes. An Internet address of the access server. sThe table entry is suppressed. *The table entry is valid. >The table entry is the best entry to use for that network. iThe table entry was learned via an internal BGP session.

Origin codes

Indicates the 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: iEntry originated from IGP and was advertised with a network router configuration command. eEntry originated from EGP. ?Origin of the path is not clear Usually, this is a router that is redistributed into BGP from an IGP.

Network Next Hop

Internet address of the network the entry describes. 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. If shown, this is the value of the interautonomous system metric. This field is frequently not used. Local preference value. Default is 100. Weight of the route as set via autonomous system filters. 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. iThe entry was originated with the IGP and advertised with a network router configuration command. eThe 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.

Metric LocPrf Weight Path

Network Protocols Command Reference, Part 1

P1R-467

BGP Commands show ip bgp flap-statistics

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 list} | {address mask [longer-prefix]}]

Syntax Description

regexp regexp filter-list list address mask longer-prefix

(Optional) Clears flap statistics for all the paths that match the regular expression. (Optional) Clears flap statistics for all the paths that pass the access list. (Optional) Clears flap statistics for a single entry at this IP address. (Optional) Network mask applied to the address. (Optional) Displays flap statistics for more specific entries.

Command Modes

EXEC

Command History

Release 11.0

Modification This command was introduced.

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:
Router# show ip bgp flap-statistics BGP table version is 10, local router ID is 172.16.232.182 Status codes: s suppressed, d damped, h history, * valid, > best, i internal Origin codes: i - IGP, e - EGP, ? - incomplete Network *d 10.0.0.0 *d 12.0.0.0 From 172.16.232.177 172.16.232.177 Flaps Duration Reuse Path 4 00:13:31 00:18:10 100 4 00:02:45 00:28:20 100

Network Protocols Command Reference, Part 1

P1R-468

BGP Commands show ip bgp flap-statistics

Table 45 describes the significant fields in the display.

Table 45 show ip bgp ap-statistics Field Descriptions

Field BGP table version local router ID Network From Flaps Duration Reuse Path

Description Internal version number of the table. This number is incremented any time the table changes. IP address of the router where route dampening is enabled. Route to the network indicated is dampened. IP address of the peer that advertised this path. Number of times the route has flapped. Time (in hours:minutes:seconds) since the router noticed the first flap. Time (in hours:minutes:seconds) after which the path will be made available. AS-path of the route that is being dampened.

Related Commands

Command bgp dampening clear ip bgp flap-statistics

Description Enables BGP route dampening or change various BGP route dampening factors. Clears BGP flap statistics.

Network Protocols Command Reference, Part 1

P1R-469

BGP Commands show ip bgp inconsistent-as

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 11.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp inconsistent-as command:
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 * 11.0.0.0 *> * 172.16.0.0 *> * 200.200.199.0 *> Next Hop 172.16.232.55 172.16.232.52 172.16.232.55 172.16.232.52 172.16.232.55 172.16.232.52 Metric LocPrf Weight Path 0 0 300 88 90 99 ? 2222 0 400 ? 0 0 300 90 99 88 200 ? 2222 0 400 ? 0 0 300 88 90 99 ? 2222 0 400 ?

Network Protocols Command Reference, Part 1

P1R-470

BGP Commands show ip bgp neighbors

show ip bgp neighbors

To display information about the TCP and BGP connections to neighbors, use the show ip bgp neighbors command in EXEC mode. show ip bgp neighbors [address] [received-routes | routes | advertised-routes | {paths regular-expression} | dampened-routes]

Syntax Description

address received-routes routes advertised-routes paths regular-expression dampened-routes

(Optional) Address of the neighbor whose routes you have learned from. If you omit this argument, all neighbors are displayed. (Optional) Displays all received routes (both accepted and rejected) from the specified neighbor. (Optional) Displays all routes that are received and accepted. This is a subset of the output from the received-routes keyword. (Optional) Displays all the routes the router has advertised to the neighbor. (Optional) Regular expression that is used to match the paths received. (Optional) Displays the dampened routes to the neighbor at the IP address specified.

Command Modes

EXEC

Command History

Release 10.0 11.2

Modification This command was introduced. The received-routes keyword was added.

Network Protocols Command Reference, Part 1

P1R-471

BGP Commands show ip bgp neighbors

Examples

The following is sample output from the show ip bgp neighbors command:
Router# show ip bgp neighbors 172.16.232.178 BGP neighbor is 172.16.232.178, remote AS 10, external link Index 1, Offset 0, Mask 0x2 Inbound soft reconfiguration allowed BGP version 4, remote router ID 172.16.232.178 BGP state = Established, table version = 27, up for 00:06:12 Last read 00:00:12, hold time is 180, keepalive interval is 60 seconds Minimum time between advertisement runs is 30 seconds Received 19 messages, 0 notifications, 0 in queue Sent 17 messages, 0 notifications, 0 in queue Inbound path policy configured Route map for incoming advertisements is testing Connections established 2; dropped 1 Connection state is ESTAB, I/O status: 1, unread input bytes: 0 Local host: 172.16.232.181, Local port: 11002 Foreign host: 172.16.232.178, Foreign port: 179 Enqueued packets for retransmit: 0, input: 0, saved: 0 Event Timers (current time is 0x530C294): Timer Starts Wakeups Retrans 12 0 TimeWait 0 0 AckHold 12 10 SendWnd 0 0 KeepAlive 0 0 GiveUp 0 0 PmtuAger 0 0 iss: 133981889 irs: 3317025518 snduna: 133982166 rcvnxt: 3317025810 sndnxt: rcvwnd:

Next 0x0 0x0 0x0 0x0 0x0 0x0 0x0 133982166 16093 sndwnd: delrcvwnd: 16108 291

SRTT: 441 ms, RTTO: 2784 ms, RTV: 951 ms, KRTT: 0 ms minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms Flags: higher precedence, nagle Datagrams (max data segment is 1460 bytes): Rcvd: 15 (out of order: 0), with data: 12, total data bytes: 291 Sent: 23 (retransmit: 0), with data: 11, total data bytes: 276

Table 46 describes the fields shown in the display.

Table 46 show ip bgp neighbors Field Descriptions

Field BGP neighbor

Description IP address of the BGP neighbor and its autonomous system number. If the neighbor is in the same autonomous system as the router, then the link between them is internal; otherwise, it is considered external. BGP version being used to communicate with the remote router; the neighbors router ID (an IP address) is also specified. Internal state of this BGP connection. Indicates that the neighbor has been updated with this version of the primary BGP routing table. Amount of time that the underlying TCP connection has been in existence.

BGP version BGP state table version up for

Network Protocols Command Reference, Part 1

P1R-472

BGP Commands show ip bgp neighbors

Table 46

show ip bgp neighbors Field Descriptions (continued)

Field Last read hold time keepalive interval Received notifications Sent notifications Connections established dropped Connection state unread input bytes

Description Time that BGP last read a message from this neighbor. Maximum amount of time that can elapse between messages from the peer. Time period between sending keepalive packets, which help ensure that the TCP connection is up. Number of total BGP messages received from this peer, including keepalives. Number of error messages received from the peer. Total number of BGP messages that have been sent to this peer, including keepalives. Number of error messages the router has sent to this peer. Number of times the router has established a TCP connection and the two peers have agreed speak BGP with each other. Number of times that a good connection has failed or been taken down. State of BGP peer. Number of bytes of packets still to be processed.

Local host, Local port Peering address of local router, plus port. Foreign host, Foreign Neighbors peering address. port Event Timers iss snduna sndnxt sndwnd irs rcvnxt rcvwnd delrecvwnd Table displays the number of starts and wakeups for each timer. Initial send sequence number. Last send sequence number the local host sent but has not received an acknowledgment for. Sequence number the local host will send next. TCP window size of the remote host. Initial receive sequence number. Last receive sequence number the local host has acknowledged. Local hosts TCP window size. Delayed receive windowdata 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. A calculated smoothed round-trip timeout. Round-trip timeout. Variance of the round-trip time. New round-trip timeout (using the Karn algorithm). This field separately tracks the round-trip time of packets that have been retransmitted.

SRTT RTTO RTV KRTT

Network Protocols Command Reference, Part 1

P1R-473

BGP Commands show ip bgp neighbors

Table 46

show ip bgp neighbors Field Descriptions (continued)

Field minRTT maxRTT ACK hold Flags Datagrams: Rcvd with data total data bytes Sent with data total data bytes

Description Smallest recorded round-trip timeout (hard wire value used for calculation). Largest recorded round-trip timeout. Time the local host will delay an acknowledgment in order to piggyback data on it. IP precedence of the BGP packets. Number of update packets received from neighbor. Number of update packets received with data. Total bytes of data. Number of update packets sent. Number of update packets with data sent. Total number of data bytes.

The following is sample output from the show ip bgp neighbors command with advertised-routes:
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 *>i110.0.0.0 *> 200.2.2.0 Next Hop 172.16.232.179 0.0.0.0 Metric LocPrf Weight Path 0 100 0 ? 0 32768 i

The following is sample output from the show ip bgp neighbors command with routes:
Router# show ip bgp neighbors 172.16.232.178 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 *> 10.0.0.0 *> 10.2.0.0 Next Hop 172.16.232.178 172.16.232.178 Metric LocPrf Weight Path 40 0 10 ? 40 0 10 ?

Table 47 describes the fields shown in the display.

Table 47 show ip bgp neighbors Advertised-Routes and Routes Field Descriptions

Field BGP table version local router ID

Description Internal version number of the table. This number is incremented whenever the table changes. IP address of the router.

Network Protocols Command Reference, Part 1

P1R-474

BGP Commands show ip bgp neighbors

Table 47

show ip bgp neighbors Advertised-Routes and Routes Field Descriptions (continued)

Field Status codes

Description sThe table entry is suppressed. *The table entry is valid. >The table entry is the best entry to use for that network. iThe table entry was learned via an internal BGP session.

Origin codes

Indicates the 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: iEntry originated from IGP and was advertised with a network router configuration command. eEntry originated from EGP. ?Origin of the path is not clear Usually, this is a router that is redistributed into BGP from an IGP.

Network Next Hop

IP address of a network entity. 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. If shown, this is the value of the interautonomous system metric. This field is frequently not used. Local preference value as set with the set local-preference route-map configuration command. The default value is 100. Weight of the route as set via autonomous system filters. Autonomous system paths to the destination network. There can be one entry in this field for each autonomous system in the path.

Metric LocPrf Weight Path

The following is sample output from the show ip bgp neighbors command with paths:
Router# show ip bgp neighbors 172.16.232.178 paths ^10 Address Refcount Metric Path 0x60E577B0 2 40 10 ?

Network Protocols Command Reference, Part 1

P1R-475

BGP Commands show ip bgp paths

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

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release 10.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp paths command:
Router# show ip bgp paths Address Hash Refcount Metric 0x60E5742C 0 1 0 0x60E3D7AC 2 1 0 0x60E5C6C0 11 3 0 0x60E577B0 35 2 40 Path i ? 10 ? 10 ?

Table 48 describes significant fields shown in the display.

Table 48 show ip bgp paths Field Descriptions

Field Address Hash Refcount Metric

Description Internal address where the path is stored. Hash bucket where path is stored. Number of routes using that path. The Multi Exit Discriminator (MED) metric for the path. (The name of this metric for BGP versions 2 and 3 is INTER_AS.) The AS_PATH for that route, followed by the origin code for that route.

Path

Network Protocols Command Reference, Part 1

P1R-476

BGP Commands show ip bgp peer-group

show ip bgp peer-group

To display information about BGP peer groups, use the show ip bgp peer-group command in EXEC mode. show ip bgp peer-group [tag] [summary]

Syntax Description

tag summary

(Optional) Displays information about that specific peer group. (Optional) Displays a summary of the status of all the members of a peer group.

Command Modes

EXEC

Command History

Release 11.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp peer-group command:
Router# show ip bgp peer-group0 internal BGP neighbor is internal, peer-group leader BGP version 4 Minimum time between advertisement runs is 5 seconds Incoming update AS path filter list is 2 Outgoing update AS path filter list is 1 Route map for outgoing advertisements is set-med

Network Protocols Command Reference, Part 1

P1R-477

BGP Commands show ip bgp regexp

show ip bgp regexp

To display routes matching the regular expression, use the show ip bgp regexp privileged command in EXEC mode. show ip bgp regexp regular-expression

Syntax Description

regular-expression

Regular expression to match the BGP autonomous system paths.

Command Modes

Privileged EXEC

Command History

Release 10.0

Modification This command was introduced.

Examples

The following is sample output from the show ip bgp regexp command:
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 172.16.0.0 172.16.1.0 172.16.11.0 172.16.14.0 172.16.15.0 172.16.16.0 172.16.17.0 172.16.18.0 172.16.19.0 172.16.24.0 172.16.29.0 172.16.30.0 172.16.33.0 172.16.35.0 172.16.36.0 172.16.37.0 172.16.38.0 172.16.39.0 Next Hop 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 172.16.72.30 Metric LocPrf Weight 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Path 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108 109 108

* * * * * * * * * * * * * * * * * *

? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

Network Protocols Command Reference, Part 1

P1R-478

BGP Commands show ip bgp summary

show ip bgp summary

To display the status of all BGP connections, use the show ip bgp summary command in EXEC mode. show ip bgp summary

Syntax Description

This command has no arguments or keywords.

Command Modes

EXEC

Command History

Release 10.0 12.0

Modification This command was introduced. The PfxRcd and Admin entries were added.

Examples

The following is sample output from the show ip bgp summary command:
Router# show ip bgp summary BGP table version is 717029, main routing table version 717029 19073 network entries (37544 paths) using 3542756 bytes of memory 691 BGP path attribute entries using 57200 bytes of memory Neighbor 193.0.16.1 193.0.17.1 193.0.18.1 193.0.19.1 193.0.20.1 193.0.21.1 193.0.22.1 193.0.23.1 193.0.24.1 193.0.25.1 193.0.26.1 193.0.27.1 193.0.28.1 172.16.72.24 172.16.72.36 V 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 AS MsgRcvd MsgSent 1755 32642 2973 1755 4790 2973 1755 7722 3024 1755 0 0 1755 3673 3049 1755 3741 3048 1755 33129 3051 1755 0 0 1755 0 0 1755 0 0 1755 0 0 1755 4269 3049 1755 3037 3050 1878 11635 13300 1001 0 0 TblVer 717029 717029 717029 0 717029 717029 717029 0 0 0 0 717029 717029 717028 0 InQ OutQ Up/Down 0 0 1:27:11 0 0 1:27:51 0 0 1:28:13 0 0 2d02 0 0 2:50:10 0 0 12:24:43 0 0 12:24:48 0 0 2d02 0 0 2d02 0 0 2d02 0 0 2d02 0 0 12:39:33 0 0 2:08:15 0 0 0:50:39 0 0 never State/PfxRcd

Active Idle (PfxRcd)

Active Active Active Active

Idle (Admin)

Table 49 describes significant fields shown in the display

.

Table 49

show ip bgp summary Field Descriptions

Field BGP table version main routing table version Neighbor

Description Internal version number of BGP database. Last version of BGP database that was injected into main routing table. IP address of a neighbor.

Network Protocols Command Reference, Part 1

P1R-479

BGP Commands show ip bgp summary

Table 49

show ip bgp summary Field Descriptions (continued)

Field V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

Description BGP version number spoken to that neighbor. Autonomous system. BGP messages received from that neighbor. BGP messages sent to that neighbor. Last version of the BGP database that was sent to that neighbor. Number of messages from that neighbor waiting to be processed. Number of messages waiting to be sent to that neighbor. The length of time that the BGP session has been in state Established, or the current state if it is not Established. Current state of the BGP session/the number of prefixes the router has 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 Idle. An (Admin) entry with Idle status indicates that the connection has been shut down using the neighbor shutdown command.

Related Commands

Command neighbor maximum-prefix neighbor shutdown show ip bgp summary

Description Controls how many prefixes can be received from a neighbor. Disables a neighbor or peer group. Display the status of all BGP connections.

Network Protocols Command Reference, Part 1

P1R-480

BGP Commands synchronization

synchronization
To enable the synchronization between BGP and your IGP, use the synchronization command in router configuration mode. To enable the Cisco IOS software to advertise a network route without waiting for the IGP, use the no form of this command. synchronization no synchronization

Syntax Description

This command has no arguments or keywords.

Defaults

The behavior of this command is enabled by default.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

Usually, a BGP speaker does not advertise a route to an external neighbor unless that route is local or exists in the IGP. The no synchronization command allows the Cisco IOS software to advertise a network route without waiting for the IGP. This feature allows routers and access servers within an autonomous system to have the route before BGP makes it available to other autonomous systems. Use synchronization if there are routers in the autonomous system that do not speak BGP.

Examples

The following example enables a router to advertise a network route without waiting for the IGP:
router bgp 120 no synchronization

Network Protocols Command Reference, Part 1

P1R-481

BGP Commands table-map

table-map
To modify metric and tag values when the IP routing table is updated with BGP learned routes, use the table-map command in router configuration mode. To disable this function, use the no form of the command. table-map route-map-name no table-map route-map-name

Syntax Description

route-map-name

Route-map name, from the route-map command.

Defaults

This command is disabled by default.

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Usage Guidelines

This command adds the route-map name defined by the route-map command to the IP routing table. This command is used to set the tag name and the route metric to implement redistribution. You can use match clauses of route maps in the table-map command. IP access list, autonomous system paths, and next-hop match clauses are supported.

Examples

In the following example, the Cisco IOS software is configured to automatically compute the tag value for the BGP learned routes and to update the IP routing table.
route-map tag match as path 10 set automatic-tag ! router bgp 100 table-map tag

Network Protocols Command Reference, Part 1

P1R-482

BGP Commands table-map

Related Commands

Command match as-path match ip address

Description Matches a BGP autonomous system path access list. Distributes any routes that have a destination network number address that is permitted by a standard or extended access list, or performs policy routing. Redistributes any routes that have a next-hop router address passed by one of the access lists specified. Defines the conditions for redistributing routes form one routing protocol into another, or enables policy routing.

match ip next-hop route-map

Network Protocols Command Reference, Part 1

P1R-483

BGP Commands timers bgp

timers bgp
To adjust BGP network timers, use the timers bgp command in router configuration mode. To reset the BGP timing defaults, use the no form of this command. timers bgp keepalive holdtime no timers bgp

Syntax Description

keepalive

Frequency, in seconds, with which the Cisco IOS software sends keepalive messages to its peer. The default is 60 seconds. Interval, in seconds, after not receiving a keepalive message that the software declares a peer dead. The default is 180 seconds.

holdtime

Defaults

keepalive: 60 seconds holdtime: 180 seconds

Command Modes

Router configuration

Command History

Release 10.0

Modification This command was introduced.

Examples

The following example changes the keepalive timer to 70 seconds and the holdtime timer to 210 seconds:
timers bgp 70 210

Related Commands

Command clear ip bgp peer-group router bgp show ip bgp

Description Removes all the members of a BGP peer group. Configures the Border Gateway Protocol (BGP) routing process. Display entries in the BGP routing table.

Network Protocols Command Reference, Part 1

P1R-484