![]() |
IP Routing: ODR Configuration Guide Cisco IOS XE Release 3S
|
||||||||||||||||||||
Configuring On-Demand Routing
![]() |
|||||||||||||||||||||
Contents
Configuring On-Demand RoutingLast Updated: July 28, 2011
The On-Demand Routing feature provides IP routing for stub sites, with minimum cost. The cost of a general, dynamic routing protocol is avoided without incurring the configuration and management burden of static routing.
Finding Feature InformationYour 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 Table at the end of this document. 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. Restrictions for Configuring On-Demand RoutingNo IP routing protocol can be configured on the stub router. Information About On-Demand RoutingBenefits of On-Demand RoutingThis module describes how to configure On-Demand Routing (ODR). The ODR feature provides IP routing for stub sites, with minimum cost. The cost of a general, dynamic routing protocol is avoided without incurring the configuration and management burden of static routing. Stub NetworksA stub router can be considered a spoke router in a hub-and-spoke network topology--as shown in the figure below--where the only router to which the spoke is adjacent is the hub router. In such a network topology, the IP routing information required to represent this topology is fairly simple. These stub routers commonly have a WAN connection to the hub router, and a small number of LAN network segments (stub networks) are directly connected to the stub router. These stub networks might consist only of end systems and the stub router, and therefore do not require the stub router to learn any dynamic IP routing information. Overview of On-Demand RoutingODR allows you to easily install IP stub networks where the hubs dynamically maintain routes to the stub networks. This installation is accomplished without requiring the configuration of an IP routing protocol on the stubs. In fact, from the standpoint of ODR, a router is automatically considered to be a stub when no IP routing protocols have been configured. A stub router that supports the ODR feature advertises IP prefixes corresponding to the IP networks configured on all directly connected interfaces. If the interface has multiple logical IP networks configured, only the primary IP network is advertised through ODR. Because ODR advertises IP prefixes and not simply IP network numbers, ODR is able to carry variable-length subnet mask (VLSM) information. Once ODR is enabled on a hub router, the hub router begins installing stub network routes in the IP forwarding table. The hub router also can be configured to redistribute these routes into any configured dynamic IP routing protocols. ODR uses the Cisco Discovery Protocol to carry minimal routing information between the hub and stub routers. The stub routers send IP prefixes to the hub router. The hub router provides default route information to the stub routers, thereby eliminating the need to configure a default route on each stub router. How to Configure On-Demand Routing
Enabling ODROnce ODR is enabled on a hub router, the hub router begins installing stub network routes in the IP forwarding table. The hub router also can be configured to redistribute these routes into any configured dynamic IP routing protocols. To enable ODR on a hub router, perform the steps in this task. DETAILED STEPS Disabling the Propagation of ODR Stub Routing InformationODR uses Cisco Discovery Protocol to carry minimal routing information between the hub and stub routers, allowing stub routers to send IP prefixes to the hub router. Perform the steps in this task to disable the propagation of ODR stub routing information by disabling CDP. DETAILED STEPS Disabling the Propagation of ODR Stub Routing Information on a Specified InterfaceOn stub routers that support the ODR feature, the stub router advertises IP prefixes corresponding to the IP networks configured on all directly connected interfaces. Perform the steps in this task to disable the propagation of ODR stub routing information on a specified interface. DETAILED STEPS Filtering ODR InformationThe hub router will attempt to populate the IP routing table with ODR routes as they are learned dynamically from stub routers. The IP next hop for these routes is the IP address of the neighboring router as advertised through Cisco Discovery Protocol. Use IP filtering to limit the network prefixes that the hub router will permit to be learned dynamically through ODR. In this example, the ACL filters the following Class A network prefixes: access-list 101 permit 10.48.0.3 access-list 101 deny 10.48.0.0 0.0.255.255 access-list 101 permit 10.0.0.0 0.255.255.255 interface gigabitethernet 0/0/0 ip access-group 2 in To filter ODR information, perform the steps in this task. DETAILED STEPS Redistributing ODR Information into the Dynamic Routing Protocol of the HubThe exact command syntax needed to redistribute ODR information into the dynamic routing protocol of the hub depends upon the routing protocol into which ODR is being redistributed. See the "Redistributing Routing Information" section in the "Configuring IP Routing Protocol-Independent Features" module for further information. Reconfiguring Cisco Discovery Protocol or ODR TimersBy default, Cisco Discovery Protocol sends updates every 60 seconds. This update interval may not be frequent enough to provide fast reconvergence of IP routes on the hub router side of the network. A faster reconvergence rate may be necessary if the stub connects to one of several hub routers via asynchronous interfaces such as modem lines. ODR expects to receive periodic Cisco Discovery Protocol updates containing IP prefix information. When ODR fails to receive such updates for routes that it has installed in the routing table, these ODR routes are first marked invalid and eventually removed from the routing table. (By default, ODR routes are marked invalid after 180 seconds and are removed from the routing table after 240 seconds.) These defaults are based on the default Cisco Discovery Protocol update interval. Configuration changes made to either the Cisco Discovery Protocol or ODR timers should be reflected through changes made to both. To reconfigure Cisco Discovery Protocol or ODR timers, perform the steps in this task. DETAILED STEPS Using Dialer Map Statements to Direct Cisco Discovery Protocol Broadcast PacketsFor interfaces that specify dialer mappings, Cisco Discovery Protocol packets will make use of dialer map configuration statements that pertain to the IP protocol. Because Cisco Discovery Protocol packets are always broadcast packets, these dialer map statements must handle broadcast packets, typically through use of the dialer map command with the broadcast keyword. The dialer string command in interface configuration mode may also be used. On dial-on-demand (DDR) routing interfaces, certain kinds of packets can be classified as interesting. These interesting packets can cause a DDR connection to be made or cause the idle timer of a DDR interface to be reset. For the purposes of DDR classification, Cisco Discovery Protocol packets are considered uninteresting. This classification occurs even while Cisco Discovery Protocol is making use of dialer map statements for IP, where IP packets are classified as interesting. The following task describes how to use dialer map statements to direct Cisco Discovery Protocol broadcast packets. or dialer string dial-string [: isdn-subaddress]
DETAILED STEPS Configuration Examples for On-Demand RoutingEnabling ODR and Filtering ODR Information ExampleThe following example shows how to enable ODR on a Cisco router and enable filtering of ODR information. The configuration example for filtering ODR information causes the hub router to accept only advertisements for IP prefixes about (or subnets of) the Class C network 192.168.1.0:
Router(config)# access-list 101 permit ip host 10.0.0.1 192.168.1.0 0.0.0.255
Router(config)# access-list 101 permit ip 10.0.10.2 255.0.0.0 192.168.2.0 0.0.0.255
Router(config)# router odr
Router(config-router)# distribute-list 101 in
Router(config-router)# end
Additional ReferencesRelated Documents
MIBsTechnical Assistance
Feature Information for Configuring On-Demand RoutingThe 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 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. |
|||||||||||||||||||||
|
|