<?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 Triggered alerts after upgrading to 3.1 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569812#M573446</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Recently ISE cluster was upgraded to 3.1 from 2.6.&lt;/P&gt;&lt;P&gt;From that time and on, I am receiving the alerts below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Insufficient Virtual Machine Resources&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Details :&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;On node eacgnvaise03 average IO read performance directly from disk device is: 296 MB/Sec; which is less than the minimum requirement of 300 MB/Sec.&amp;nbsp; Please update VM hosting to support IO performance requirement.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Description :&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Virtual Machine resources such as CPU, RAM, Disk Space, or IOPS are insufficient on this host&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Alarm Name : &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Insufficient Virtual Machine Resources&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Details : &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;The required minimum of hard disk(s) total size is 300 GB; found only 0 GB on node eacgnvaise04 &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Description : &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Virtual Machine resources such as CPU, RAM, Disk Space, or IOPS are insufficient on this host&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Are they valid alerts or we do hit a bug?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideas are welcomed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Panos&lt;/P&gt;</description>
    <pubDate>Mon, 14 Mar 2022 09:28:55 GMT</pubDate>
    <dc:creator>desmobrains</dc:creator>
    <dc:date>2022-03-14T09:28:55Z</dc:date>
    <item>
      <title>Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569812#M573446</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Recently ISE cluster was upgraded to 3.1 from 2.6.&lt;/P&gt;&lt;P&gt;From that time and on, I am receiving the alerts below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Insufficient Virtual Machine Resources&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Details :&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;On node eacgnvaise03 average IO read performance directly from disk device is: 296 MB/Sec; which is less than the minimum requirement of 300 MB/Sec.&amp;nbsp; Please update VM hosting to support IO performance requirement.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Description :&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Virtual Machine resources such as CPU, RAM, Disk Space, or IOPS are insufficient on this host&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Alarm Name : &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Insufficient Virtual Machine Resources&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Details : &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;The required minimum of hard disk(s) total size is 300 GB; found only 0 GB on node eacgnvaise04 &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Description : &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Virtual Machine resources such as CPU, RAM, Disk Space, or IOPS are insufficient on this host&lt;/EM&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Are they valid alerts or we do hit a bug?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideas are welcomed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Panos&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 09:28:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569812#M573446</guid>
      <dc:creator>desmobrains</dc:creator>
      <dc:date>2022-03-14T09:28:55Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569842#M573447</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;- You may confirm the disk test results with :&amp;nbsp;&lt;STRONG&gt; show tech | begin "disk IO perf"&lt;/STRONG&gt;&amp;nbsp; , for the rest use the monitoring tools from the hypervisor to observe if sufficient resources can remain available for the particular ISE-VM , one might expect some more resource usage on&amp;nbsp; the new ISE version.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 10:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569842#M573447</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-03-14T10:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569995#M573451</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I will give it a go and come back.&lt;/P&gt;&lt;P&gt;I just spotted that I get the alert around 03:00 in the morning. I had a look into vCenter and I see spikes on CPU and Disk at that moment...&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 14:49:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4569995#M573451</guid>
      <dc:creator>desmobrains</dc:creator>
      <dc:date>2022-03-14T14:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4570095#M573456</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; - Presumably&amp;nbsp; , short single-spike(s) may not need increasing CPU , but if observed several times a&amp;nbsp; day ,&lt;EM&gt;then the conclusion may be &lt;U&gt;opposit&lt;/U&gt;&lt;/EM&gt;&lt;U&gt;e.&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 16:49:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4570095#M573456</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-03-14T16:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4570446#M573462</link>
      <description>&lt;P&gt;The only minimum spec that changed between 2.6 and 3.1 is the minimum RAM for eval - it was 8GB and now it's 16GB.&lt;/P&gt;
&lt;P&gt;How much RAM do you have for the VM? And how many CPUs allocated?&lt;/P&gt;
&lt;P&gt;The disk IO thing is not an issue unless it's consistently low - 300MB/s is borderline and not that fast to be honest - the more throughput (and more IO) the better for the MNT node. Perhaps ISE is on an oversubscribed host - the &lt;STRONG&gt;ISE resources should not be oversubscribed!&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2022 21:39:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4570446#M573462</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2022-03-14T21:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4571580#M573498</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/869603"&gt;@desmobrains&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;I agree with&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;and&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/291804"&gt;@Mark Elsen&lt;/a&gt;&amp;nbsp;...&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;STRONG&gt;ISE&lt;/STRONG&gt; continues to test &lt;STRONG&gt;I/O Read&lt;/STRONG&gt; and &lt;STRONG&gt;Write Performance&lt;/STRONG&gt; on a &lt;STRONG&gt;3Hr interval&lt;/STRONG&gt;&amp;nbsp;(0, 3, 6, 12, 18 and 21 - 9 is skipped due to the&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvx44981" target="_blank" rel="noopener"&gt;CSCvx44981 VM IO Performance Checks not done at 09:00&lt;/A&gt;) and &lt;STRONG&gt;ISE&lt;/STRONG&gt; has a &lt;STRONG&gt;Daily Task&lt;/STRONG&gt; (&lt;EM&gt;isedailycron.sh&lt;/EM&gt;) that takes the &lt;STRONG&gt;Average Disk I/O Performance Measurements&lt;/STRONG&gt; gather for the&amp;nbsp; day and triggers an &lt;STRONG&gt;Alarm&lt;/STRONG&gt; if the average is &lt;U&gt;poor than the threshold&lt;/U&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;Your options:&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;1. Double check if you are receiving the &lt;STRONG&gt;Alarm&lt;/STRONG&gt; on &lt;U&gt;ALL&lt;/U&gt; &lt;STRONG&gt;Nodes&lt;/STRONG&gt; or &lt;STRONG&gt;Nodes&lt;/STRONG&gt; of a specific &lt;STRONG&gt;Host&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;2. Double check the &lt;STRONG&gt;Disk Size&lt;/STRONG&gt; - at least &lt;STRONG&gt;300GB&lt;/STRONG&gt; for &lt;STRONG&gt;PSN&lt;/STRONG&gt; and &lt;STRONG&gt;600GB&lt;/STRONG&gt; for &lt;STRONG&gt;PAN&lt;/STRONG&gt; and &lt;STRONG&gt;MnT&lt;/STRONG&gt; (&lt;STRONG&gt;Small&lt;/STRONG&gt; or &lt;STRONG&gt;Medium&lt;/STRONG&gt;) - take a look at &lt;A href="https://software.cisco.com/download/home/283801620/type/283802505/release/3.1.0" target="_blank" rel="noopener"&gt;ISE 3.1 Software&lt;/A&gt;.&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;3. open a &lt;STRONG&gt;TAC&lt;/STRONG&gt;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2022 12:24:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4571580#M573498</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2022-03-16T12:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4571619#M573500</link>
      <description>&lt;P&gt;Hi Arne,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for coming back.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the allocation for each VM:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;CPUs:16&lt;/P&gt;&lt;P&gt;RAM: 32GB&lt;/P&gt;&lt;P&gt;HDD: 1,23 TB&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The host is not oversubscribed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Panos&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Mar 2022 13:16:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/4571619#M573500</guid>
      <dc:creator>desmobrains</dc:creator>
      <dc:date>2022-03-16T13:16:33Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/5201441#M592094</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.cisco.com/t5/user/viewprofilepage/user-id/869603" target="_blank"&gt;@desmobrains&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Did you find solution for this issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 05:43:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/5201441#M592094</guid>
      <dc:creator>PetriH8</dc:creator>
      <dc:date>2024-10-01T05:43:23Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/5202045#M592116</link>
      <description>&lt;P class="lia-align-justify"&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1095239"&gt;@PetriH8&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P class="lia-align-justify"&gt;&amp;nbsp;are you having the same issue or something similar ?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Oct 2024 21:04:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/5202045#M592116</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2024-10-01T21:04:37Z</dc:date>
    </item>
    <item>
      <title>Re: Triggered alerts after upgrading to 3.1</title>
      <link>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/5228250#M593332</link>
      <description>&lt;P&gt;We have the same issue but only specific host with PxGrid,&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Do you think this the bug or anything else?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2024 02:40:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/triggered-alerts-after-upgrading-to-3-1/m-p/5228250#M593332</guid>
      <dc:creator>oumodom</dc:creator>
      <dc:date>2024-11-25T02:40:39Z</dc:date>
    </item>
  </channel>
</rss>

