<?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 Make ISE standalone in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3940936#M456436</link>
    <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an ISE deployment that was previously two nodes. The secondary node does not exist anymore.&amp;nbsp; I deregistered it already.&amp;nbsp; SInce I have no plans of adding a new secondary node, the next step is for me to make the current node from primary to standalone.&amp;nbsp; Is there any downtime from and endpoint perspective for switching from primary to standalone?&lt;/P&gt;&lt;P&gt;ISE 2.2 Patch 9&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Oct 2019 14:13:27 GMT</pubDate>
    <dc:creator>BrianPersaud</dc:creator>
    <dc:date>2019-10-15T14:13:27Z</dc:date>
    <item>
      <title>Make ISE standalone</title>
      <link>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3940936#M456436</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an ISE deployment that was previously two nodes. The secondary node does not exist anymore.&amp;nbsp; I deregistered it already.&amp;nbsp; SInce I have no plans of adding a new secondary node, the next step is for me to make the current node from primary to standalone.&amp;nbsp; Is there any downtime from and endpoint perspective for switching from primary to standalone?&lt;/P&gt;&lt;P&gt;ISE 2.2 Patch 9&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2019 14:13:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3940936#M456436</guid>
      <dc:creator>BrianPersaud</dc:creator>
      <dc:date>2019-10-15T14:13:27Z</dc:date>
    </item>
    <item>
      <title>Re: Make ISE standalone</title>
      <link>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3941093#M456437</link>
      <description>&lt;P&gt;Switching from Primary to Standalone will require a restart of the Application Server.&amp;nbsp; I would recommend making the change during a maintenance window or after hours.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2019 17:18:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3941093#M456437</guid>
      <dc:creator>Colby LeMaire</dc:creator>
      <dc:date>2019-10-15T17:18:52Z</dc:date>
    </item>
    <item>
      <title>Re: Make ISE standalone</title>
      <link>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3941617#M456440</link>
      <description>&lt;P&gt;Thanks some endpoints were disconnected for a minute during the switch.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Oct 2019 12:19:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/make-ise-standalone/m-p/3941617#M456440</guid>
      <dc:creator>BrianPersaud</dc:creator>
      <dc:date>2019-10-16T12:19:14Z</dc:date>
    </item>
  </channel>
</rss>

