<?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 Hyperflex with ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/hyperflex-with-ise/m-p/3525164#M519986</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is recommended to use Thick provisioning when installing ISE on a VM, however, Cisco Hyperflex only provides thin provisioned datastore. Should we still use thick provisioning while installing ISE on VM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 11 Nov 2017 17:02:57 GMT</pubDate>
    <dc:creator>Nancy Saini</dc:creator>
    <dc:date>2017-11-11T17:02:57Z</dc:date>
    <item>
      <title>Hyperflex with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/hyperflex-with-ise/m-p/3525164#M519986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is recommended to use Thick provisioning when installing ISE on a VM, however, Cisco Hyperflex only provides thin provisioned datastore. Should we still use thick provisioning while installing ISE on VM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Nov 2017 17:02:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hyperflex-with-ise/m-p/3525164#M519986</guid>
      <dc:creator>Nancy Saini</dc:creator>
      <dc:date>2017-11-11T17:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: Hyperflex with ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/hyperflex-with-ise/m-p/3525165#M519987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please review &lt;A _jive_internal="true" href="https://community.cisco.com/docs/DOC-68347#jive_content_id_VM_Disk_Size_Minimum_Requirement"&gt;VM Disk Size Minimum Requirement&lt;/A&gt;, if not already done. As our teams have not tested HX specifically, I would suggest you to seek support from HX teams. &lt;A href="https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/HX_TroubleshootingGuide/2-6/b_HyperFlexSystems_TroubleshootingGuide_2_6/b_HyperFlexSystems_TroubleshootingGuide_2_6_chapter_0100.html#id_34366" style="font-family: inherit; font-size: inherit; font-style: inherit; color: #6f53bc;"&gt;Cluster Capacity Different Than Provisioned in HX Data Platform Troubleshooting Topics&lt;/A&gt; mentioned,&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE border="1"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;
&lt;P&gt;&lt;SPAN style="font-family: CiscoSans, Arial, sans-serif; font-size: 14px; font-weight: bold; color: #58585b;"&gt;Thick provisioning or Thick clones.&lt;/SPAN&gt;&lt;SPAN style="color: #58585b; font-family: CiscoSans, Arial, sans-serif; font-size: 14px;"&gt; If thick disks or clones are created, then HX Data Platform does not reserve the space. A soft reservation is used and datastores show space used, but the space is not used in the storage cluster. This is by design to help administrators with not over-provisioning their datastore.&lt;/SPAN&gt;&lt;/P&gt;
&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, I would suggest to read more about thin provisioning to understand its potentially pitfalls. For example, &lt;A href="https://communities.vmware.com/thread/508865"&gt;thin vs thick provisioning and performance impact |VMware Communities&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Nov 2017 17:31:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/hyperflex-with-ise/m-p/3525165#M519987</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-11-11T17:31:46Z</dc:date>
    </item>
  </channel>
</rss>

