<?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 There's no documented way of in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-wipe-sfr-module-configuration/m-p/2796517#M44248</link>
    <description>&lt;P&gt;There's no documented way of doing what you ask short of uninstalling the module and then reinstalling it. that's what's recommended to wipe customer data when moving systems between customer networks for demo purposes. It would also be recommended for an RMA.&lt;/P&gt;
&lt;P&gt;When we use Firepower Management Center, the recommended method is to snapshot the VM when it's first installed. Then you can rollback to that.&lt;/P&gt;
&lt;P&gt;The less complete method going forward would be to make all policies from copies of the system defaults. Then restore to the default policies and delete the modified ones. You would still be post-setup of the system address, manager and and EULA on the module interface though.&lt;/P&gt;
&lt;P&gt;Of course all that is stored in files on the underlying Linux but it would not be a supported method to go in and modify / delete those outside of a support engineer's direction and guidance.&lt;/P&gt;</description>
    <pubDate>Mon, 18 Jan 2016 03:10:17 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2016-01-18T03:10:17Z</dc:date>
    <item>
      <title>How to wipe sfr module configuration?</title>
      <link>https://community.cisco.com/t5/network-security/how-to-wipe-sfr-module-configuration/m-p/2796516#M44247</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I was just wondering if there is a way to wipe the configuration for the SFR module in a 5506? Basically I'd like to get back to the point when you first session into the SFR and you're greeted with the EULA and then the setup page.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I've just updated it and don't want to have to go through the whole process of going into the boot image and then reloading the sys packaged over an FTP server again.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:32:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-wipe-sfr-module-configuration/m-p/2796516#M44247</guid>
      <dc:creator>Eponymous One</dc:creator>
      <dc:date>2019-03-10T13:32:38Z</dc:date>
    </item>
    <item>
      <title>There's no documented way of</title>
      <link>https://community.cisco.com/t5/network-security/how-to-wipe-sfr-module-configuration/m-p/2796517#M44248</link>
      <description>&lt;P&gt;There's no documented way of doing what you ask short of uninstalling the module and then reinstalling it. that's what's recommended to wipe customer data when moving systems between customer networks for demo purposes. It would also be recommended for an RMA.&lt;/P&gt;
&lt;P&gt;When we use Firepower Management Center, the recommended method is to snapshot the VM when it's first installed. Then you can rollback to that.&lt;/P&gt;
&lt;P&gt;The less complete method going forward would be to make all policies from copies of the system defaults. Then restore to the default policies and delete the modified ones. You would still be post-setup of the system address, manager and and EULA on the module interface though.&lt;/P&gt;
&lt;P&gt;Of course all that is stored in files on the underlying Linux but it would not be a supported method to go in and modify / delete those outside of a support engineer's direction and guidance.&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jan 2016 03:10:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-wipe-sfr-module-configuration/m-p/2796517#M44248</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2016-01-18T03:10:17Z</dc:date>
    </item>
  </channel>
</rss>

