<?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: ISE disk utilization in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928600#M456942</link>
    <description>You may also want to double check the output of the "show disks" command. The localdisk you are looking at is only 15 or 30 GB of the provisioned space depending on the ISE release.  It is preallocated under the covers, so while you will still get an alarm if /localdisk is full, it wouldn't free up space in /opt if that was the culprit.</description>
    <pubDate>Mon, 23 Sep 2019 14:08:53 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2019-09-23T14:08:53Z</dc:date>
    <item>
      <title>ISE disk utilization</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928521#M456937</link>
      <description>&lt;P&gt;Good day!&lt;/P&gt;&lt;P&gt;I've issue with my Cisco ISE. Disk space was exhausted by 100 %&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had erase old patches and now disk space is free. But i'm sure that some trash files also exist in my ISE. Which are could be delete from disk and why? Which files are more critical and couldn't be erased ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt; dir disk:/ rec

Directory of disk:/

       1216 Dec 27 2017 12:15:47  CmdTool.log
     126942 Dec 27 2017 12:15:47  MegaSAS.log
 2079452706 Dec 27 2017 12:44:13  test-CFG10-171227-1233.tar.gpg
  857975062 Dec 27 2017 13:28:31  logs-OPS10-171227-1326.tar.gpg
          0 Jun 07 2018 16:12:47  prrt-server.log
  470139656 Jan 13 2018 01:05:23  ise-patchbundle-2.2.0.470-Patch5-225829.SPA.x86_64.tar.gz
  474075920 Mar 12 2018 19:00:01  ise-patchbundle-2.2.0.470-Patch6-232642.SPA.x86_64.tar.gz
       5186 Dec 27 2017 12:19:54  RootKey-appbundle-1.0-x86_64.tar.gz
        317 Aug 18 2019 11:12:06  &amp;amp;1
     178122 Dec 26 2017 15:42:21  \\10.10.10.100\1\tech.txt
      16384 Nov 28 2017 11:32:13  lost+found/
       4096 Jun 07 2018 16:12:47  config/
       4096 Sep 23 2019 15:04:09  corefiles/

Directory of disk:/lost+found

No files in directory

Directory of disk:/config

       1208 Jun 07 2018 16:12:47  RuntimeDebugLog.config

Directory of disk:/corefiles

10320667496 Jul 29 2019 17:43:53  core.20323
      46759 Jul 29 2019 19:01:01  hs_err_pid20323.log.gz&lt;/PRE&gt;</description>
      <pubDate>Mon, 23 Sep 2019 12:36:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928521#M456937</guid>
      <dc:creator>Konev6990</dc:creator>
      <dc:date>2019-09-23T12:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE disk utilization</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928562#M456938</link>
      <description>Seems like your ISE server crashed on 29th of July. Did you get that checked with TAC ? If yes, you can remove the file  core.20323 and all the following files :&lt;BR /&gt;&lt;BR /&gt;       1216 Dec 27 2017 12:15:47  CmdTool.log&lt;BR /&gt;     126942 Dec 27 2017 12:15:47  MegaSAS.log&lt;BR /&gt;2079452706 Dec 27 2017 12:44:13  test-CFG10-171227-1233.tar.gpg&lt;BR /&gt;  857975062 Dec 27 2017 13:28:31  logs-OPS10-171227-1326.tar.gpg&lt;BR /&gt;          0 Jun 07 2018 16:12:47  prrt-server.log&lt;BR /&gt;  470139656 Jan 13 2018 01:05:23  ise-patchbundle-2.2.0.470-Patch5-225829.SPA.x86_64.tar.gz&lt;BR /&gt;  474075920 Mar 12 2018 19:00:01  ise-patchbundle-2.2.0.470-Patch6-232642.SPA.x86_64.tar.gz&lt;BR /&gt;       5186 Dec 27 2017 12:19:54  RootKey-appbundle-1.0-x86_64.tar.gz&lt;BR /&gt;        317 Aug 18 2019 11:12:06  &amp;amp;1&lt;BR /&gt;     178122 Dec 26 2017 15:42:21  \\10.10.10.100\1\tech.txt&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Sep 2019 13:23:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928562#M456938</guid>
      <dc:creator>Surendra</dc:creator>
      <dc:date>2019-09-23T13:23:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE disk utilization</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928588#M456940</link>
      <description>&lt;P&gt;You can remove everything from the localdisk if you don't need it anymore.&amp;nbsp; Even coredumps will happen during normal operation and those files can be removed as well unless the "crash" actually caused some symptoms that the users experienced.&amp;nbsp; I have seen many ISE deployments where coredumps happen every so often but don't result in impact to operations.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2019 13:58:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928588#M456940</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2019-09-23T13:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE disk utilization</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928600#M456942</link>
      <description>You may also want to double check the output of the "show disks" command. The localdisk you are looking at is only 15 or 30 GB of the provisioned space depending on the ISE release.  It is preallocated under the covers, so while you will still get an alarm if /localdisk is full, it wouldn't free up space in /opt if that was the culprit.</description>
      <pubDate>Mon, 23 Sep 2019 14:08:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-disk-utilization/m-p/3928600#M456942</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-09-23T14:08:53Z</dc:date>
    </item>
  </channel>
</rss>

