<?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 behaviour for HA in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-for-ha/m-p/3430968#M538872</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depends if you have admin fail-over enabled or not.&amp;nbsp; If not, The secondary admin node will wait until it can re-establish a connection and then synchronize its database. If you have fail-over enabled, the secondary admin node will be promoted to primary.&amp;nbsp; You will be able to administer the deployment from the new primary at that point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 May 2016 14:23:45 GMT</pubDate>
    <dc:creator>Timothy Abbott</dc:creator>
    <dc:date>2016-05-17T14:23:45Z</dc:date>
    <item>
      <title>ISE behaviour for HA</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-for-ha/m-p/3430967#M538867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys!&lt;/P&gt;&lt;P&gt;I've gone through with Cisco Live session for ISE scale up and HA, and I've got a question about the example.&lt;/P&gt;&lt;P&gt;According to the session, there's an primary PAN in DC-A, and the secondary PAN in DC-B.&lt;/P&gt;&lt;P&gt;The question is, when the WAN connection goes down, what will be happened in both PAN?&lt;/P&gt;&lt;P&gt;I guess, the secondary PAN will recognized that the primary PAN is unreachable and it could start to work actively.&lt;/P&gt;&lt;P&gt;What about the Primary PAN? will it continue to work?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;IMG class="image-1 jive-image" height="503" src="https://community.cisco.com/legacyfs/online/fusion/95538_pastedImage_1.png" style="max-height: 900px; max-width: 1200px;" width="790" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 May 2016 03:44:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-for-ha/m-p/3430967#M538867</guid>
      <dc:creator>jinapark</dc:creator>
      <dc:date>2016-05-17T03:44:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE behaviour for HA</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-behaviour-for-ha/m-p/3430968#M538872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depends if you have admin fail-over enabled or not.&amp;nbsp; If not, The secondary admin node will wait until it can re-establish a connection and then synchronize its database. If you have fail-over enabled, the secondary admin node will be promoted to primary.&amp;nbsp; You will be able to administer the deployment from the new primary at that point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 May 2016 14:23:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-behaviour-for-ha/m-p/3430968#M538872</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2016-05-17T14:23:45Z</dc:date>
    </item>
  </channel>
</rss>

