<?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.2 VM Dedicated Resources in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588015#M527491</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes! You’re working with a critical piece of your network and need to dedicate resources so its always avialable&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Aug 2017 17:16:34 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2017-08-22T17:16:34Z</dc:date>
    <item>
      <title>ISE 2.2 VM Dedicated Resources</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588014#M527490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="font-size: 13.3333px;"&gt;In past ISE documentation for installing ISE on a virtual machine there was always a note stating, "&lt;SPAN style="color: #58585b; font-family: CiscoSans, Arial, sans-serif; font-size: 14px;"&gt;It is highly recommended that VM resources be dedicated and not shared or oversubscribed across multiple VMs. Deploying Cisco ISE virtual appliances using the OVF templates will ensure that adequate resources are assigned to each VM.".&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="color: #58585b; font-family: CiscoSans, Arial, sans-serif; font-size: 14px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-size: 13.3333px;"&gt;&lt;SPAN style="color: #58585b; font-family: CiscoSans, Arial, sans-serif; font-size: 14px;"&gt;In ISE 2.2 there is no note in the documentation stating it is highly recommended that VM resources be dedicated.&amp;nbsp; Does this recommendation still stand?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 17:14:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588014#M527490</guid>
      <dc:creator>jarosner</dc:creator>
      <dc:date>2017-08-22T17:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 VM Dedicated Resources</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588015#M527491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes! You’re working with a critical piece of your network and need to dedicate resources so its always avialable&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 17:16:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588015#M527491</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-08-22T17:16:34Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 VM Dedicated Resources</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588016#M527492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I see that original wording in Install Guide was changed.&amp;nbsp; The end goal is to ensure customers deploy ISE in a manner that does not lead to failure of this critical service.&amp;nbsp; However, we do acknowledge that some customers have very experienced staff that maintain their virtual server deployments.&amp;nbsp; As covered in BRKSEC-3699 (ciscolive.com), I still note that it is possible to deploy without reservations, but doing so is at customer risk.&amp;nbsp; In other words, if call TAC for issue that is not related to resource utilization, they should not make an issue that you have not enabled reservations, for example.&amp;nbsp; However, if run into any issue that may be related to resource utilization, it is perfectly in TAC's right to call this out and request that the reservations or other minimum requirements be met before attempting to troubleshoot other aspects of issue.&amp;nbsp; I suspect that concerns over over-subscription and under-resourcing led someone to request removal of the "strong recommendation".&amp;nbsp; Many of our TAC issues are rooted in customers that deploy with less than required resources, or attempted to over-subscribe resources with multiple VMs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 21:59:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-vm-dedicated-resources/m-p/3588016#M527492</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2017-08-22T21:59:26Z</dc:date>
    </item>
  </channel>
</rss>

