<?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 Problem to save changes in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824114#M489683</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hello Marco,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adding to what Marvin said, I worked on one case like the one you are having this week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you do a fsck flash:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will run a scan on the flash to detect if there are some corrupted files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is one link where you get some information from this memory issues.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080b95d3d.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080b95d3d.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you provide the show version of your ASA and also show blocks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 30 Dec 2011 23:03:59 GMT</pubDate>
    <dc:creator>Julio Carvajal</dc:creator>
    <dc:date>2011-12-30T23:03:59Z</dc:date>
    <item>
      <title>Problem to save changes</title>
      <link>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824112#M489681</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a big trouble, becase when we try to "save changes" in a Firewall ASA-5520 this show an error FAILED, and because of this we have lost parts of the configuration. Did you know any solution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# wr mem &lt;/P&gt;&lt;P&gt;Building configuration...&lt;/P&gt;&lt;P&gt;No memory available&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error executing command&lt;/P&gt;&lt;P&gt;[FAILED]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# sh mem &lt;/P&gt;&lt;P&gt;Free memory:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 88792120 bytes (17%)&lt;/P&gt;&lt;P&gt;Used memory:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 448078792 bytes (83%)&lt;/P&gt;&lt;P&gt;-------------&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ----------------&lt;/P&gt;&lt;P&gt;Total memory:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 536870912 bytes (100%)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# sh cpu &lt;/P&gt;&lt;P&gt;CPU utilization for 5 seconds = 1%; 1 minute: 3%; 5 minutes: 4%&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# dir&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Directory of disk0:/&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;214&amp;nbsp;&amp;nbsp;&amp;nbsp; -rwx&amp;nbsp; 14635008&amp;nbsp;&amp;nbsp;&amp;nbsp; 21:14:46 May 05 2009&amp;nbsp; asa803-k8.bin&lt;/P&gt;&lt;P&gt;215&amp;nbsp;&amp;nbsp;&amp;nbsp; -rwx&amp;nbsp; 6851212&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 21:16:08 May 05 2009&amp;nbsp; asdm-603.bin&lt;/P&gt;&lt;P&gt;216&amp;nbsp;&amp;nbsp;&amp;nbsp; drwx&amp;nbsp; 4096&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 15:11:12 Nov 14 2011&amp;nbsp; log&lt;/P&gt;&lt;P&gt;217&amp;nbsp;&amp;nbsp;&amp;nbsp; drwx&amp;nbsp; 4096&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 19:46:18 Aug 18 2007&amp;nbsp; crypto_archive&lt;/P&gt;&lt;P&gt;218&amp;nbsp;&amp;nbsp;&amp;nbsp; -rwx&amp;nbsp; 16275456&amp;nbsp;&amp;nbsp;&amp;nbsp; 09:21:52 Sep 11 2009&amp;nbsp; asa821-k8.bin&lt;/P&gt;&lt;P&gt;220&amp;nbsp;&amp;nbsp;&amp;nbsp; -rwx&amp;nbsp; 11348300&amp;nbsp;&amp;nbsp;&amp;nbsp; 09:23:28 Sep 11 2009&amp;nbsp; asdm-621.bin&lt;/P&gt;&lt;P&gt;202&amp;nbsp;&amp;nbsp;&amp;nbsp; drwx&amp;nbsp; 4096&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 17:05:50 Sep 14 2009&amp;nbsp; coredumpinfo&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;62881792 bytes total (13209600 bytes free)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# wr mem &lt;/P&gt;&lt;P&gt;Building configuration...&lt;/P&gt;&lt;P&gt;No memory available&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error executing command&lt;/P&gt;&lt;P&gt;[FAILED]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:08:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824112#M489681</guid>
      <dc:creator>MarcoPoffal</dc:creator>
      <dc:date>2019-03-11T22:08:41Z</dc:date>
    </item>
    <item>
      <title>Problem to save changes</title>
      <link>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824113#M489682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may have a bad Compact Flash (CF) card. startup-config (where the config is stored when you do wr mem) is on a hidden directory of disk0: (the CF).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh mem is showing you the DRAM, separate from the flash memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have an HA pair? If so you could failover to the standby, break the HA pair and then see if the standby unit allows you to store the running-config to startup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Dec 2011 14:58:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824113#M489682</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2011-12-30T14:58:26Z</dc:date>
    </item>
    <item>
      <title>Problem to save changes</title>
      <link>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824114#M489683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Hello Marco,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Adding to what Marvin said, I worked on one case like the one you are having this week.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you do a fsck flash:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will run a scan on the flash to detect if there are some corrupted files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is one link where you get some information from this memory issues.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080b95d3d.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a0080b95d3d.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you provide the show version of your ASA and also show blocks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 30 Dec 2011 23:03:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824114#M489683</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2011-12-30T23:03:59Z</dc:date>
    </item>
    <item>
      <title>Problem to save changes</title>
      <link>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824115#M489684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Julio:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do a fsck flash and the results are the next:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# fsck flash: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;fsck of flash: complete&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we try to save the changes appears this error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sputnik# wr mem &lt;/P&gt;&lt;P&gt;Building configuration...&lt;/P&gt;&lt;P&gt;No memory available&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error executing command&lt;/P&gt;&lt;P&gt;[FAILED]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can not reboot the firewall, because we are apply a lot of changes, and with the restart all those changes will be lost.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know something else?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jan 2012 16:38:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824115#M489684</guid>
      <dc:creator>Gonzalo Arce</dc:creator>
      <dc:date>2012-01-02T16:38:10Z</dc:date>
    </item>
    <item>
      <title>Problem to save changes</title>
      <link>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824116#M489685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gonzalo,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can always backup the running configuration locally (to your workstation). Under ASDM, "Tools, Backup Configuration". After a reboot, you can restore that backup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Jan 2012 17:03:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/problem-to-save-changes/m-p/1824116#M489685</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2012-01-02T17:03:02Z</dc:date>
    </item>
  </channel>
</rss>

