<?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: could not issue wr mem command in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373288#M713608</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the memory utilization goes high then you can't issue write mem?&lt;/P&gt;&lt;P&gt;We need to figure out what is eating all that memory.&amp;nbsp; Tracking memory usage is a mundane process. I'd suggest opening a TAC case and letting them collect what they need and let you know if this is a known issue and may be upgrade the code accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Apr 2010 10:28:21 GMT</pubDate>
    <dc:creator>Kureli Sankar</dc:creator>
    <dc:date>2010-04-16T10:28:21Z</dc:date>
    <item>
      <title>could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373282#M713539</link>
      <description>&lt;P&gt;i have 5520 ASA ,i am unable to write config in startup ,means it gives error on issuing wr mem command.&lt;/P&gt;&lt;P&gt;i am able to add or modify the rules&lt;/P&gt;&lt;P&gt;the cpu usage is showing around 30 % while the memory usage is high above 80% as has 512 memory installed&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:33:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373282#M713539</guid>
      <dc:creator>JEETENDRA BAGALE</dc:creator>
      <dc:date>2019-03-11T17:33:46Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373283#M713543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the error message that you are getting?&lt;/P&gt;&lt;P&gt;What do you have in flash? Please share "show flash"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:00:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373283#M713543</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-04-16T10:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373284#M713545</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Pls. run fsck disk0: and then try to write mem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00807ea93d.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00807ea93d.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:12:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373284#M713545</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-04-16T10:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373285#M713551</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have seen this before. &lt;/P&gt;&lt;P&gt;try to copy the running config to a new *.cfg file on the disk:0 and then change the config-url location.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:18:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373285#M713551</guid>
      <dc:creator>matt.walls</dc:creator>
      <dc:date>2010-04-16T10:18:05Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373286#M713573</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;now i am able to issue wr mem command but the memory utilisation is still high it is about&amp;nbsp; at 85 % constant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:24:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373286#M713573</guid>
      <dc:creator>JEETENDRA BAGALE</dc:creator>
      <dc:date>2010-04-16T10:24:40Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373287#M713594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use running-config startup-config to to save configuration to startup (NVRAM)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Arulkumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:25:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373287#M713594</guid>
      <dc:creator>arulkumar80</dc:creator>
      <dc:date>2010-04-16T10:25:08Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373288#M713608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When the memory utilization goes high then you can't issue write mem?&lt;/P&gt;&lt;P&gt;We need to figure out what is eating all that memory.&amp;nbsp; Tracking memory usage is a mundane process. I'd suggest opening a TAC case and letting them collect what they need and let you know if this is a known issue and may be upgrade the code accordingly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:28:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373288#M713608</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-04-16T10:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373289#M713620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;pls find the attached file can you make anything out from that,it&lt;/P&gt;&lt;P&gt;is the output of sho proc mem&amp;nbsp; .&lt;/P&gt;&lt;P&gt;and i was able to issue the command wr mem when my memory utilisation was 83 %&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 10:38:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373289#M713620</guid>
      <dc:creator>JEETENDRA BAGALE</dc:creator>
      <dc:date>2010-04-16T10:38:31Z</dc:date>
    </item>
    <item>
      <title>Re: could not issue wr mem command</title>
      <link>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373290#M713628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can also try to disable threat-detection and that will free coniguous blocks of memory and you will be able to save it with "wr mem"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Apr 2010 22:25:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/could-not-issue-wr-mem-command/m-p/1373290#M713628</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2010-04-16T22:25:49Z</dc:date>
    </item>
  </channel>
</rss>

