<?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 2.x: Failover ISE through API call? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502288#M517970</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please keep in mind this only works in a medium sized deployment or larger where you have dedicated policy services nodes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-0/admin_guide/b_ise_admin_guide_20/b_ise_admin_guide_20_chapter_010.html#ID616&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Feb 2018 15:11:08 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2018-02-08T15:11:08Z</dc:date>
    <item>
      <title>ISE 2.x: Failover ISE through API call?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502286#M517968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello Team,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My customer is asking for the following:&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;&lt;STRONG&gt;Is there a way to promote a Secondary Admin Node to Primary using an API Call? Basically we want to make a script that help us to promote a Secondary ISE node instead of using the GUI in "Administration &amp;gt; System &amp;gt; Deployment" path.&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it possible or in the road-map?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please advise.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 08:24:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502286#M517968</guid>
      <dc:creator>musultan</dc:creator>
      <dc:date>2018-02-08T08:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.x: Failover ISE through API call?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502287#M517969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no exposed API for this function.&amp;nbsp; We have a special option that can be configured on any non-PAN node to perform this function automatically under Administration &amp;gt; System &amp;gt; Deployment &amp;gt; PAN Failover&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 15:03:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502287#M517969</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2018-02-08T15:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.x: Failover ISE through API call?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502288#M517970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please keep in mind this only works in a medium sized deployment or larger where you have dedicated policy services nodes&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-0/admin_guide/b_ise_admin_guide_20/b_ise_admin_guide_20_chapter_010.html#ID616&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Feb 2018 15:11:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-x-failover-ise-through-api-call/m-p/3502288#M517970</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-02-08T15:11:08Z</dc:date>
    </item>
  </channel>
</rss>

