<?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: Firepower Updates in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756440#M1012553</link>
    <description>&lt;P&gt;I've just editted my previous post. Yes they would all be impacted, you can use the Deploy Policy scheduled tasks to schedule the updates and target specific devices. (Leave the automatic deploy SRU checkbox unchecked)&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Sun, 02 Dec 2018 14:20:46 GMT</pubDate>
    <dc:creator>phil.hydea</dc:creator>
    <dc:date>2018-12-02T14:20:46Z</dc:date>
    <item>
      <title>Firepower Updates</title>
      <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756425#M1012550</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Quick question regarding Recurring Rule Updates within FMC. If it tick the 'Deploy Updated Policies to targeted devices' does that mean that the update will be automatically deployed to my FTDs and the Snort Process restarted?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 14:08:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756425#M1012550</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2019-03-12T14:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Updates</title>
      <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756436#M1012551</link>
      <description>&lt;P&gt;Hi - yes it will automatically deploy the updates and there will be detection engine restarts which will disrupt traffic inspection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can uncheck that box and create a scheduled task &amp;gt; Deploy Policy. This would allow you to choose the desired time (eg. a maintenance window) and frequency. This would mean if there are 3 SRU updates since the last policy deploy, the FMC would wait to deploy them (culminative).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 02 Dec 2018 14:18:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756436#M1012551</guid>
      <dc:creator>phil.hydea</dc:creator>
      <dc:date>2018-12-02T14:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Updates</title>
      <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756438#M1012552</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Thanks for the response. If I have 10 FTDs in my deployment, will these all be impacted at the same time if I configure this? Is there anyway to deploy the updates the the FTDs one by one?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 02 Dec 2018 14:17:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756438#M1012552</guid>
      <dc:creator>dm2020</dc:creator>
      <dc:date>2018-12-02T14:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Updates</title>
      <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756440#M1012553</link>
      <description>&lt;P&gt;I've just editted my previous post. Yes they would all be impacted, you can use the Deploy Policy scheduled tasks to schedule the updates and target specific devices. (Leave the automatic deploy SRU checkbox unchecked)&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sun, 02 Dec 2018 14:20:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756440#M1012553</guid>
      <dc:creator>phil.hydea</dc:creator>
      <dc:date>2018-12-02T14:20:46Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Updates</title>
      <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756443#M1012554</link>
      <description>&lt;P&gt;Hi , If you are running version 6.2.3, then you can configure from cli to preserve the snort connections&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;configure snort preserve-connection&amp;nbsp;enable&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/623/configuration/guide/fpmc-config-guide-v623/policy_management.html#concept_uc1_gtq_ty" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/623/configuration/guide/fpmc-config-guide-v623/policy_management.html#concept_uc1_gtq_ty&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;HTH&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Abheesh&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 02 Dec 2018 14:22:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756443#M1012554</guid>
      <dc:creator>Abheesh Kumar</dc:creator>
      <dc:date>2018-12-02T14:22:17Z</dc:date>
    </item>
    <item>
      <title>Re: Firepower Updates</title>
      <link>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756445#M1012555</link>
      <description>Yes good point. To also add to this, whilst existing connections can be&lt;BR /&gt;preserved, new connections will be dropped during the snort/detection&lt;BR /&gt;engine reload&lt;BR /&gt;</description>
      <pubDate>Sun, 02 Dec 2018 14:25:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-updates/m-p/3756445#M1012555</guid>
      <dc:creator>phil.hydea</dc:creator>
      <dc:date>2018-12-02T14:25:04Z</dc:date>
    </item>
  </channel>
</rss>

