<?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: Palo Alto Routing Issue (Forwarding Table) in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170151#M53993</link>
    <description>&lt;P&gt;yes, i also lowered the HQ OSPF AD. I'll proceed to open a case.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using PA 8.0&lt;/P&gt;</description>
    <pubDate>Sat, 05 Aug 2017 09:47:29 GMT</pubDate>
    <dc:creator>SecurityConsultant</dc:creator>
    <dc:date>2017-08-05T09:47:29Z</dc:date>
    <item>
      <title>Palo Alto Routing Issue (Forwarding Table)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170109#M53984</link>
      <description>&lt;P&gt;Hello Everybody,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have several PAs for branches, we have MPLS that is connecting all our branches. We are changing our design in order to use site-to-site IPsec tunnels from each branch to the HQ. And using OSPF in our tunnel to advertise our subnets, since we are connecting one site each week, we are still advertising the subnets via BGP until we finish all sites. I'm facing an issue with the routing and the forwarding table since i'm&amp;nbsp;receiving the subnets via EBGP and OSPF and because EBGP has an AD 20 and OSPF has 30 the PA is using the EBGP. To overcome this problem i lowered the AD of OSPF to 18 to become less than the EBGP. Now all my traffic must go through the tunnel and not EBGP. However, i noticed once i ping from the branch to the HQ the traffic is passing through the tunnel which is good but from the HQ PA to the branch, the traffic is using the EBGP and not the tunnel which is not logical since also the OSPF AD is less than EBGP. Is this a bug with PA IOS 8.0? or is there another issue which i'm missing.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2017 20:09:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170109#M53984</guid>
      <dc:creator>SecurityConsultant</dc:creator>
      <dc:date>2017-08-04T20:09:03Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Routing Issue (Forwarding Table)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170124#M53986</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;So you want all traffic to use the VPN instead of the MPLS and then remove MPLS correct? If yes, they you can utilize policy based forwarding at the remote sites until the MPLS is decommed. Also with the PBF if the VPN goes down, you have have it default back to MPLS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have a static route that points all traffic out&amp;nbsp;via the MPLS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since PBF takes place prior to static routing, everything will go down the VPN&amp;nbsp;via the PBF rule. If the IP in the Montior is unreachable, then the PBF is disabled and traffic will follow the static route you have defined to send down the&amp;nbsp;MPLS&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Once the VPN&amp;nbsp;is available again, the monitor will notice and reenable the PBF so then all traffic will flow down the VPN path.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additional detailed info:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.paloaltonetworks.com/content/dam/pan/en_US/assets/pdf/framemaker/80/pan-os/pan-os/section_16.pdf" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.paloaltonetworks.com/content/dam/pan/en_US/assets/pdf/framemaker/80/pan-os/pan-os/sectio...&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know if you would like further details.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers!&lt;/P&gt;</description>
      <pubDate>Fri, 04 Aug 2017 21:20:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170124#M53986</guid>
      <dc:creator>OtakarKlier</dc:creator>
      <dc:date>2017-08-04T21:20:29Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Routing Issue (Forwarding Table)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170149#M53991</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for your reply,&lt;/P&gt;&lt;P&gt;I know we can use a lot of work around solutions like PBF and using two static routes with different metrics and monitoring. But i&amp;nbsp;planned for this scenario with dynamic routing and i have to make it work without static routing. &amp;nbsp;My thing is i forced the OSPF to have the priority by lowering its AD to 18 and make it less than EBGP and it's not working from one side. Why is it using the wrong forwarding path? &amp;nbsp;i need to fix it.&lt;/P&gt;</description>
      <pubDate>Sat, 05 Aug 2017 09:07:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170149#M53991</guid>
      <dc:creator>SecurityConsultant</dc:creator>
      <dc:date>2017-08-05T09:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Routing Issue (Forwarding Table)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170150#M53992</link>
      <description>&lt;P&gt;Hi &lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/59092"&gt;@SecurityConsultant&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You also lowered the AD of OSPF on the HQ and not only on the branches, right? If your forwarding table is absolutely correct on the HQ and the traffic still takes the wrong path, the best you can probably do is opening a TAC case...&lt;/P&gt;&lt;P&gt;(What exact version of PAN-OS 8 is installed on your firewalls?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Remo&lt;/P&gt;</description>
      <pubDate>Sat, 05 Aug 2017 09:38:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170150#M53992</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2017-08-05T09:38:33Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Routing Issue (Forwarding Table)</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170151#M53993</link>
      <description>&lt;P&gt;yes, i also lowered the HQ OSPF AD. I'll proceed to open a case.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using PA 8.0&lt;/P&gt;</description>
      <pubDate>Sat, 05 Aug 2017 09:47:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/palo-alto-routing-issue-forwarding-table/m-p/170151#M53993</guid>
      <dc:creator>SecurityConsultant</dc:creator>
      <dc:date>2017-08-05T09:47:29Z</dc:date>
    </item>
  </channel>
</rss>

