EIGRP Route Tag Enhancements
|
|||||||||||||||
Contents
EIGRP Route Tag EnhancementsLast Updated: July 26, 2012
The EIGRP Route Tag Enhancements feature enables you to specify and display route tags in dotted-decimal format, filter routes using the route tag value with wildcard mask, and set a default route tag for all internal Enhanced Interior Gateway Routing Protocol (EIGRP) routes. Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About EIGRP Route Tag EnhancementsEIGRP Route Tag Enhancements OverviewA route tag is a 32-bit value attached to routes. Route tags are used to filter routes and apply administrative policies, such as redistribution and route summarization, to tagged routes. You can tag routes within a route map by using the set tag command. You can match tagged routes and apply administrative policies to tagged routes within a route map by using the match tag or match tag list command. The match tag list command is used to match a list of route tags. Prior to the EIGRP Route Tag Enhancements feature, EIGRP routes could only be tagged using plain decimals (range: 1 to 4294967295). This feature enables users to specify and display route tag values as dotted decimals (range: 0.0.0.0 to 255.255.255.255), similar to the format used by IPv4 addresses. This enhancement is intended to simplify the use of route tags as users can now filter routes by using the route tag wildcard mask. This feature also allows you to configure a default route tag for all internal EIGRP routes without using route maps. Use the eigrp default-route-tag command in address family configuration mode to configure a default route tag for internal EIGRP routes. How to Configure EIGRP Route Tag Enhancements
Enabling Dotted-Decimal Notation for Route TagsPerform this task to enable route tags to be displayed as dotted decimals in show commands, irrespective of whether or not the tags were configured as dotted decimals. DETAILED STEPS Setting a Route Tag in a Route MapSUMMARY STEPS
DETAILED STEPS Matching a Route Tag in a Route MapSUMMARY STEPS
DETAILED STEPS Creating a Route Tag ListSUMMARY STEPS
DETAILED STEPS Matching a Route Tag List Route tag lists are used in route maps to match routes based on conditions specified in the route tag lists. Multiple route tag and mask pair sequences can be configured to permit or deny any condition for a list of route tags.
SUMMARY STEPS
DETAILED STEPS Setting a Default Route Tag for EIGRP Internal RoutesPerform this task to set a default route tag for all internal EIGRP routes without using a route map. Default route tags are supported only in EIGRP named mode configurations. DETAILED STEPS Configuration Examples for EIGRP Route Tag Enhancements
Example: Enabling Dotted-Decimal Notation for Route TagsThe following example shows how to enable the display of route tags in dotted-decimal format by using the route-tag notation command. If you do not configure the route-tag notation command, route tags will be displayed as plain decimals in show commands even if the route tags were configured as dotted decimals. When you configure the route-tag notation command, route tags will be displayed as dotted decimals even if the route tags were configured as plain decimals. Device# configure terminal Device(config)# route-tag notation dotted-decimal Example: Setting a Route TagThe following example shows how to redistribute EIGRP routes into RIP and RIP routes into EIGRP by setting tags for routes within route maps: Device(config)# route-map eigrp-to-rip Device(config-route-map)# set tag 10.10.10.10 Device(config-route-map)# exit Device(config)# route-map rip-to-eigrp Device(config-route-map)# set tag 20.20.20.20 Device(config-route-map)# exit Device(config)# router rip Device(config-router)# redistribute eigrp 7 route-map eigrp-to-rip metric 5 Device(config-router)# exit Device(config)# router eigrp name Device(config-router)# address-family ipv4 autonomous-system 10 Device(config-router-af)# topology base Device(config-router-af-topology)# redistribute rip route-map rip-to-eigrp 2 2 2 2 2 Device(config-router-af-topology)# end Example: Matching a Route TagThe following example shows how to redistribute EIGRP routes with a route tag value of 10.10.10.10 into a RIP domain: Device(config)# route-map eigrp-to-rip Device(config-route-map)# match tag 10.10.10.10 Device(config-route-map)# exit Device(config)# router rip Device(config-router)# redistribute eigrp 7 route-map eigrp-to-rip 5 Device(config-router)# end Example: Configuring a Route Tag ListThe following example shows how to configure a route tag list named TAG with various criteria for filtering routes. Route maps will use this list to match routes based on the criteria specified in the list. Route tag lists can accept route tags and wild card masks. Device(config)# route-tag list TAG permit 1.1.1.1 0.0.0.1 Device(config)# route-tag list TAG seq 3 permit 2.2.2.2 0.0.0.3 Device(config)# route-tag list TAG seq 10 permit 3.3.3.3 0.0.0.7 Device(config)# route-tag list TAG seq 15 5.5.5.5 0.0.0.31 Device(config)# route-tag list TAG seq 20 deny 4.4.4.4 0.0.0.4 Example: Matching a Route Tag ListThe following example shows how to use a route map to filter routes that match a specific route tag list. A single list can have multiple match criteria. All criteria must match before the route can be filtered. This example shows how to configure a route tag list named List1 in a route map and use the match tag list command to filter routes that match the criteria listed in the route tag list. Device(config)# route-tag list List1 permit 10.10.10.0 0.0.0.7 Device(config)# route-map to-ospf Device(config-route-map)# match tag list List1 Device(config-route-map)# exit Device(config)# router ospf 10 Device(config-router)# redistribute eigrp 7 route-map to-ospf metric 20 Device(config-router)# end Example: Setting a Default Route TagThe following example shows how to set a default route tag for all internal EIGRP routes without using a route map. Default route tags are supported only in EIGRP named configurations. Device(config)# router eigrp name Device(config-router)# address-family ipv4 unicast autonomous-system 1 Device(config-router-af)# eigrp default-route-tag 10.10.10.10 Additional ReferencesTechnical Assistance
Feature Information for EIGRP Route Tag EnhancementsThe following table provides release information about the feature or features described in this module. This table 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. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R) 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. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||