<?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: Questions about ISE fail over in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3870941#M24795</link>
    <description>&lt;P&gt;The default applies because it's based on the failed heartbeat timers.&amp;nbsp; You can make the polling more aggressive to achieve a faster time to detection.&amp;nbsp; Don't do it!&amp;nbsp; &amp;nbsp;Failover is not a fun topic.&amp;nbsp; It causes processes to restart and ISE is not fast to restart.&amp;nbsp; Let's say you innocently restart the active PAN processes because of a TAC case or whatever.&amp;nbsp; If your polling is too aggressive, then the standby PAN could try to take over.&amp;nbsp; What's the rush anyway?&amp;nbsp; Failover in 30 minutes is more than enough in the greater scheme of things.&amp;nbsp; When PAN is down then the worst thing that can happen is that you cannot create a new policy, or you cannot create a new Sponsored Guest, and things like that.&amp;nbsp; In my books this doesn't constitute a need for fast failover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Manual fail-over only takes as long as the duration that is needed for the standby to restart its processes.&amp;nbsp; &amp;nbsp; So if you typically take 10 minutes to stop, and then start the application processes, then that is how long it will take from the time you manually promote the standby PAN.&amp;nbsp; You do this on the Standby PAN GUI.&lt;/P&gt;
&lt;P&gt;You'll notice also that the previously active PAN node will also restart its processes.&amp;nbsp; it's been a while but I believe that is still the case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 11 Jun 2019 12:40:03 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2019-06-11T12:40:03Z</dc:date>
    <item>
      <title>Questions about ISE fail over</title>
      <link>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3870719#M24790</link>
      <description>&lt;H3&gt;Automatic Failover to the Secondary PAN&lt;/H3&gt;&lt;P class="p"&gt;You can configure ISE to automatically the promote the secondary PAN when the primary PAN becomes unavailable. The configuration is done on the primary administrative node (Primary PAN) on the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph menucascade"&gt;&lt;SPAN class="ph uicontrol"&gt;Administration&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph uicontrol"&gt;System&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&amp;gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph uicontrol"&gt;Deployment&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;page. The failover period is defined as the number of times configured in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph uicontrol"&gt;Number of Failure Polls Before Failover&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;times the number of seconds configured in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ph uicontrol"&gt;Polling Interval&lt;/SPAN&gt;. &lt;STRONG&gt;With the default configuration, that time is 10 minutes.&lt;/STRONG&gt; Promotion of the secondary PAN to primary takes another 10 minutes. So by default, the total time from primary PAN failure to secondary PAN working is 20 minutes.&lt;/P&gt;&lt;P class="p"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p"&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_22_chapter_010.html#ID330" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_22_chapter_010.html#ID330&lt;/A&gt;&lt;/P&gt;&lt;P class="p"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p"&gt;I am reading an article on ISE fail over.&lt;/P&gt;&lt;P class="p"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p"&gt;&lt;STRONG&gt;What does the default configuration in bold mean?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The document states that Auto Fail over takes a total of 20 minutes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Does Manually Fail over also take 20 minutes?&lt;/STRONG&gt;&lt;/P&gt;&lt;P class="p"&gt;&amp;nbsp;&lt;/P&gt;&lt;P class="p"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jun 2019 07:04:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3870719#M24790</guid>
      <dc:creator>JustTakeTheFirstStep</dc:creator>
      <dc:date>2019-06-11T07:04:57Z</dc:date>
    </item>
    <item>
      <title>Re: Questions about ISE fail over</title>
      <link>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3870941#M24795</link>
      <description>&lt;P&gt;The default applies because it's based on the failed heartbeat timers.&amp;nbsp; You can make the polling more aggressive to achieve a faster time to detection.&amp;nbsp; Don't do it!&amp;nbsp; &amp;nbsp;Failover is not a fun topic.&amp;nbsp; It causes processes to restart and ISE is not fast to restart.&amp;nbsp; Let's say you innocently restart the active PAN processes because of a TAC case or whatever.&amp;nbsp; If your polling is too aggressive, then the standby PAN could try to take over.&amp;nbsp; What's the rush anyway?&amp;nbsp; Failover in 30 minutes is more than enough in the greater scheme of things.&amp;nbsp; When PAN is down then the worst thing that can happen is that you cannot create a new policy, or you cannot create a new Sponsored Guest, and things like that.&amp;nbsp; In my books this doesn't constitute a need for fast failover.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Manual fail-over only takes as long as the duration that is needed for the standby to restart its processes.&amp;nbsp; &amp;nbsp; So if you typically take 10 minutes to stop, and then start the application processes, then that is how long it will take from the time you manually promote the standby PAN.&amp;nbsp; You do this on the Standby PAN GUI.&lt;/P&gt;
&lt;P&gt;You'll notice also that the previously active PAN node will also restart its processes.&amp;nbsp; it's been a while but I believe that is still the case.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jun 2019 12:40:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3870941#M24795</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-06-11T12:40:03Z</dc:date>
    </item>
    <item>
      <title>Re: Questions about ISE fail over</title>
      <link>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3871136#M24796</link>
      <description>Thanks arne, you can also look at BRKSEC-3432 and the other performance and scale overview at &lt;A href="https://community.cisco.com/t5/security-documents/ise-performance-amp-scale/ta-p/3642148#toc-hId-118574828" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-performance-amp-scale/ta-p/3642148#toc-hId-118574828&lt;/A&gt;</description>
      <pubDate>Tue, 11 Jun 2019 16:59:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/questions-about-ise-fail-over/m-p/3871136#M24796</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-06-11T16:59:26Z</dc:date>
    </item>
  </channel>
</rss>

