<?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: URT on node with multiple personas? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5017342#M587301</link>
    <description>&lt;P&gt;Thanks for the info, it is very straight forward and easy to use.&lt;/P&gt;&lt;P&gt;besides the fact that the estimated time for upgrade is 917 minutes.&lt;/P&gt;&lt;P&gt;Edit after upgrade:&lt;/P&gt;&lt;P&gt;All went surprisingly smooth. We did everything through the GUI.&lt;BR /&gt;The only strange thing was that the REST service had disabled itself after the upgrade.&lt;BR /&gt;The estimated time was very close to the actual used time.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 14 Feb 2024 11:52:01 GMT</pubDate>
    <dc:creator>Janne K.</dc:creator>
    <dc:date>2024-02-14T11:52:01Z</dc:date>
    <item>
      <title>URT on node with multiple personas?</title>
      <link>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5014821#M587166</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Im currently on ISE 2.7 p10 and want to run the URT for 3.2&lt;/P&gt;&lt;P&gt;It says to install on the secondary Administration node.&amp;nbsp;&lt;/P&gt;&lt;P&gt;But, our deployment of six nodes has:&lt;/P&gt;&lt;P&gt;1 combined Primary PAN and secondary MnT,&lt;/P&gt;&lt;P&gt;1 combined Secondary PAN and Primary MnT,&lt;/P&gt;&lt;P&gt;4x PSN&lt;/P&gt;&lt;P&gt;Can I still run it on the secondary pan without any issues or downtime even if it has multiple personas?&lt;/P&gt;</description>
      <pubDate>Thu, 08 Feb 2024 13:08:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5014821#M587166</guid>
      <dc:creator>Janne K.</dc:creator>
      <dc:date>2024-02-08T13:08:52Z</dc:date>
    </item>
    <item>
      <title>Re: URT on node with multiple personas?</title>
      <link>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5015168#M587190</link>
      <description>&lt;P&gt;URT causes no downtime. It's a little application that must be installed on the Secondary PAN and during that installation process, it will prompt you a few times to press a button. It just reads the database and checks for expired certs, disk space requirements and a whole bunch of stuff.&amp;nbsp; If you have to run it again (e.g. after fixing an issue that it has found), then you must first uninstall the urt app, and then install it again.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Feb 2024 20:28:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5015168#M587190</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-02-08T20:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: URT on node with multiple personas?</title>
      <link>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5017342#M587301</link>
      <description>&lt;P&gt;Thanks for the info, it is very straight forward and easy to use.&lt;/P&gt;&lt;P&gt;besides the fact that the estimated time for upgrade is 917 minutes.&lt;/P&gt;&lt;P&gt;Edit after upgrade:&lt;/P&gt;&lt;P&gt;All went surprisingly smooth. We did everything through the GUI.&lt;BR /&gt;The only strange thing was that the REST service had disabled itself after the upgrade.&lt;BR /&gt;The estimated time was very close to the actual used time.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2024 11:52:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/urt-on-node-with-multiple-personas/m-p/5017342#M587301</guid>
      <dc:creator>Janne K.</dc:creator>
      <dc:date>2024-02-14T11:52:01Z</dc:date>
    </item>
  </channel>
</rss>

