<?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: IP SLA/PBR behavior for Firepower in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4399292#M1080601</link>
    <description>&lt;P&gt;In the IP SLA Track you define the interface to use for pinging, if the interface is down, or the GW for that Interface is down, the ping fails and therefore the track fails.&lt;/P&gt;</description>
    <pubDate>Fri, 07 May 2021 12:36:06 GMT</pubDate>
    <dc:creator>rschlayer</dc:creator>
    <dc:date>2021-05-07T12:36:06Z</dc:date>
    <item>
      <title>IP SLA/PBR behavior for Firepower</title>
      <link>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4397064#M1080475</link>
      <description>&lt;P&gt;We have an FTD with two ISPs where Guest traffic PBR policy uses the backup circuit. I am wondering though, is it possible to use IP SLA in conjunction with PBR so that if this circuit has issues, it falls back to the other circuit? Or is the PBR always going to be in effect?&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 14:48:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4397064#M1080475</guid>
      <dc:creator>ryan14</dc:creator>
      <dc:date>2021-05-03T14:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: IP SLA/PBR behavior for Firepower</title>
      <link>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4397082#M1080477</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/855502"&gt;@ryan14&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can configure an IP SLA track and add that track in the set clause of your route map. When the track goes down the device will route the device using normal route lookup.&lt;/P&gt;&lt;P&gt;See here:&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/general/asa-96-general-config/route-policy-based.html#ID-2182-00000032" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/general/asa-96-general-config/route-policy-based.html#ID-2182-00000032&lt;/A&gt;&lt;/P&gt;&lt;P&gt;BR&lt;BR /&gt;Rick&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 15:02:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4397082#M1080477</guid>
      <dc:creator>rschlayer</dc:creator>
      <dc:date>2021-05-03T15:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: IP SLA/PBR behavior for Firepower</title>
      <link>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4397103#M1080478</link>
      <description>&lt;P&gt;Thank you for that info. I'm still a little confused. If I have a default route pointing to the other (primary) circuit, and the ip sla responder is up (because the primary circuit is) how does the FTD check the availability of the backup circuit, if the default route on the FTD is sending traffic via the primary? Is there a way to specify the source interface?&lt;/P&gt;</description>
      <pubDate>Mon, 03 May 2021 15:29:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4397103#M1080478</guid>
      <dc:creator>ryan14</dc:creator>
      <dc:date>2021-05-03T15:29:34Z</dc:date>
    </item>
    <item>
      <title>Re: IP SLA/PBR behavior for Firepower</title>
      <link>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4399292#M1080601</link>
      <description>&lt;P&gt;In the IP SLA Track you define the interface to use for pinging, if the interface is down, or the GW for that Interface is down, the ping fails and therefore the track fails.&lt;/P&gt;</description>
      <pubDate>Fri, 07 May 2021 12:36:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-sla-pbr-behavior-for-firepower/m-p/4399292#M1080601</guid>
      <dc:creator>rschlayer</dc:creator>
      <dc:date>2021-05-07T12:36:06Z</dc:date>
    </item>
  </channel>
</rss>

