<?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 cluster proper shutdown order in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828488#M527818</link>
    <description>&lt;P&gt;Yes, that looks to me.&lt;/P&gt;</description>
    <pubDate>Thu, 28 Mar 2019 20:27:33 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2019-03-28T20:27:33Z</dc:date>
    <item>
      <title>ISE cluster proper shutdown order</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3502752#M527808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been doing some regression testing with a small VM-based ISE 2.0 p5 cluster in a customer environment. The cluster has 5 nodes; 2x PAN/MnT nodes, 2x PSN, 1x pxGrid. I've found that when I shutdown all of the VMs for maintenance (taking snapshots, modifying VM settings, etc), and power them all back up, the 2x PSNs come back as Replication Stopped and I have to do a manual resync.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried shutting them down in different sequences (PSNs first then PAN/MnT and vice-versa, halting from CLI, stopping ISE application then halting, etc) but have not found a way to do this without having to resync the PSNs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a proper sequence for shutting down the cluster so as to prevent this Replication Stopped issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not found anything documented, so this might be helpful info for future documentation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Aug 2017 22:01:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3502752#M527808</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2017-08-08T22:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster proper shutdown order</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3502753#M527811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What order do you restart the VM's?&amp;nbsp; Although, that shouldn't theoretically make a difference, since we can't always control the order in which VMs restart.&amp;nbsp; But maybe try starting PANs, then MnT and then PSN.&amp;nbsp; A lot of waiting in between though &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Aug 2017 23:47:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3502753#M527811</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2017-08-08T23:47:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster proper shutdown order</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3502754#M527814</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please note that taking VM snapshots is not a supported means for ISE backup/restore and may drag VM performance down considerably in some cases. When shutting down ISE VMs, please explicitly stop ISE services first as the VM stop option does not seem to do that in ISE 2.0. The sequences I would suggest to try are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;stop: PAN, PSNs, and MnT&lt;/P&gt;&lt;P&gt;start: MnT, PSNs and then PAN&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 12 Aug 2017 02:15:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3502754#M527814</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-08-12T02:15:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster proper shutdown order</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828406#M527816</link>
      <description>&lt;P&gt;Just want to confirm full order of execution - examples below. Please confirm&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The correct way to shut down an ISE node&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Application stop ISE&lt;/LI&gt;
&lt;LI&gt;Halt&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Order of shutting down ISE Environment&lt;/P&gt;
&lt;P&gt;- Stop: PAN, PSNs, and MnT&lt;/P&gt;
&lt;P&gt;- Start: MnT, PSNs and then PAN&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If HA then shutdown standby first.&lt;/P&gt;
&lt;P&gt;- Stop: PAN (Standby), PAN (Active), PSNs (Standby), PSNs (Active), and MnT (Standby), MnT (Active)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;- Start: MnT (Active), MnT (Standby), PSNs (Active), PSNs (Standby)&amp;nbsp; and then PAN (Active), PAN (Standby)&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 18:26:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828406#M527816</guid>
      <dc:creator>Jason Maynard</dc:creator>
      <dc:date>2019-03-28T18:26:36Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster proper shutdown order</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828488#M527818</link>
      <description>&lt;P&gt;Yes, that looks to me.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 20:27:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828488#M527818</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-03-28T20:27:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE cluster proper shutdown order</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828496#M527820</link>
      <description>&lt;P&gt;Thanks for confirming.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 20:35:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cluster-proper-shutdown-order/m-p/3828496#M527820</guid>
      <dc:creator>Jason Maynard</dc:creator>
      <dc:date>2019-03-28T20:35:53Z</dc:date>
    </item>
  </channel>
</rss>

