<?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: External ping to public ip of secondary ISP interface. in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449124#M100900</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/200899"&gt;@Dyardley&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If other end is still not able to ping the palo alto interface, did you checked the traffic logs? Traffic logs should give you clarity on what's actually happening.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 23 Nov 2021 17:15:54 GMT</pubDate>
    <dc:creator>SutareMayur</dc:creator>
    <dc:date>2021-11-23T17:15:54Z</dc:date>
    <item>
      <title>External ping to public ip of secondary ISP interface.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449093#M100896</link>
      <description>&lt;P&gt;I am having issues allowing pings on my secondary ISP interface. I have a dual ISP set up with my main connection a 10gbit connection with ISP1 and a backup 1gbit with ISP2. I am currently using path monitoring for internet failover and I also have a few PBF rules for some traffic to leave through ISP2. I was asked by ISP2 to allow ICMP for their subnet so they can monitor the connection. So I set up a second management profile that only allowed ping from their subnet and applied it to that interface. They still can seem to get a response when they ping it. Is there something else that I am missing?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 15:24:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449093#M100896</guid>
      <dc:creator>Dyardley</dc:creator>
      <dc:date>2021-11-23T15:24:35Z</dc:date>
    </item>
    <item>
      <title>Re: External ping to public ip of secondary ISP interface.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449124#M100900</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/200899"&gt;@Dyardley&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If other end is still not able to ping the palo alto interface, did you checked the traffic logs? Traffic logs should give you clarity on what's actually happening.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 17:15:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449124#M100900</guid>
      <dc:creator>SutareMayur</dc:creator>
      <dc:date>2021-11-23T17:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: External ping to public ip of secondary ISP interface.</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449508#M100942</link>
      <description>&lt;P&gt;I literally just configured this.&amp;nbsp; I have the default virtual router and then a separate virtual router for each ISP (hub and spoke). With this method, you can prevent the dedicated ISP virtual routers having a zero route to the other ISP.&amp;nbsp; Therefore path monitoring will have the desired effect to flush the zero route for that specific ISP. You need to create a loopback on each virtual router.&amp;nbsp; Then create static routes (hub and spoke) to each ISP router (requires loopback). You can then configure eBGP on those links, along with redistribute. The method I used was local pref on the internal (default) virtual router to designate primary and secondary ISP.&amp;nbsp; The failover is tuned to 3 seconds and then hold time of 2 minutes for fail back. PDF with screenshot can be found here, although this is not a how-to guide, it will give you some of the main concepts.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.linkedin.com/feed/update/urn:li:activity:6869729830720688128/" target="_blank"&gt;https://www.linkedin.com/feed/update/urn:li:activity:6869729830720688128/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Nov 2021 22:42:03 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/external-ping-to-public-ip-of-secondary-isp-interface/m-p/449508#M100942</guid>
      <dc:creator>johnwalshaw</dc:creator>
      <dc:date>2021-11-25T22:42:03Z</dc:date>
    </item>
  </channel>
</rss>

