<?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 Upgrade Time in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366407#M545311</link>
    <description>&lt;P&gt;Hi Jayson&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the answer to your question is to use the URT tool&amp;nbsp;(Upgrade Readiness Tool) because that will run all sorts of consistency checks on your 2.0 PAN, and then also give you a DETAILED analysis of the time taken to upgrade all nodes in the deployment.&amp;nbsp; It's a great tool.&amp;nbsp; Download it from software.cisco.com and then install it on your Secondary PAN node.&amp;nbsp; Running it there has no impact to the operation of the node.&lt;/P&gt;</description>
    <pubDate>Mon, 16 Apr 2018 01:03:45 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2018-04-16T01:03:45Z</dc:date>
    <item>
      <title>ISE Upgrade Time</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366397#M545308</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have two ISE&amp;nbsp; appliances running on&amp;nbsp;2.0.0.306 configured&amp;nbsp;for distributed deployment setup.&amp;nbsp; I have a requirement to upgrade it to 2.3.&amp;nbsp;&amp;nbsp;I would just like to check with you guys how much time it will take to upgrade both devices&amp;nbsp; One is running as primary for all personas(Administration, Monitoring, Policy Service) and other is running as secondary for all personas.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here are the disk sizes:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Priamry/admin# show disks&lt;/P&gt;
&lt;P&gt;disk repository: 9% used (1220856 of 14985796)&lt;/P&gt;
&lt;P&gt;Internal filesystems:&lt;BR /&gt;/ : 18% used ( 89686464 of 549834344)&lt;BR /&gt;/dev/shm : 0% used ( 0 of 8099972)&lt;BR /&gt;/boot : 8% used ( 32577 of 481800)&lt;BR /&gt;/storedconfig : 2% used ( 1585 of 89231)&lt;BR /&gt;/tmp : 3% used ( 41776 of 1975372)&lt;BR /&gt; all internal filesystems have sufficient free space&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Secondary/admin# show disks&lt;/P&gt;
&lt;P&gt;disk repository: 9% used (1220664 of 14985796)&lt;/P&gt;
&lt;P&gt;Internal filesystems:&lt;BR /&gt;/ : 56% used ( 95595980 of 180476204)&lt;BR /&gt;/dev/shm : 0% used ( 0 of 8166968)&lt;BR /&gt;/boot : 8% used ( 32295 of 481764)&lt;BR /&gt;/storedconfig : 2% used ( 1585 of 89231)&lt;BR /&gt;/tmp : 3% used ( 45076 of 1975372)&lt;BR /&gt; all internal filesystems have sufficient free space&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jayson&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:53:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366397#M545308</guid>
      <dc:creator>pagosojayson</dc:creator>
      <dc:date>2020-02-21T18:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Upgrade Time</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366407#M545311</link>
      <description>&lt;P&gt;Hi Jayson&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the answer to your question is to use the URT tool&amp;nbsp;(Upgrade Readiness Tool) because that will run all sorts of consistency checks on your 2.0 PAN, and then also give you a DETAILED analysis of the time taken to upgrade all nodes in the deployment.&amp;nbsp; It's a great tool.&amp;nbsp; Download it from software.cisco.com and then install it on your Secondary PAN node.&amp;nbsp; Running it there has no impact to the operation of the node.&lt;/P&gt;</description>
      <pubDate>Mon, 16 Apr 2018 01:03:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366407#M545311</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-04-16T01:03:45Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Upgrade Time</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366685#M545312</link>
      <description>&lt;P&gt;What&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;said. +5!&lt;/P&gt;</description>
      <pubDate>Mon, 16 Apr 2018 12:13:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-time/m-p/3366685#M545312</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2018-04-16T12:13:23Z</dc:date>
    </item>
  </channel>
</rss>

