![]() |
IP Routing: OSPF Configuration Guide, Cisco IOS Release 15S
|
||||||||||||
OSPF Inbound Filtering Using Route Maps with a Distribute List
![]() |
|||||||||||||
|
Contents
OSPF Inbound Filtering Using Route Maps with a Distribute ListLast Updated: November 26, 2012
The OSPF Inbound Filtering Using Route Maps with a Distribute List feature allows users to define a route map to prevent Open Shortest Path First (OSPF) routes from being added to the routing table. In the route map, the user can match on any attribute of the OSPF route.
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. Prerequisites for OSPF Inbound Filtering Using Route Maps with a Distribute ListIt is presumed that you have OSPF configured in your network. Information About OSPF Inbound Filtering Using Route Maps with a Distribute ListUsers can define a route map to prevent OSPF routes from being added to the routing table. This filtering happens at the moment when OSPF is installing the route in the routing table. This feature has no effect on link-state advertisement (LSA) flooding. In the route map, the user can match on any attribute of the OSPF route. That is, the route map could be based on the following match options:
This feature can be useful during redistribution if the user tags prefixes when they get redistributed on Autonomous System Boundary Routers (ASBRs) and later uses the tag to filter the prefixes from being installed in the routing table on other routers. Filtering Based on Route TagUsers can assign tags to external routes when they are redistributed to OSPF. Then the user can deny or permit those routes in the OSPF domain by identifying that tag in the route-map and distribute-list in commands. Filtering Based on Route TypeIn OSPF, the external routes could be Type 1 or Type 2. Users can create route maps to match either Type 1 or Type 2 and then use the distribute-list in command to filter certain prefixes. Also, route maps can identify internal routes (interarea and intra-area) and then those routes can be filtered. Filtering Based on Route SourceWhen a match is done on the route source, the route source represents the OSPF Router ID of the LSA originator of the LSA in which the prefix is advertised. Filtering Based on InterfaceWhen a match is done on the interface, the interface represents the outgoing interface for the route that OSPF is trying to install in the routing table. Filtering Based on Next HopWhen a match is done on the next hop, the next hop represents the next hop for the route that OSPF is trying to install in the routing table. How to Configure OSPF Inbound Filtering Using Route MapsConfiguring OSPF Route Map-Based FilteringSUMMARY STEPS
DETAILED STEPS Configuration Examples for OSPF Inbound Filtering Using Route Maps with a Distribute ListExample OSPF Route Map-Based FilteringIn this example, OSPF external LSAs have a tag. The value of the tag is examined before the prefix is installed in the routing table. All OSPF external prefixes that have the tag value of 777 are filtered (prevented from being installed in the routing table). The permit statement with sequence number 20 has no match conditions, and there are no other route-map statements after sequence number 20, so all other conditions are permitted. route-map tag-filter deny 10 match tag 777 route-map tag-filter permit 20 ! router ospf 1 router-id 10.0.0.2 log-adjacency-changes network 172.16.2.1 0.0.0.255 area 0 distribute-list route-map tag-filter in Additional ReferencesMIBsTechnical Assistance
Feature Information for OSPF Inbound Filtering Using Route Maps with a Distribute ListThe 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.
|
||||||||||||
|
|