<?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 ISE Operational data question in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-operational-data-question/m-p/4406013#M567430</link>
    <description>&lt;P&gt;We recently performed a DR failover event for our distributed ISE environment which consists of 4 nodes, a PAN/MnT and PSN node in geographically distinct data centers.&amp;nbsp; We shut down the ISE application on the primary data center PAN and PSN in order to effect the application unavailable as well as shut down the NICs on the primary d.c. PSN.&amp;nbsp; We promoted the secondary PAN at the backup d.c.&lt;/P&gt;&lt;P&gt;Operations after failover appeared to run without issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is: While operating in this mode and operational changes were made on the backup data center PAN (now Primary), when failing back to the primary d.c. how does the platform ensure these operational changes are brought back to the primary d.c.?&amp;nbsp; Does a manual configuration backup need to occur on the PAN acting as primary prior to reverting back to normal state?&amp;nbsp; Then that configuration backup is restored once back in a normal state?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
    <pubDate>Thu, 20 May 2021 13:14:46 GMT</pubDate>
    <dc:creator>fredluneau</dc:creator>
    <dc:date>2021-05-20T13:14:46Z</dc:date>
    <item>
      <title>ISE Operational data question</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-operational-data-question/m-p/4406013#M567430</link>
      <description>&lt;P&gt;We recently performed a DR failover event for our distributed ISE environment which consists of 4 nodes, a PAN/MnT and PSN node in geographically distinct data centers.&amp;nbsp; We shut down the ISE application on the primary data center PAN and PSN in order to effect the application unavailable as well as shut down the NICs on the primary d.c. PSN.&amp;nbsp; We promoted the secondary PAN at the backup d.c.&lt;/P&gt;&lt;P&gt;Operations after failover appeared to run without issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My question is: While operating in this mode and operational changes were made on the backup data center PAN (now Primary), when failing back to the primary d.c. how does the platform ensure these operational changes are brought back to the primary d.c.?&amp;nbsp; Does a manual configuration backup need to occur on the PAN acting as primary prior to reverting back to normal state?&amp;nbsp; Then that configuration backup is restored once back in a normal state?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Thu, 20 May 2021 13:14:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-operational-data-question/m-p/4406013#M567430</guid>
      <dc:creator>fredluneau</dc:creator>
      <dc:date>2021-05-20T13:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Operational data question</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-operational-data-question/m-p/4406507#M567454</link>
      <description>&lt;P&gt;When the primary datacenter's ISE node is online again, it will re-register to the current PAN, the PAN will prompt the node status (in Administration-System-Deployment-Deployment Nodes), it will prompt "Replication Stopped" "Please do a manual sync"&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;You can select this node, click Syncup, and wait for 10-20 minutes until "Node Status" turns green. At this time, all data is synchronized. You can choose a suitable time to switch PAN back to Primary DataCenter&lt;/P&gt;&lt;P&gt;1.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="0715.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/120897i4A0D8D7A7BBD228C/image-size/large?v=v2&amp;amp;px=999" role="button" title="0715.png" alt="0715.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;2.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="0755.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/120898iE195312F896DC0F7/image-size/large?v=v2&amp;amp;px=999" role="button" title="0755.png" alt="0755.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;3.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="0823.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/120896iF037E6ACC313974C/image-size/large?v=v2&amp;amp;px=999" role="button" title="0823.png" alt="0823.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;4.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="0912.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/120899i89D3136B15A7F126/image-size/large?v=v2&amp;amp;px=999" role="button" title="0912.png" alt="0912.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;5.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="1655.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/120900iC3B1379881A56C24/image-size/large?v=v2&amp;amp;px=999" role="button" title="1655.png" alt="1655.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH. &lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2021 09:57:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-operational-data-question/m-p/4406507#M567454</guid>
      <dc:creator>ilay</dc:creator>
      <dc:date>2021-05-21T09:57:02Z</dc:date>
    </item>
  </channel>
</rss>

