<?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 6.4 Inline Set Modification in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059089#M1068753</link>
    <description>&lt;P&gt;similar bug hit us in our testing production environment we on version 6.5. TAC suggest the same advise. however we was in testing. in your case better raise a change control. this change is not production impact if you follow the TAC instruction but jsut in case to be safe.&lt;/P&gt;</description>
    <pubDate>Sat, 04 Apr 2020 19:27:46 GMT</pubDate>
    <dc:creator>Sheraz.Salim</dc:creator>
    <dc:date>2020-04-04T19:27:46Z</dc:date>
    <item>
      <title>FirePOWER 6.4 Inline Set Modification</title>
      <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4057995#M1068665</link>
      <description>&lt;P&gt;Due to a bug (CSCvq71351) in 6.4.0.7 - inline sets must be deleted/recreated if they need to be edited&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any potential traffic impact in deleting/recreating an inline set - as long as you don't push policy until after the inline set is rebuilt?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Seems to me you should not be affecting what the sensor knows about the configuration until the policy is pushed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It was recommended by TAC to make changes off hours/maintenance window - was this just CYA?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;B&lt;/P&gt;</description>
      <pubDate>Thu, 02 Apr 2020 22:34:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4057995#M1068665</guid>
      <dc:creator>reheindel</dc:creator>
      <dc:date>2020-04-02T22:34:19Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER 6.4 Inline Set Modification</title>
      <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059041#M1068743</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; Never tried it, but your logic is correct. TAC recommends pretty much any changes to be done in a maintenance, in my experience, cause you never know in reality. If everything would behave the way it should, there would be no more bugs; you get the point.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Cristian Matei.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Apr 2020 16:13:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059041#M1068743</guid>
      <dc:creator>Cristian Matei</dc:creator>
      <dc:date>2020-04-04T16:13:55Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER 6.4 Inline Set Modification</title>
      <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059089#M1068753</link>
      <description>&lt;P&gt;similar bug hit us in our testing production environment we on version 6.5. TAC suggest the same advise. however we was in testing. in your case better raise a change control. this change is not production impact if you follow the TAC instruction but jsut in case to be safe.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Apr 2020 19:27:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059089#M1068753</guid>
      <dc:creator>Sheraz.Salim</dc:creator>
      <dc:date>2020-04-04T19:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER 6.4 Inline Set Modification</title>
      <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059986#M1068860</link>
      <description>&lt;P&gt;Thanks Christian, I appreciate the reply and wholeheartedly agree - they are called bugs for a reason.&lt;BR /&gt;&lt;BR /&gt;I have 12 inline sets to recreate - just to be safe I guess I'll just break them down into smaller change windows and do a few at a time - rather than edit/delete/recreate them all at once and push the updated policy a single time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 14:52:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059986#M1068860</guid>
      <dc:creator>reheindel</dc:creator>
      <dc:date>2020-04-06T14:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER 6.4 Inline Set Modification</title>
      <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059993#M1068862</link>
      <description>&lt;P&gt;Thank you Sheraz for the reply, we do submit change requests but best to do the entire change in a weekend change window.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was hoping to edit the configuration on all 12 inline sets (across 4 sensors) at one - and push the policy a single time - but I'll be safe and break the changes into multiple smaller change windows&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 14:55:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4059993#M1068862</guid>
      <dc:creator>reheindel</dc:creator>
      <dc:date>2020-04-06T14:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: FirePOWER 6.4 Inline Set Modification</title>
      <link>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4060022#M1068865</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;You can still do all within the same maintenance window; just do one at a time, verify functionality, move to next one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Cristian Matei.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Apr 2020 15:24:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-6-4-inline-set-modification/m-p/4060022#M1068865</guid>
      <dc:creator>Cristian Matei</dc:creator>
      <dc:date>2020-04-06T15:24:09Z</dc:date>
    </item>
  </channel>
</rss>

