<?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.7 - New install - 100% cpu in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4188894#M563994</link>
    <description>&lt;P&gt;Yep... there must be a glitch somewhere that intermittently triggers this. #1 started with a different version so I can't consider that... but why it happened on #3-#4-#5-#6 but not #2 is a mystery. Had it happen on my #2 machine I would never have joined it to the deployment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TAC did a onceover on it and declared it good. No alarms at that point, the certs were generated, no crash files. They joined the deployment ok. I'm chasing other intra-deployment cert issues now but cpu is normal&lt;/P&gt;</description>
    <pubDate>Wed, 25 Nov 2020 19:08:37 GMT</pubDate>
    <dc:creator>Y C</dc:creator>
    <dc:date>2020-11-25T19:08:37Z</dc:date>
    <item>
      <title>ISE 2.7 - New install - 100% cpu</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4185964#M563909</link>
      <description>&lt;P&gt;We have an ise 2.1 cluster that's been working for some time. Intent was to start a non-production 2.7 cluster, get it up and running, then move production over to it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Created new vm #1- installed 2.4 - isntalled patch 13 - restored 2.1 backup - upgraded to 2.7 - installed patch 2 - good&lt;/P&gt;&lt;P&gt;Created new vm #2- installed 2.7 - installed patch 2 - joined to deployment - good&lt;/P&gt;&lt;P&gt;Created new vm #3- installed 2.7 - stayed at 100% cpu pegged - rebooted after 30 min - seems ok&lt;/P&gt;&lt;P&gt;Created new vm #4- installed 2.7 - stayed at 100% cpu pegged for 8 hours - seems ok - havent done patch 2 or joined deployment yet&lt;/P&gt;&lt;P&gt;Created new vm #5- installed 2.7 - stayed at 100% cpu pegged for 8 hours - seems ok&amp;nbsp;- havent done patch 2 or joined deployment yet&lt;/P&gt;&lt;P&gt;Created new vm #6- installed 2.7 - stayed at 100% cpu pegged for 8 hours - seems ok&amp;nbsp;- havent done patch 2 or joined deployment yet&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure whats going on with #3-4-5-6. All services were running except application server got stuck initializing. When doing an application stop ise I got the following:&lt;/P&gt;&lt;P&gt;Waiting up to 20 seconds for lock: DATABASE_CLEANUP to complete&lt;BR /&gt;Database is still locked by lock: DATABASE_CLEANUP. Aborting. Please try again later&lt;BR /&gt;%Error: Another ISE DB process (DATABASE_CLEANUP) is in progress, cannot perform Application Stop at this time&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After rebooting #3 the application came up as normal within minutes as expected. I left for the night and came back in the morning - #4-5-6 came up on their own after 8 hours of 100% cpu.&amp;nbsp; These are brand new installs that have no config. I found an existing past thread that had the same error but that indicated it was on an existing install that possibly had a large db.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2020 16:33:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4185964#M563909</guid>
      <dc:creator>Y C</dc:creator>
      <dc:date>2020-11-19T16:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 - New install - 100% cpu</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4188872#M563992</link>
      <description>&lt;P&gt;I had the same problem immediately after deploying 2.7 on a 3655 server.&amp;nbsp; After a while I did a server restart and the Application Server service came up shortly after.&amp;nbsp; Once that did I immediately installed Patch 2 and it seems to be fine now.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 18:42:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4188872#M563992</guid>
      <dc:creator>jstickler</dc:creator>
      <dc:date>2020-11-25T18:42:11Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.7 - New install - 100% cpu</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4188894#M563994</link>
      <description>&lt;P&gt;Yep... there must be a glitch somewhere that intermittently triggers this. #1 started with a different version so I can't consider that... but why it happened on #3-#4-#5-#6 but not #2 is a mystery. Had it happen on my #2 machine I would never have joined it to the deployment.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TAC did a onceover on it and declared it good. No alarms at that point, the certs were generated, no crash files. They joined the deployment ok. I'm chasing other intra-deployment cert issues now but cpu is normal&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 19:08:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-7-new-install-100-cpu/m-p/4188894#M563994</guid>
      <dc:creator>Y C</dc:creator>
      <dc:date>2020-11-25T19:08:37Z</dc:date>
    </item>
  </channel>
</rss>

