Table Of Contents
BGP Prefix-Based Outbound Route Filtering
Prerequisites for BGP Prefix-Based Outbound Route Filtering
Restrictions for BGP Prefix-Based Outbound Route Filtering
Information About BGP Prefix-Based Outbound Route Filtering
BGP Prefix-Based Outbound Route Filtering Overview
Enabling BGP Prefix-Based Outbound Route Filtering
Benefits of BGP Prefix-Based Outbound Route Filtering
How to Configure BGP Prefix-Based Outbound Route Filtering
Configuring BGP Prefix-Based Outbound Route Filtering
Verifying BGP Prefix-Based Outbound Route Filtering
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Send Mode
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Receive Mode
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Send and Receive Modes
BGP Prefix-Based Outbound Route Filtering
The BGP Prefix-Based Outbound Route Filtering feature uses Border Gateway Protocol (BGP) outbound route filter (ORF) send and receive capabilities to minimize the number of BGP updates that are sent between peer routers. The configuration of this feature can help reduce the amount of resources required for generating and processing routing updates by filtering out unwanted routing updates at the source. For example, this feature can be used to reduce the amount of processing required on a router that is not accepting full routes from a service provider network.
Feature History for BGP Prefix-Based Outbound Route Filtering
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•
Prerequisites for BGP Prefix-Based Outbound Route Filtering
•
Restrictions for BGP Prefix-Based Outbound Route Filtering
•
Information About BGP Prefix-Based Outbound Route Filtering
•
How to Configure BGP Prefix-Based Outbound Route Filtering
Prerequisites for BGP Prefix-Based Outbound Route Filtering
BGP peering sessions must be up and running, and BGP ORF capabilities must be enabled on each participating router before a router can send or receive prefix-based ORF announcements and before the BGP Prefix-Based Outbound Route Filtering feature can be enabled.
Restrictions for BGP Prefix-Based Outbound Route Filtering
The BGP Prefix-Based Outbound Route Filtering feature does not support IP multicast routes.
Information About BGP Prefix-Based Outbound Route Filtering
To configure BGP prefix-based outbound route filtering, you must understand the following concepts:
•
BGP Prefix-Based Outbound Route Filtering Overview
•
Enabling BGP Prefix-Based Outbound Route Filtering
•
Benefits of BGP Prefix-Based Outbound Route Filtering
BGP Prefix-Based Outbound Route Filtering Overview
The BGP Prefix-Based Outbound Route Filtering feature uses Border Gateway Protocol (BGP) outbound route filter (ORF) send and receive capabilities to minimize the number of BGP updates that are sent between peer routers. The configuration of this feature can help reduce the amount of resources required for generating and processing routing updates by filtering out unwanted routing updates at the source. For example, this feature can be used to reduce the amount of processing required on a router that is not accepting full routes from a service provider network.
Enabling BGP Prefix-Based Outbound Route Filtering
The BGP Prefix-Based Outbound Route Filtering feature is enabled through the advertisement of ORF capabilities to peer routers. The advertisement of the ORF capability indicates that a BGP-speaking router will accept a prefix list from a neighbor and apply the prefix list to locally configured ORFs (if any exist). When this capability is enabled, the BGP speaker can install the inbound prefix list filter to the remote peer as an outbound filter, which reduces unwanted routing updates.
The BGP Prefix-Based Outbound Route Filtering feature can be configured with send, receive, or send and receive ORF capabilities. The local peer advertises the ORF capability in send mode. The remote peer receives the ORF capability in receive mode and applies the filter as an outbound policy. The local and remote peers exchange updates to maintain the ORF for each router. Updates are exchanged between peer routers by address family depending on the ORF prefix list capability that is advertised. The remote peer starts sending updates to the local peer after it receives a route refresh request or an ORF prefix list with immediate status. The BGP speaker will continue to apply the inbound prefix list to received updates after the speaker pushes the inbound prefix list to the remote peer.
Benefits of BGP Prefix-Based Outbound Route Filtering
The BGP Prefix-Based Outbound Route Filtering feature can limit the number of unwanted routing updates, which will reduce the amount of resources required for routing update generation and processing. This feature also reduces the amount of resources required to receive and discard routes that would otherwise be filtered out.
How to Configure BGP Prefix-Based Outbound Route Filtering
This section contains the following procedures:
•
Configuring BGP Prefix-Based Outbound Route Filtering
•
Verifying BGP Prefix-Based Outbound Route Filtering
Configuring BGP Prefix-Based Outbound Route Filtering
The BGP Prefix-Based Outbound Route Filtering supports prefix length matching, wild-card based prefix matching, and exact address prefix matching for address family support. This feature can be configured on a router to send or receive ORF capabilities with either the send or receive keywords. This feature can also be configured on a router to both send and receive ORF capabilities with the both keyword.
Prerequisites
BGP peering sessions must be up and running, and BGP ORF capabilities must be enabled on each participating router before a router can send or receive prefix-based ORF announcements and before the BGP Prefix-Based Outbound Route Filtering feature can be configured.
Restrictions
The BGP Prefix-Based Outbound Route Filtering feature does not support multicast.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
router bgp as-number
4.
address-family {ipv4 | ipv6 | vpnv4| [multicast | unicast | vrf {vrf-name}]
5.
neighbor ip-address remote-as as-number
6.
neighbor ip-address capability prefixlist-orf [send | receive | both]
7.
exit
DETAILED STEPS
Examples
The following example configures Router-A to advertise prefix-based ORF send capabilities to Router-B (172.16.1.2):
router bgp 100address-family ipv4 unicastneighbor 172.16.1.2 remote-as 200neighbor 172.16.1.2 capability orf prefix-list sendexitThe following example configures Router-B to advertise prefix-based ORF receive capabilities to Router-A (10.1.1.1). This example also creates the prefix filter to permit route from the 192.168.1.0 network.
router bgp 200address-family ipv4 unicastneighbor 10.1.1.1 remote-as 100neighbor 10.1.1.1 capability orf prefix-filter receiveneighbor 10.1.1.1 distribute-list 10 inexitaccess-list 10 permit 192.168.1.0 0.0.0.255!The following example configures Router-A to advertise both send and receive prefix-based ORF capabilities to Router-B (192.168.1.2) and to initiate an inbound soft reset with Router-B:
router bgp 100address-family ipv4 unicastneighbor 192.168.1.2 remote-as 200neighbor 192.168.1.2 capability orf prefix-list bothexitclear ip bgp 192.168.1.2 in prefix-filter!What to Do Next
You can verify that this feature is configured correctly with the show running-config and show ip bgp neighbors command. Go to the Verifying BGP Prefix-Based Outbound Route Filtering section for instructions and example output.
Verifying BGP Prefix-Based Outbound Route Filtering
To verify that the BGP Prefix-Based Outbound Route Filtering feature has been configured on peer routers, use the show ip bgp neighbor command in privileged EXEC mode. This command is used to display information about the TCP and BGP connections to neighbors. The status and type of ORF capabilities advertised and received is displayed in the output. Use the show running-config command in privileged EXEC mode to verify the local configuration of this feature.
See the following examples. The relevant lines of the output are in bold text.
•
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Send Mode
•
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Receive Mode
•
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Send and Receive Modes
Verifying BGP Prefix-Based Outbound Route Filtering Configured in Send Mode
The following example output from the show running-config privileged EXEC command shows that neighbor 192.168.20.72 is configured with the prefix-based ORF feature in send mode:
Router# show running-config | begin bgprouter bgp 1bgp log-neighbor-changesnetwork 10.0.0.0network 172.16.1.2neighbor 192.168.20.72 remote-as 2neighbor 192.168.20.72 capability orf prefix-list send!The following example output from the show ip bgp neighbors privileged EXEC command shows that neighbor 192.168.20.72 is configured with the prefix-based ORF feature in send mode:
Router# show ip bgp neighbors 192.168.20.72BGP neighbor is 192.168.20.72, remote AS 2, external linkBGP version 4, remote router ID 172.16.1.2BGP state = Established, up for 00:13:27Last read 00:00:27, hold time is 180, keepalive interval is 60 secondsNeighbor capabilities:Route refresh:advertised and received(new)Address family IPv4 Unicast:advertised and receivedReceived 36 messages, 0 notifications, 0 in queueSent 36 messages, 0 notifications, 0 in queueDefault minimum time between advertisement runs is 30 secondsFor address family:IPv4 UnicastBGP table version 13, neighbor version 13Index 1, Offset 0, Mask 0x2AF-dependant capabilities:Outbound Route Filter (ORF) type (128) Prefix-list:Send-mode:advertised, receivedReceive-mode:receivedRoute refresh request:received 4, sent 22 accepted prefixes consume 80 bytesPrefix advertised 8, suppressed 0, withdrawn 2Verifying BGP Prefix-Based Outbound Route Filtering Configured in Receive Mode
The following example output from the show running-config privileged EXEC command shows that neighbor 172.16.1.2 is configured with the prefix-based ORF feature in receive mode:
Router# show running-config | begin bgprouter bgp 1bgp log-neighbor-changesnetwork 10.0.0.0network 192.168.20.72neighbor 172.16.1.2 remote-as 2neighbor 172.16.1.2 capability orf prefix-list receive!The following example output from the show ip bgp neighbors privileged EXEC command shows that neighbor 172.16.1. 2 is configured with the prefix-based ORF feature in receive mode:
Router# show ip bgp neighbors 172.16.1.2BGP neighbor is 172.16.1.2, remote AS 2, external linkBGP version 4, remote router ID 192.168.20.72BGP state = Established, up for 00:02:47Last read 00:00:46, hold time is 180, keepalive interval is 60 secondsNeighbor capabilities:Route refresh:advertised and received(new)Address family IPv4 Unicast:advertised and receivedReceived 45 messages, 0 notifications, 0 in queueSent 44 messages, 0 notifications, 0 in queueDefault minimum time between advertisement runs is 30 secondsFor address family:IPv4 UnicastBGP table version 17, neighbor version 17Index 1, Offset 0, Mask 0x2AF-dependant capabilities:Outbound Route Filter (ORF) type (128) Prefix-list:Send-mode:receivedReceive-mode:advertised, receivedRoute refresh request:received 5, sent 22 accepted prefixes consume 80 bytesPrefix advertised 10, suppressed 0, withdrawn 2Verifying BGP Prefix-Based Outbound Route Filtering Configured in Send and Receive Modes
The following example output from the show running-config privileged EXEC command shows that neighbor 192.168.20.72 is configured with the prefix-based ORF feature in both send and receive modes:
Router# show running-config | begin bgprouter bgp 1bgp log-neighbor-changesnetwork 10.0.0.0network 172.16.1.2neighbor 192.168.20.72 remote-as 2neighbor 192.168.20.72 capability orf prefix-list both!The following example output from the show ip bgp neighbors privileged EXEC command shows that neighbor 192.168.20.72 is configured with the prefix-based ORF feature in both send and receive modes:
Router# show ip bgp neighbors 192.168.20.72BGP neighbor is 192.168.20.72, remote AS 2, external linkBGP version 4, remote router ID 172.16.1.2BGP state = Established, up for 00:00:09Last read 00:00:09, hold time is 180, keepalive interval is 60 secondsNeighbor capabilities:Route refresh:advertised and received(new)Address family IPv4 Unicast:advertised and receivedReceived 57 messages, 0 notifications, 0 in queueSent 56 messages, 0 notifications, 0 in queueDefault minimum time between advertisement runs is 30 secondsFor address family:IPv4 UnicastBGP table version 21, neighbor version 19Index 1, Offset 0, Mask 0x2AF-dependant capabilities:Outbound Route Filter (ORF) type (128) Prefix-list:Send-mode:advertised, receivedReceive-mode:advertised, receivedRoute refresh request:received 6, sent 32 accepted prefixes consume 80 bytesPrefix advertised 12, suppressed 0, withdrawn 2Additional References
The following sections provide references related to BGP Prefix-Based Outbound Route Filtering feature.
Related Documents
Related Topic Document TitleFor more information about IP access lists, refer to the IP address and services chapters in the IP configuration guide and command reference.
•
Cisco IOS IP Configuration Guide, Release 12.3
•
Cisco IOS IP Command Reference, Volume 1 of 4: Addressing and Services, Release 12.3
The BGP Prefix-Based Outbound Route Filtering feature is an extension of the BGP routing protocol. For more information about configuring BGP and configuring route summarization and filtering, refer to the "Configuring BGP" chapter of the Cisco IOS IP Configuration Guide and the Cisco IOS IP Command Reference.
•
Cisco IOS IP Configuration Guide, Release 12.3
•
Cisco IOS IP Command Reference, Volume 2 of 4: Routing Protocols, Release 12.3
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
Technical Assistance
Description LinkTechnical Assistance Center (TAC) home page, containing 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
TAC Home Page:
http://www.cisco.com/public/support/tac/home.shtml
BGP Support Page:
http://www.cisco.com/cgi-bin/Support/browse/psp_view.pl?p=Internetworking:BGP
Command Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS command reference publications.
New Commands
•
clear ip bgp in prefix-filter
Modified Commands
clear ip bgp in prefix-filter
To clear a BGP outbound route filter (ORF) and initiate an inbound soft reset, use the clear ip bgp in prefix-filter command in privileged EXEC mode.
clear ip bgp {ip-address | *} in prefix filter
Syntax Description
*
Clears all ORFs and resets all inbound BGP sessions.
ip-address
(Optional) IP address of the network about which to clear dampening information.
Defaults
The prefix-filter keyword will be ignored and a normal inbound route refresh will be performed if the ORF capability has not been received or the send capability has not been enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is used to push out the existing ORF prefix list so that a new route refresh will be received from a neighbor. When this command is used without the prefix-filter keyword, a normal route refresh is performed. This command should be used when inbound routing policy changes other than a prefix list filter occur, such as a route map change.
Examples
The following example clears BGP ORFs for the 192.168.0.1 neighbor initiate an initiate an inbound soft reset:
Router# clear ip bgp 192.168.0.1 in prefix-filterRelated Commands
Command DescriptionAdvertises ORF capabilities to peer routers.
Displays information about the TCP and BGP connections to neighbors.
neighbor orf prefix-filter
To advertise outbound route filter (ORF) capabilities to a peer router, use the neighbor orf prefix-filter command in address family or router configuration mode. To disable ORF capabilities, use the no form of this command.
neighbor {ip-address} [capability] orf prefix-filter [both | receive | send]
no neighbor {ip-address} [capability] orf prefix-filter [both | receive | send]
Syntax Description
Defaults
Disabled
Command Modes
Address family configuration
Router configuration
Command History
Usage Guidelines
The neighbor prefix-filter command is used to reduce the number of BGP prefixes that a BGP speaker sends or receives from a peer router based on prefix filtering.
In most configurations, this command will be used to advertise both send and receive ORF capabilities with the both keyword. However this feature can be configured in one direction between two routers with one router configured to send ORF capabilities and another router configured to receive ORF capabilities from the first router.
Examples
The following example configures the router to advertise ORF send capabilities to neighbor 172.16.1.2:
router bgp 100neighbor 176.16.1.2 capability orf prefix-filter sendThe following example configures the router to advertise ORF receive capabilities to neighbor 10.1.1.1:
router bgp 100neighbor 10.1.1.1 capability orf prefix-filter receiveThe following example configures the router to advertise ORF receive capabilities to neighbor 192.168.1.2:
router bgp 100neighbor 192.168.1.2 capability orf prefix-filter both
Related Commands
Command DescriptionDistributes BGP neighbor information as specified in an access list.
Distributes BGP neighbor information as specified in a prefix list.
show ip bgp neighbors
To display information about the TCP and Border Gateway Protocol (BGP) connections to neighbors, use the show ip bgp neighbors command in EXEC mode.
show ip bgp neighbors [neighbor-address] [received-routes | routes | advertised-routes | {paths regexp} | dampened-routes] [received prefix-filter]
Syntax Description
Command Modes
EXEC
Command History
Release Modification10.0
This command was introduced.
11.2
The received-routes keyword was added.
12.2(4)T
12.2(14S
12.0(22)S
The received prefix-filter keyword was added.
Examples
The following is sample output from the show ip bgp neighbors command in privileged EXEC mode:
Router# show ip bgp neighbors 172.16.232.178BGP neighbor is 172.16.232.178, remote AS 35, external linkBGP version 4, remote router ID 192.168.3.3BGP state = Established, up for 1w1dLast read 00:00:53, hold time is 180, keepalive interval is 60 secondsNeighbor capabilities:Route refresh: advertised and receivedAddress family IPv4 Unicast: advertised and receivedAddress family IPv4 Multicast: advertised and receivedReceived 12519 messages, 0 notifications, 0 in queueSent 12523 messages, 0 notifications, 0 in queueRoute refresh request: received 0, sent 0Minimum time between advertisement runs is 30 secondsFor address family: IPv4 UnicastBGP table version 5, neighbor version 5Index 1, Offset 0, Mask 0x2Community attribute sent to this neighborInbound path policy configuredOutbound path policy configuredRoute map for incoming advertisements is uni-inRoute map for outgoing advertisements is uni-out3 accepted prefixes consume 108 bytesPrefix advertised 6, suppressed 0, withdrawn 0For address family: IPv4 MulticastBGP table version 5, neighbor version 5Index 1, Offset 0, Mask 0x2Inbound path policy configuredOutbound path policy configuredRoute map for incoming advertisements is mul-inRoute map for outgoing advertisements is mul-out3 accepted prefixes consume 108 bytesPrefix advertised 6, suppressed 0, withdrawn 0Connections established 2; dropped 1Last reset 1w1d, due to Peer closed the sessionConnection state is ESTAB, I/O status: 1, unread input bytes: 0Local host: 172.16.232.178, Local port: 179Foreign host: 172.16.232.179, Foreign port: 11002Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)Event Timers (current time is 0x2CF49CF8):Timer Starts Wakeups NextRetrans 12518 0 0x0TimeWait 0 0 0x0AckHold 12514 12281 0x0SendWnd 0 0 0x0KeepAlive 0 0 0x0GiveUp 0 0 0x0PmtuAger 0 0 0x0DeadWait 0 0 0x0iss: 273358651 snduna: 273596614 sndnxt: 273596614 sndwnd: 15434irs: 190480283 rcvnxt: 190718186 rcvwnd: 15491 delrcvwnd: 893SRTT: 300 ms, RTTO: 607 ms, RTV: 3 ms, KRTT: 0 msminRTT: 0 ms, maxRTT: 300 ms, ACK hold: 200 msFlags: passive open, nagle, gen tcbsDatagrams (max data segment is 1460 bytes):Rcvd: 24889 (out of order: 0), with data: 12515, total data bytes: 237921Sent: 24963 (retransmit: 0), with data: 12518, total data bytes: 237981Table 1 describes the significant fields shown in the display.
The following is sample output from the show ip bgp neighbors command with the advertised-routes keyword in privileged EXEC mode:
Router# show ip bgp neighbors 172.16.232.178 advertised-routesBGP table version is 27, local router ID is 172.16.232.181Status codes: s suppressed, d damped, h history, * valid, > best, i - internalOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i110.0.0.0 172.16.232.179 0 100 0 ?*> 200.2.2.0 0.0.0.0 0 32768 iThe following is sample output from the show ip bgp neighbors command with the routes keyword in privileged EXEC mode:
Router# show ip bgp neighbors 172.16.232.178 routesBGP table version is 27, local router ID is 172.16.232.181Status codes: s suppressed, d damped, h history, * valid, > best, i - internalOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*> 10.0.0.0 172.16.232.178 40 0 10 ?*> 20.0.0.0 172.16.232.178 40 0 10 ?Table 2 describes the significant fields shown in the displays.
The following is sample output from the show ip bgp neighbors command with the paths keyword in privileged EXEC mode:
Router# show ip bgp neighbors 171.69.232.178 paths ^10Address Refcount Metric Path0x60E577B0 2 40 10 ?Table 3 describes the significant fields shown in the display.
The following is sample output from the show ip bgp neighbors command with the received prefix-filter keyword in privileged EXEC mode:
Router# show ip bgp neighbor 192.168.20.72 received prefix-filterAddress family:IPv4 Unicastip prefix-list 192.168.20.72:1 entriesseq 5 deny 10.0.0.0/8 le 32Table 4 describes the significant fields shown in the display.
Table 4 show ip bgp neighbors paths Field Descriptions
Field DescriptionAddress family:
The configured address family mode.
ip prefix-list ...
The configured prefix list for the specified neighbor.
