<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Modify OSPF routes based on source criteria and destination  in Routing and SD-WAN</title>
    <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972096#M79997</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edison,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tried using PBR; unfortunately, matching on ip next-hop can only be used for redistribution.  PBR can only use match ip and match length.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of this I was wondering if I could analyze OSPF routes, modify them based on criteria in a route map, and then redistribute the changes back into the same instance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am also open to other suggestions of how this may be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Apr 2008 18:45:17 GMT</pubDate>
    <dc:creator>deschete</dc:creator>
    <dc:date>2008-04-16T18:45:17Z</dc:date>
    <item>
      <title>Modify OSPF routes based on source criteria and destination interface</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972094#M79995</link>
      <description>&lt;P&gt;Hopefully someone here can assist with a problem I've been having for a few months now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We run OSPF.  On two of our routers, I would like to have the router analyze the traffic and decide which of two paths to take based on two things:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) The source IP and precdence of the packet,  and&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) The next-hop interface of the packet once the router decides where it will be routed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way to have the router examine a list of criteria and then the routing table to find matches, then alter the next-hop route for entries that match this criteria?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am also open to other suggestions of how to achieve this.&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2019 05:35:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972094#M79995</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2019-03-04T05:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972095#M79996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can't do this with destination-based routing  protocols such as OSPF or EIGRP, for that matter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Source-based routing is implemented with Policy-Based Routing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please have a read and come back if you have any questions:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/ios/12_4/ip_route/configuration/guide/piconfig.html#wp1001398" target="_blank"&gt;http://www.cisco.com/en/US/docs/ios/12_4/ip_route/configuration/guide/piconfig.html#wp1001398&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;__&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edison.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 18:40:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972095#M79996</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2008-04-16T18:40:27Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972096#M79997</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edison,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tried using PBR; unfortunately, matching on ip next-hop can only be used for redistribution.  PBR can only use match ip and match length.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of this I was wondering if I could analyze OSPF routes, modify them based on criteria in a route map, and then redistribute the changes back into the same instance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am also open to other suggestions of how this may be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 18:45:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972096#M79997</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2008-04-16T18:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972097#M79998</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In OSPF you can't redistribute from OSPF back into OSPF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please give us a sample scenario that we can follow? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a hard time understanding what exactly you want to accomplish.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With PBR, you can change default routing behavior based on the source parameters. From the main posts, it seems that what you wanted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 18:49:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972097#M79998</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2008-04-16T18:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972098#M79999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure, let me try to make it a little more clear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two routers in two cities.  Between these two routers there are two connections.  One is intended for general traffic and is configured to participate in OSPF.  The second link is for traffic with priority 5 from a select list of IP addresses, and this link is not participating in OSPF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here's where the problem comes in - there are multiple T1 connections coming in to both of these routers also.  This means that technically speaking, there are multiple "inbound" interfaces on the router.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I classify based on source or priority with PBR, I may send traffic that simply needs to go out of another T1 on the router across the WAN to the second router, where it will be sent back and then go over the neighboring T1!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So in short, the easiest way to solve this particular problem would be to analyze all traffic destined to go out of the primary uplink to the other city's router.  If it matches a set of criteria, it is re-routed over the secondary link for priority traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can try to explain in greater detail if this is still unclear.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 18:56:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972098#M79999</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2008-04-16T18:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972099#M80000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want to force traffic (bi-directionally) via a specified T1 based on certain criteria, then you need PBR on both routers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 19:03:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972099#M80000</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2008-04-16T19:03:46Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972100#M80001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem is that the need to send the traffic hinges on if it was already destined to go over another interface.  Because PBR is processed before the routing table is processed, I can't find a way to do this with PBR.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 19:08:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972100#M80001</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2008-04-16T19:08:01Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972101#M80002</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You lost me there, sorry - traffic hinges ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you pull up a quick visio diagram and explain the traffic pattern that you want out of this task ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Apr 2008 19:45:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972101#M80002</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2008-04-16T19:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972102#M80003</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Edit: see next post, I can't attach to an edit...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2008 19:45:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972102#M80003</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2008-04-17T19:45:39Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972103#M80004</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Attached is a drawing showing the situation that I'm describing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Item #4 should read "after an inefficient trip through R1," not R4 as on this diagram.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Apr 2008 19:49:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972103#M80004</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2008-04-17T19:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972104#M80005</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone have any ideas about this one?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2008 12:54:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972104#M80005</guid>
      <dc:creator>deschete</dc:creator>
      <dc:date>2008-04-21T12:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: Modify OSPF routes based on source criteria and destination</title>
      <link>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972105#M80006</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Based on your diagram, I believe your requirement can't be accomplished.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Apr 2008 13:01:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/routing-and-sd-wan/modify-ospf-routes-based-on-source-criteria-and-destination/m-p/972105#M80006</guid>
      <dc:creator>Edison Ortiz</dc:creator>
      <dc:date>2008-04-21T13:01:51Z</dc:date>
    </item>
  </channel>
</rss>

