<?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 Memory management for ISE VM in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596673#M530589</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 15px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #58585b;"&gt;Customer is using ISE 3595 VM which by default allocates 64GB of RAM to the VM. They have been monitoring the memory usage on PSN nodes from vCenter and it's mostly using ~1GB. They are interested in turning the 'Turbonomics Memory Management' feature on, which will dynamically lower or increase the allocated RAM for the VM so there's better usage of shared resources. Is it safe to use such feature for ISE VM? I think it's possible to assign a low watermark which will always be allocated to the VM. What should be that watermark?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 15px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #58585b;"&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 23 Mar 2017 16:52:56 GMT</pubDate>
    <dc:creator>Chetankumar Phulpagare</dc:creator>
    <dc:date>2017-03-23T16:52:56Z</dc:date>
    <item>
      <title>Memory management for ISE VM</title>
      <link>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596673#M530589</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 15px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #58585b;"&gt;Customer is using ISE 3595 VM which by default allocates 64GB of RAM to the VM. They have been monitoring the memory usage on PSN nodes from vCenter and it's mostly using ~1GB. They are interested in turning the 'Turbonomics Memory Management' feature on, which will dynamically lower or increase the allocated RAM for the VM so there's better usage of shared resources. Is it safe to use such feature for ISE VM? I think it's possible to assign a low watermark which will always be allocated to the VM. What should be that watermark?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="font-size: 15px; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #58585b;"&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Mar 2017 16:52:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596673#M530589</guid>
      <dc:creator>Chetankumar Phulpagare</dc:creator>
      <dc:date>2017-03-23T16:52:56Z</dc:date>
    </item>
    <item>
      <title>Re: Memory management for ISE VM</title>
      <link>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596674#M530591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Chetan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't believe that feature is tested and thus would likely be unsupported for production use. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Russ&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Mar 2017 16:57:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596674#M530591</guid>
      <dc:creator>ruhearn</dc:creator>
      <dc:date>2017-03-23T16:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Memory management for ISE VM</title>
      <link>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596675#M530595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;correct&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Mar 2017 16:58:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596675#M530595</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-03-23T16:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Memory management for ISE VM</title>
      <link>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596676#M530597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please reach out to the ISE-PM team &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Mar 2017 17:00:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596676#M530597</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-03-23T17:00:05Z</dc:date>
    </item>
    <item>
      <title>Re: Memory management for ISE VM</title>
      <link>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596677#M530598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the confirmation Russ and Jason!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Mar 2017 17:03:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/memory-management-for-ise-vm/m-p/3596677#M530598</guid>
      <dc:creator>Chetankumar Phulpagare</dc:creator>
      <dc:date>2017-03-23T17:03:45Z</dc:date>
    </item>
  </channel>
</rss>

