<?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 reboot or VM reboot in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606892#M574639</link>
    <description>&lt;P&gt;you can safe to reboot, that will autmatically reboot all the process and come back as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 09 May 2022 14:31:18 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2022-05-09T14:31:18Z</dc:date>
    <item>
      <title>ISE reboot or VM reboot</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606890#M574638</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Does rebooting the ISE VM without halting ISE risk database corruption ? (are their any other risks?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 14:29:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606890#M574638</guid>
      <dc:creator>markleibbrandt</dc:creator>
      <dc:date>2022-05-09T14:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: ISE reboot or VM reboot</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606892#M574639</link>
      <description>&lt;P&gt;you can safe to reboot, that will autmatically reboot all the process and come back as expected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 14:31:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606892#M574639</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-05-09T14:31:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE reboot or VM reboot</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606972#M574641</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;- Still I would advice halting ISE first&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 16:34:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606972#M574641</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2022-05-09T16:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISE reboot or VM reboot</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606977#M574644</link>
      <description>&lt;P&gt;FYSA here are some helpful commands:&lt;/P&gt;
&lt;P&gt;reload - will do the trick for you&lt;/P&gt;
&lt;P&gt;application stop ise - gracefully stop services&lt;/P&gt;
&lt;P&gt;application start ise - gracefully start services&lt;/P&gt;
&lt;P&gt;If you need to completely shutdown:&lt;/P&gt;
&lt;P&gt;application stop ise&lt;/P&gt;
&lt;P&gt;halt&lt;/P&gt;
&lt;P&gt;That shutdown workflow will help decrease risk of db corruption.&amp;nbsp; HTH!&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 16:42:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4606977#M574644</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2022-05-09T16:42:34Z</dc:date>
    </item>
    <item>
      <title>Re: ISE reboot or VM reboot</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4607094#M574654</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/84585"&gt;@markleibbrandt&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;STRONG&gt;STOP&lt;/STRONG&gt; the &lt;STRONG&gt;Application&lt;/STRONG&gt; process before &lt;STRONG&gt;RELOAD&lt;/STRONG&gt; ou &lt;STRONG&gt;HALT&lt;/STRONG&gt; the &lt;STRONG&gt;Appliance&lt;/STRONG&gt; is a &lt;U&gt;good practice&lt;/U&gt;.&lt;/P&gt;
&lt;P&gt;Note 1: &lt;STRONG&gt;RELOAD&lt;/STRONG&gt; the &lt;STRONG&gt;ISE&lt;/STRONG&gt; (via the&amp;nbsp;&lt;STRONG&gt;ise/admin# reload&lt;/STRONG&gt; command)&amp;nbsp;will stop the &lt;STRONG&gt;Processes&lt;/STRONG&gt; first before the "real reload".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps !!!&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 22:46:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-reboot-or-vm-reboot/m-p/4607094#M574654</guid>
      <dc:creator>Marcelo Morais</dc:creator>
      <dc:date>2022-05-09T22:46:21Z</dc:date>
    </item>
  </channel>
</rss>

