Feedback
|
Table Of Contents
EIGRP Support for Route Map Filtering
Information About EIGRP Support for Route Map Filtering
How to Configure EIGRP Support for Route Map Filtering
Setting EIGRP Tags Using a Route Map for Autonomous System Configurations
Setting EIGRP Tags Using a Route Map for Named Configurations
Configuration Examples for EIGRP Support for Route Map Filtering
Example: Setting EIGRP Tags Using a Route Map—Autonomous System Configuration Examples
Example: Setting EIGRP Tags Using a Route Map—Named Configuration Examples
Feature Information for EIGRP Support for Route Map Filtering
EIGRP Support for Route Map Filtering
First Published: May 17, 2004Last Updated: November 25, 2009The EIGRP Support for Route Map Filtering feature enables Enhanced Interior Gateway Routing Protocol (EIGRP) to interoperate with other protocols to leverage additional routing functionality by filtering inbound and outbound traffic based on complex route map options. Several extended filtering options are introduced to provide EIGRP-specific match choices.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for EIGRP Support for Route Map Filtering" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Information About EIGRP Support for Route Map Filtering
•
How to Configure EIGRP Support for Route Map Filtering
•
Configuration Examples for EIGRP Support for Route Map Filtering
•
Feature Information for EIGRP Support for Route Map Filtering
Information About EIGRP Support for Route Map Filtering
EIGRP Route Map Support
EIGRP support for route map filtering enables EIGRP to interoperate with other protocols by filtering inbound and outbound traffic based on route map options. Additional EIGRP-specific match choices are available to allow flexibility in fine-tuning EIGRP network operations.
EIGRP supports the route map filtering capability that exists for other routing protocols to filter routes being redistributed into their protocol. For more details about understanding and configuring route maps, see the "Enabling Policy Routing" section of the "Configuring IP Routing Protocol-Independent Features" module of the Cisco IOS XE IP Routing: Protocol-Independent Configuration Guide, Release 2.
Match options allow EIGRP to filter internal and external routes based on source protocols, to match a metric against a range, and to match on an external protocol metric.
EIGRP can be configured to filter traffic using a route map and the redistribute or distribute-list command. Using a route map with the redistribute command allows routes that are redistributed from the routing table to be filtered with a route map before being admitted into an EIGRP topology table. Routes that are dynamically received from, or advertised to, EIGRP peers can be filtered by adding a route map option to the distribute-list command.
A route map may be configured with both the redistribute and the distribute-list commands in the same routing process. When a route map is used with a distribute-list command that is configured for inbound or outbound filtering, route packets that are learned from or advertised to EIGRP peers can be processed with the route map to provide better control of route selection during the route exchange process. Redistribution serves as a mechanism to import routes into the EIGRP topology table from a routing table. A route map configured with the redistribute command adds flexibility to the redistribution capability and results in a more specific redistributed route selection.
The use of route maps to filter traffic is the same for both autonomous-system configurations and named configurations. See the "Configuring EIGRP" module for more information about autonomous system and named configurations.
Demands for EIGRP to interoperate with other protocols and flexibility in fine-tuning network operation necessitate the capability to filter traffic using a route map.
How to Configure EIGRP Support for Route Map Filtering
•
Setting EIGRP Tags Using a Route Map for Autonomous System Configurations (required)
•
Setting EIGRP Tags Using a Route Map for Named Configurations (optional)
Setting EIGRP Tags Using a Route Map for Autonomous System Configurations
Perform this task to set EIGRP tags for autonomous system configurations using a route map. The EIGRP metrics used for filtering are configured within a route map. The first match clause defines EIGRP routes that contain an external protocol metric between 400 and 600 inclusive; the second match clause defines EIGRP external routes that match a source protocol of BGP and the autonomous system 45000. When the two match clauses are true, a tag value of the destination routing protocol is set to 5. This route map can be used with the distribute-list command, see the "Example: Setting EIGRP Tags Using a Route Map—Autonomous System Configuration Examples" section for an example configuration.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
route-map map-tag [permit | deny] [sequence-number]
4.
match metric {metric-value | external metric-value} [+- deviation-number]
5.
match source-protocol source-protocol [autonomous-system-number]
6.
set tag tag-value
7.
exit
8.
router eigrp as-number
9.
network ip-address
10.
distribute-list route-map map-tag in
DETAILED STEPS
Setting EIGRP Tags Using a Route Map for Named Configurations
Perform this task to set EIGRP tags for named configurations using a route map. The EIGRP metrics used for filtering are configured within a route map. The first match clause defines EIGRP routes that contain an external protocol metric between 400 and 600 inclusive; the second match clause defines EIGRP external routes that match a source protocol of BGP and the autonomous system 45000. When the two match clauses are true, a tag value of the destination routing protocol is set to 5. This route map can be used with the distribute-list command, see the "Example: Setting EIGRP Tags Using a Route Map—Named Configuration Examples" section for an example configuration.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
route-map map-tag [permit | deny] [sequence-number]
4.
set metric bandwidth delay reliability loading mtu
5.
match ip route-source {access-list-number | access-list-name} [...access-list-number | ...access-list-name]
6.
match metric {metric-value | external metric-value} [+- deviation-number]
7.
match source-protocol source-protocol [autonomous-system-number]
8.
set tag source-protocol [autonomous-system-number]
9.
exit
10.
router eigrp virtual-instance-name
11.
address-family ipv4 [multicast] [unicast] [vrf vrf-name] autonomous-system autonomous-system-number
or
address-family ipv6 [unicast] [vrf vrf-name] autonomous-system autonomous-system-number
12.
network ip-address [wildcard-mask]
13.
af-interface {default | interface-type interface-number}
14.
next-hop-self eigrp
15.
exit-af-interface
16.
topology {base | topology-name tid number}
17.
distribute-list route-map map-tag in
DETAILED STEPS
Configuration Examples for EIGRP Support for Route Map Filtering
•
Example: Setting EIGRP Tags Using a Route Map—Autonomous System Configuration Examples
•
Example: Setting EIGRP Tags Using a Route Map—Named Configuration Examples
Example: Setting EIGRP Tags Using a Route Map—Autonomous System Configuration Examples
The following example shows how to configure a route map to match an EIGRP external protocol metric route with an allowable deviation of 100, a source protocol of BGP, and an autonomous system 45000. When the two match clauses are true, the tag value of the destination routing protocol is set to 5. The route map is used to distribute incoming packets for an EIGRP process.
Router(config)# route-map metric-rangeRouter(config-route-map)# match metric external 500 +- 100Router(config-route-map)# match source-protocol bgp 45000Router(config-route-map)# set tag 5Router(config-route-map)# exitRouter(config)# router eigrp 1Router(config-router)# network 172.16.0.0Router(config-router)# distribute-list route-map metric_range inThe following example shows how to configure a route map to match EIGRP routes with a metric of 110, 200, or an inclusive range of 700 to 800. When the match clause is true, the tag value of the destination routing protocol is set to 10. The route map is used to redistribute EIGRP packets.
Router(config)# route-map metric-eigrpRouter(config-route-map)# match metric 110 200 750 +- 50Router(config-route-map)# set tag 10Router(config-route-map)# exitRouter(config)# router eigrp 1Router(config-router)# network 172.21.1.0/24Router(config-router)# redistribute eigrp route-map metric-eigrpExample: Setting EIGRP Tags Using a Route Map—Named Configuration Examples
The following example shows how to configure a route map to match an EIGRP external protocol metric route with an allowable deviation of 100, a source protocol of BGP, and an autonomous system 45000. When the two match clauses are true, the tag value of the destination routing protocol is set to 5. The route map is used to distribute incoming packets for an EIGRP process.
Router(config)# route-map metric_rangeRouter(config-route-map)# match metric external 500 +- 100Router(config-route-map)# match source-protocol bgp 45000Router(config-route-map)# set tag 5Router(config-route-map)# exitRouter(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 autonomous-system 45000
Router(config-router-af)# network 172.21.1.0/24Router(config-router-af)# topology baseRouter(config-router-af-topology)# distribute-list route-map metric_range inThe following example shows how to configure a route map to match EIGRP routes with a metric of 110, 200, or an inclusive range of 700 to 800. When the match clause is true, the tag value of the destination routing protocol is set to 10. The route map is used to redistribute EIGRP packets.
Router(config)# route-map metric_eigrpRouter(config-route-map)# match metric 110 200 750 +- 50Router(config-route-map)# set tag 10Router(config-route-map)# exitRouter(config)# router eigrp virtual-nameRouter(config-router)# address-family ipv4 autonomous-system 45000
Router(config-router-af)# network 172.21.1.0/24Router(config-router-af)# topology baseRouter(config-router-af-topology)# distribute-list route-map metric-range inAdditional References
Related Documents
Related Topic Document TitleCisco IOS commands
EIGRP overview and configuration
EIGRP commands including syntax, usage guidelines, and examples
Standards
MIBs
MIB MIBs LinkNone
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for EIGRP Support for Route Map Filtering
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2004-2010 Cisco Systems, Inc. All rights reserved.
Feedback