<?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: OSPF Accept Policy in ExtremeSwitching (VSP/Fabric Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8796#M377</link>
    <description>Thanks Jessica!</description>
    <pubDate>Fri, 12 Aug 2022 14:43:00 GMT</pubDate>
    <dc:creator>RobertD1</dc:creator>
    <dc:date>2022-08-12T14:43:00Z</dc:date>
    <item>
      <title>OSPF Accept Policy</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8794#M375</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I've been trying to use an IP OSPF accept policy to filter out inter-area routes on a VSP within a VRF but it does not take affect. All routes are seen in the routing table from the advertising router.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It seems the OSPF accept policy does not influence the routes and cannot stop the routes as they are exchanged as the OSPF adjacency comes up and they exchange databases.&lt;BR /&gt;&lt;BR /&gt;The VSP VRF has only one area with all interfaces in it so not an ABR.&lt;BR /&gt;&lt;BR /&gt;I have a Secure Router 2330 joining two VRFs together on the VSP and I can filter routes between areas using a filter-list and prefix-list which is an ABR.&lt;BR /&gt;&lt;BR /&gt;Maybe the Firewall is the best place to do this anyway but frustrated by the fact the accept policy has no impact and was wondering if I was missing something. I do apply the policy and checked the prefix-list and route-map are correct.&lt;BR /&gt;&lt;BR /&gt;router vrf corporate&lt;BR /&gt;ip prefix-list "stub3" 31.31.31.31/32 id 6 ge 32 le 32&lt;BR /&gt;ip ospf accept adv-rtr 1.1.1.1 enable route-map "ospf_peer"&lt;BR /&gt;route-map "ospf_peer" 1&lt;BR /&gt;no permit&lt;BR /&gt;enable&lt;BR /&gt;match network "stub3"&lt;BR /&gt;exit&lt;BR /&gt;exit&lt;BR /&gt;ip ospf apply accept adv-rtr 1.1.1.1 vrf corporate&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Rob&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Jul 2022 12:55:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8794#M375</guid>
      <dc:creator>RobertD1</dc:creator>
      <dc:date>2022-07-19T12:55:00Z</dc:date>
    </item>
    <item>
      <title>RE: OSPF Accept Policy</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8795#M376</link>
      <description>OSPF import policy allows you to prevent external routes from being added to the routing tables of OSPF neighbors. The import policy does not impact the OSPF database. This means that the import policy has no impact on the link-state advertisements. The filtering is done only on external routes in OSPF.&amp;nbsp; &lt;A href="https://www.onecognizant.one/"&gt;&lt;SPAN style="color: #ffffff; background-color: #ffffff;"&gt;One Cognizant Portal&lt;/SPAN&gt;&lt;/A&gt;</description>
      <pubDate>Fri, 12 Aug 2022 14:39:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8795#M376</guid>
      <dc:creator>Jessicam1</dc:creator>
      <dc:date>2022-08-12T14:39:00Z</dc:date>
    </item>
    <item>
      <title>RE: OSPF Accept Policy</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8796#M377</link>
      <description>Thanks Jessica!</description>
      <pubDate>Fri, 12 Aug 2022 14:43:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-vsp-fabric/ospf-accept-policy/m-p/8796#M377</guid>
      <dc:creator>RobertD1</dc:creator>
      <dc:date>2022-08-12T14:43:00Z</dc:date>
    </item>
  </channel>
</rss>

