<?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: FTD deployment Issue (unable to get internet traffic through Firew in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4507386#M1085328</link>
    <description>&lt;P&gt;Please provide more information on how your network is physically and logically setup (are you using portchannels, subinterfaces, what VLANs correspond to what interface, etc.)&lt;/P&gt;
&lt;P&gt;And please check the following:&lt;/P&gt;
&lt;P&gt;1. Make sure there are no outstanding deployments in the FMC&lt;/P&gt;
&lt;P&gt;2. Make sure you have a Dynamic NAT configured from both Inside and DMZ interfaces towards the Outside interface&lt;/P&gt;
&lt;P&gt;3. Make sure that logging is enabled for the ACP rules, and if / when it is enabled check Analysis &amp;gt; Connection Events to see if traffic is being blocked&lt;/P&gt;
&lt;P&gt;4. If all the above looks fine, log into the FTD CLI and ping your ISP IP (default route IP), if that is successful, ping 8.8.8.8&lt;/P&gt;
&lt;P&gt;5. If all these tests are successful go to the FTD CLI (at the &amp;gt; prompt) and issue the command &lt;STRONG&gt;system support trace&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Make sure to enable &lt;STRONG&gt;system support firewall-engine-debug&lt;/STRONG&gt; when asked.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Enter the source IP of a test PC you will use to generate traffic to the internet&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Enter the destination IP you are testing towards&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; *** for all other fields just press enter ***&lt;/P&gt;
&lt;P&gt;The last step should show if traffic is being dropped by either Snort or a firewall rule, if the traffic is reaching the firewall.&lt;/P&gt;</description>
    <pubDate>Tue, 23 Nov 2021 20:46:00 GMT</pubDate>
    <dc:creator>Marius Gunnerud</dc:creator>
    <dc:date>2021-11-23T20:46:00Z</dc:date>
    <item>
      <title>FTD deployment Issue (unable to get internet traffic through Firewall)</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4506296#M1085277</link>
      <description>&lt;DIV&gt;Hello,&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I'm deploying an FTD v6.6.5 created as native device in a Firepower 4110 appliance as replacement for an ASA5585 with Firepower Services, I have already added the FTD to the FMCv (v6.6.5) and migrated the ASA configuration using the Cisco Migration tool. I verified that all the interfaces were mapped and all licenses are in compliance. I had the ASA5585 up and running in the same FMCv but after the cutover I was unable to get internet traffic through the FTD. I confirmed that the interfaces (Inside, Outside and DMZ) were up and cleared the ARP tables on the switch where the Inside and DMZ interfaces are connected.&lt;/DIV&gt;&lt;DIV&gt;I don't know if I'm missing&amp;nbsp;something after the migration, the report shows that all settings were migrated successfully, Ionly needed to configure the remote VPN manually&lt;/DIV&gt;</description>
      <pubDate>Sun, 21 Nov 2021 19:39:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4506296#M1085277</guid>
      <dc:creator>jesus.valero</dc:creator>
      <dc:date>2021-11-21T19:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: FTD deployment Issue (unable to get internet traffic through Firew</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4506298#M1085278</link>
      <description>Hello, we had the same issue when migrated from 5585's to 2130's.&lt;BR /&gt;We began creating a rule in the 2130 to allow all traffic regardless of&lt;BR /&gt;rules.&lt;BR /&gt;We didn't enable this rule right away.&lt;BR /&gt;We did a deploy of the original rule set and everything began working.&lt;BR /&gt;We never had to use the test rule.&lt;BR /&gt;&lt;BR /&gt;I found this odd and still do.&lt;BR /&gt;Whenever we do an upgrade of the OS we have to make sure that all&lt;BR /&gt;deployments are done.&lt;BR /&gt;After the upgrade we have to another deployment of rules for everything to&lt;BR /&gt;take effect.&lt;BR /&gt;</description>
      <pubDate>Sun, 21 Nov 2021 20:25:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4506298#M1085278</guid>
      <dc:creator>Eric R. Jones</dc:creator>
      <dc:date>2021-11-21T20:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: FTD deployment Issue (unable to get internet traffic through Firew</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4507365#M1085327</link>
      <description>&lt;P class=""&gt;NAT is proper configured? Static default route or dynamic route is in place?&lt;/P&gt;&lt;P class=""&gt;Ping to ISP works? Ping outside internet to 8.8.8.8 works?&lt;/P&gt;&lt;P class=""&gt;Like stated before did you check if ACP might be blocking the traffic? Maybe it did not migrate all ACP as expected.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 20:01:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4507365#M1085327</guid>
      <dc:creator>BmfL</dc:creator>
      <dc:date>2021-11-23T20:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: FTD deployment Issue (unable to get internet traffic through Firew</title>
      <link>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4507386#M1085328</link>
      <description>&lt;P&gt;Please provide more information on how your network is physically and logically setup (are you using portchannels, subinterfaces, what VLANs correspond to what interface, etc.)&lt;/P&gt;
&lt;P&gt;And please check the following:&lt;/P&gt;
&lt;P&gt;1. Make sure there are no outstanding deployments in the FMC&lt;/P&gt;
&lt;P&gt;2. Make sure you have a Dynamic NAT configured from both Inside and DMZ interfaces towards the Outside interface&lt;/P&gt;
&lt;P&gt;3. Make sure that logging is enabled for the ACP rules, and if / when it is enabled check Analysis &amp;gt; Connection Events to see if traffic is being blocked&lt;/P&gt;
&lt;P&gt;4. If all the above looks fine, log into the FTD CLI and ping your ISP IP (default route IP), if that is successful, ping 8.8.8.8&lt;/P&gt;
&lt;P&gt;5. If all these tests are successful go to the FTD CLI (at the &amp;gt; prompt) and issue the command &lt;STRONG&gt;system support trace&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Make sure to enable &lt;STRONG&gt;system support firewall-engine-debug&lt;/STRONG&gt; when asked.&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Enter the source IP of a test PC you will use to generate traffic to the internet&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Enter the destination IP you are testing towards&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; *** for all other fields just press enter ***&lt;/P&gt;
&lt;P&gt;The last step should show if traffic is being dropped by either Snort or a firewall rule, if the traffic is reaching the firewall.&lt;/P&gt;</description>
      <pubDate>Tue, 23 Nov 2021 20:46:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftd-deployment-issue-unable-to-get-internet-traffic-through/m-p/4507386#M1085328</guid>
      <dc:creator>Marius Gunnerud</dc:creator>
      <dc:date>2021-11-23T20:46:00Z</dc:date>
    </item>
  </channel>
</rss>

