<?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 Shrinking an ISE VM image in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3761885#M487199</link>
    <description>&lt;P&gt;#DearSanta&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;has anyone out there figured out how to shrink an ISE VM disk image (Thin Provisioned) to reduce the size of the .vmdk on the host?&amp;nbsp; A fresh install of ISE results in around 45GB disk image (for a Thin provisioned disk) - but after installing patches and upgrading, the disk starts growing.&amp;nbsp; I would not advocate this in a production environment but some of us lab users have SSD's and disk space is a bit previous &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; Especiclaly when it's technically possible to reclaim all this wasted space.&lt;/P&gt;
&lt;P&gt;it's quite easy with Windows OS because VMWare supports garbage collection (shrinking the unused space in the disk file).&lt;/P&gt;
&lt;P&gt;In Linux OS you can do it with command&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;vmware-toolbox-cmd disk shrink /&amp;nbsp; &amp;nbsp;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;FONT face="courier new,courier"&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;(where&amp;nbsp; /&amp;nbsp; represents a particular mount point - can be run on any mount point)&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But ... it requires the VMWare tools to be installed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And .. biggest challenge with ISE is even getting to the OS.&amp;nbsp; ###DearSanta &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;My approach would be to stop the ISE application, then get to the root shell, and then put the OS into runlevel 1 (single user mode) - hopefully at that point all the processes are killed off and I can safely run the disk shrink.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the past I tried mounting the .vmdk onto a CentOS system and then running the shrink command ... but it kind of killed the disk beyond repair.&amp;nbsp; Not sure why - in my opinion it should have worked.&amp;nbsp; Anyone tried that approach?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any hints apreciated.&amp;nbsp; Please don't reply and say this is not supported etc - I know that already.&amp;nbsp; I am looking for some advice from the lab community. This is all at my own risk.&amp;nbsp; It's not for production use.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Dec 2018 11:58:52 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2018-12-12T11:58:52Z</dc:date>
    <item>
      <title>Shrinking an ISE VM image</title>
      <link>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3761885#M487199</link>
      <description>&lt;P&gt;#DearSanta&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;has anyone out there figured out how to shrink an ISE VM disk image (Thin Provisioned) to reduce the size of the .vmdk on the host?&amp;nbsp; A fresh install of ISE results in around 45GB disk image (for a Thin provisioned disk) - but after installing patches and upgrading, the disk starts growing.&amp;nbsp; I would not advocate this in a production environment but some of us lab users have SSD's and disk space is a bit previous &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp; Especiclaly when it's technically possible to reclaim all this wasted space.&lt;/P&gt;
&lt;P&gt;it's quite easy with Windows OS because VMWare supports garbage collection (shrinking the unused space in the disk file).&lt;/P&gt;
&lt;P&gt;In Linux OS you can do it with command&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;vmware-toolbox-cmd disk shrink /&amp;nbsp; &amp;nbsp;&lt;/FONT&gt;&lt;/STRONG&gt;&lt;FONT face="courier new,courier"&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;(where&amp;nbsp; /&amp;nbsp; represents a particular mount point - can be run on any mount point)&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But ... it requires the VMWare tools to be installed.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;And .. biggest challenge with ISE is even getting to the OS.&amp;nbsp; ###DearSanta &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;My approach would be to stop the ISE application, then get to the root shell, and then put the OS into runlevel 1 (single user mode) - hopefully at that point all the processes are killed off and I can safely run the disk shrink.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the past I tried mounting the .vmdk onto a CentOS system and then running the shrink command ... but it kind of killed the disk beyond repair.&amp;nbsp; Not sure why - in my opinion it should have worked.&amp;nbsp; Anyone tried that approach?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any hints apreciated.&amp;nbsp; Please don't reply and say this is not supported etc - I know that already.&amp;nbsp; I am looking for some advice from the lab community. This is all at my own risk.&amp;nbsp; It's not for production use.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Dec 2018 11:58:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3761885#M487199</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-12-12T11:58:52Z</dc:date>
    </item>
    <item>
      <title>Re: Shrinking an ISE VM image</title>
      <link>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3762848#M487203</link>
      <description>&lt;P&gt;I had another go at shrinking my lab's ISE VM image and I was pleasantly surprised to find out that the following method actually works - I think I last time I tried this I accidentally mounted the partitions as ext3 and not as ext4, and that could have caused the corruption.&lt;/P&gt;
&lt;P&gt;Here's what I did&lt;/P&gt;
&lt;P&gt;Boot a VM running any Linux OS (I used CentOS 7)&lt;BR /&gt;Go to the Linux VM's settings and add another SCSI disk - choose all the defaults and select the ISE .vmdk that you want to shrink. &lt;BR /&gt;I used VMWare Workstation and I just selected Independent persistent mode&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="vmdisk.PNG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/26013iA6793F8184401747/image-size/large?v=v2&amp;amp;px=999" role="button" title="vmdisk.PNG" alt="vmdisk.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;The disk will by recognised by the Linux OS - if you already have a SCSI disk mounted (it will be /dev/sda) then this second disk will be /dev/sdb - if in doubt, just run the command dmesg and then check which /dev/ was used for your newly added disk.&lt;/P&gt;
&lt;P&gt;Now open a Linux terminal and become root user and make two directories&lt;/P&gt;
&lt;PRE&gt;mkdir /mnt/ise2
mkdir /mnt/ise7&lt;/PRE&gt;
&lt;P&gt;There are many partitions on the disk but the only two we care about are partition 2 and partition 7&lt;/P&gt;
&lt;P&gt;Then mount the first of the partitions and then shrink the directory as follows&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;mount /dev/sdb2 /mnt/ise2
vmware-toolbox-cmd disk shrink /mnt/ise2&lt;/PRE&gt;
&lt;P&gt;&lt;BR /&gt;When that is done, the /dev/sdb7 partition is also worth shrinking&lt;/P&gt;
&lt;PRE&gt;mount /dev/sdb7 /mnt/ise7
vmware-toolbox-cmd disk shrink /mnt/ise7&lt;/PRE&gt;
&lt;P&gt;The shrinking speed is pretty slow. I am using Samsung EVO 860 SSD's and it was reading and writing at 1/10th of the normal speed (@50MB/s) - best to leave this running when you're not in a hurry.&lt;/P&gt;
&lt;P&gt;Another tip - I discovered a lot of junk files lying around that I deleted and it made my ISE image a lot smaller. I won't go into a lot of detail here but suffice to say that my disk image is now around 32GB and still working really well. Before the shrinking operation, my disk was 110GB. That's quite a lot of SSD that got freed up &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Dec 2018 10:29:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3762848#M487203</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-12-13T10:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: Shrinking an ISE VM image</title>
      <link>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3763012#M487206</link>
      <description>Nice guide, thanks for sharing!</description>
      <pubDate>Thu, 13 Dec 2018 14:36:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3763012#M487206</guid>
      <dc:creator>andrew333</dc:creator>
      <dc:date>2018-12-13T14:36:09Z</dc:date>
    </item>
    <item>
      <title>Re: Shrinking an ISE VM image</title>
      <link>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3763088#M487210</link>
      <description>&lt;P&gt;Nice, i'm also going to give this a shot at home.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Dec 2018 15:58:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/shrinking-an-ise-vm-image/m-p/3763088#M487210</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2018-12-13T15:58:25Z</dc:date>
    </item>
  </channel>
</rss>

