<?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 2.4 Patch 9 -&amp;gt; High Disk Utilization: Server= in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900825#M470879</link>
    <description>Root "/" is 96% full, not /opt where the radius and tacacs logs are stored.  The 11% being reported for /opt is correct, there are a couple extra digits in the total number.&lt;BR /&gt;&lt;BR /&gt;You will need to contact TAC to access the underlying root file system and clean this up.</description>
    <pubDate>Wed, 31 Jul 2019 15:47:54 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2019-07-31T15:47:54Z</dc:date>
    <item>
      <title>ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900542#M470872</link>
      <description>&lt;P&gt;After patching to 2.4 9 we get massive Log-Massages "High Disk Utilization: Server=" from the secondary Cluster Member.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone else got this "Problem / Bug"&amp;nbsp;&lt;/P&gt;&lt;P&gt;Reloading the Clustermembers won´t fix it.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 08:11:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900542#M470872</guid>
      <dc:creator>bdr_noc</dc:creator>
      <dc:date>2019-07-31T08:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900593#M470875</link>
      <description>&lt;P&gt;we found the problem -&amp;gt; /opt is full.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;is there any possibility to clean up /opt? or should we open an TAC case?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ise2/admin# show disks&lt;/P&gt;&lt;P&gt;disk repository: 17% used (4571472 of 30106488)&lt;/P&gt;&lt;P&gt;Internal filesystems:&lt;BR /&gt;/ : 96% used ( 13616252 of 14987616)&lt;BR /&gt;/dev : 0% used ( 0 of 32838396)&lt;BR /&gt;/dev/shm : 0% used ( 0 of 32849728)&lt;BR /&gt;/run : 1% used ( 1272 of 32849728)&lt;BR /&gt;/sys/fs/cgroup : 0% used ( 0 of 32849728)&lt;BR /&gt;/boot : 24% used ( 106511 of 487634)&lt;BR /&gt;/tmp : 1% used ( 9444 of 1983056)&lt;BR /&gt;/storedconfig : 2% used ( 1588 of 95054)&lt;BR /&gt;&lt;EM&gt;&lt;STRONG&gt;/opt : 11% used ( 110075244 of 1125348968)&lt;/STRONG&gt;&lt;/EM&gt;&lt;BR /&gt;/boot/efi : 4% used ( 8800 of 276312)&lt;BR /&gt;/run/user/440 : 0% used ( 0 of 6569948)&lt;BR /&gt;/run/user/301 : 0% used ( 0 of 6569948)&lt;BR /&gt;/run/user/321 : 0% used ( 0 of 6569948)&lt;BR /&gt;/opt/docker/runtime/devicemapper/mnt/f8bc361d4d73dac8f9ac7d807d530d77605e24395a1bac25044dfa13e1e4f3f9 : 1% used ( 403348 of 104805376)&lt;BR /&gt;/opt/docker/runtime/containers/a5ff40a2e22a9f29238625c76984100ebfc0ffd4b133d652cb5246a68d5c1806/shm : 0% used ( 0 of 65536)&lt;BR /&gt;/run/user/0 : 0% used ( 0 of 6569948)&lt;BR /&gt;/run/user/304 : 0% used ( 0 of 6569948)&lt;BR /&gt;/run/user/303 : 0% used ( 0 of 6569948)&lt;BR /&gt;/run/user/322 : 0% used ( 0 of 6569948)&lt;BR /&gt;warning - / is 96% used (13616252 of 14987616)&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 09:37:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900593#M470875</guid>
      <dc:creator>bdr_noc</dc:creator>
      <dc:date>2019-07-31T09:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900825#M470879</link>
      <description>Root "/" is 96% full, not /opt where the radius and tacacs logs are stored.  The 11% being reported for /opt is correct, there are a couple extra digits in the total number.&lt;BR /&gt;&lt;BR /&gt;You will need to contact TAC to access the underlying root file system and clean this up.</description>
      <pubDate>Wed, 31 Jul 2019 15:47:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3900825#M470879</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-07-31T15:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3927483#M470881</link>
      <description>I have also just applied the Cisco ISE patch 9 and seeing the same symptoms.&lt;BR /&gt;Do we know which directory in the underlying system would require cleaning up?</description>
      <pubDate>Fri, 20 Sep 2019 10:12:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3927483#M470881</guid>
      <dc:creator>Greeners84</dc:creator>
      <dc:date>2019-09-20T10:12:29Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3927980#M470885</link>
      <description>&lt;P&gt;The only filesystem that you would be able to clean up yourself is the local filesystem where upgrade/patch files are stored.&amp;nbsp; Sometimes the local filesystem will get full with coredumps too and you have to clean them out.&amp;nbsp; If any of the other filesystems are full, such as /opt or root, then you have to open a TAC case.&amp;nbsp; They will have to install a rootpatch and access the underlying root filesystem.&amp;nbsp; TAC will figure out what needs to be cleaned up.&lt;/P&gt;</description>
      <pubDate>Sat, 21 Sep 2019 16:45:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3927980#M470885</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2019-09-21T16:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988055#M470887</link>
      <description>I also have a very similar problem in 2.4 patch 9. On two of the nodes in my 4 node deployment I'm seeing 90+ pct utilised after installing patch 9. I deleted everything from disk:/ on all nodes except patch9 but 2 of the nodes were are still at 93+ percent. Cisco TAC visited and installed the root patch and found a load of files in one of the subdirectories of root and they got the disk space back down around 75%. The following day a diagrunn.gz file was generated on one of these nodes which has increased the disk space back up to 94 percent. I deleted the file from disk:/corefiles area but it's still remained at 94% under 'show disk:/'. There's something very buggy going on and not aware of the fix. Not sure if the same symptoms are affecting patch 10 or newer versions?</description>
      <pubDate>Fri, 22 Nov 2019 18:51:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988055#M470887</guid>
      <dc:creator>Greeners84</dc:creator>
      <dc:date>2019-11-22T18:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988336#M470890</link>
      <description>Deleting the core file would not free up any overall used disk space. /localdisk where generated core files are saved is actually mounted in /opt and in 2.4 is a pre thick provisioned 30GB mount. &lt;BR /&gt;&lt;BR /&gt;So adding/removing files in this directory doesn't free up any space other than in /localdisk when viewing sh disk. /localdisk will always use 30 GB of /opt. &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 23 Nov 2019 18:15:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988336#M470890</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-11-23T18:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988430#M470893</link>
      <description>Thank you for the information. Looks like I need Cisco to enable root and delete file from underlying OS, again.</description>
      <pubDate>Sun, 24 Nov 2019 08:37:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988430#M470893</guid>
      <dc:creator>Greeners84</dc:creator>
      <dc:date>2019-11-24T08:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988942#M470895</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/405888"&gt;@Greeners84&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;I have also just applied the Cisco ISE patch 9 and seeing the same symptoms.&lt;BR /&gt;Do we know which directory in the underlying system would require cleaning up?&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;yes issues like this need to be worked through tac&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 15:04:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/3988942#M470895</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-11-25T15:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Patch 9 -&gt; High Disk Utilization: Server=</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/4009511#M470896</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With Cisco TAC assistance we gained access to the underlying OS and purged archive files from this location -&amp;nbsp;cd /var/log/journal/ and using the following command 'journalctl --vacuum-time=1d' free'd up approx 3.5 GB of data in my case. Over time the archive files slowly built up again and I'm now back to where I started. In my case it's only affecting 2 nodes in my 4 node deployment. I have been informed that this is related to a bug which will be fixed in patch 12. I would advise against installing patch 11 until this is fixed because in my case I installed 2.4 patch 11 and now the issue is worse and I've lost access to one of my nodes due to disk space in the underlying OS being 100% utilized. This may be different for you. Seek advice from Cisco.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Adam&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2020 15:40:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-patch-9-gt-high-disk-utilization-server/m-p/4009511#M470896</guid>
      <dc:creator>Greeners84</dc:creator>
      <dc:date>2020-01-10T15:40:15Z</dc:date>
    </item>
  </channel>
</rss>

