<?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.4 : ERS API : Reload command in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019510#M454273</link>
    <description>Nice idea.&lt;BR /&gt;&lt;BR /&gt;I am just wondering how to override the confirmations that you are asked.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;When you type reload, you are asked :&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Save the current ADE-OS running configuration? (yes/no) [yes] ?&lt;BR /&gt;&lt;BR /&gt;Generating configuration...&lt;BR /&gt;&lt;BR /&gt;Saved the ADE-OS running configuration to startup successfully&lt;BR /&gt;&lt;BR /&gt;Continue with reboot? [y/n]</description>
    <pubDate>Tue, 28 Jan 2020 13:54:21 GMT</pubDate>
    <dc:creator>gillessapene</dc:creator>
    <dc:date>2020-01-28T13:54:21Z</dc:date>
    <item>
      <title>ISE 2.4 : ERS API : Reload command</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019478#M454269</link>
      <description>&lt;P&gt;I still have issue with the scheduled reports that I export to a NAS. Sometimes, they remain "pending" and the only way to get rid of them is to reload the ISE server. I am thinking to automate the "reload" on a monthly basis.&lt;/P&gt;&lt;P&gt;I was wondering if there is a way to schedule the "reload" of an ISE without using ssh, typing "reload" and answering to the 2 questions/confirmations . I went through the "External RESTful Services (ERS) Online SDK" but didn't find anything about the "reload" command.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2020 13:12:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019478#M454269</guid>
      <dc:creator>gillessapene</dc:creator>
      <dc:date>2020-01-28T13:12:27Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 : ERS API : Reload command</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019496#M454271</link>
      <description>&lt;P&gt;See below post&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2020 15:17:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019496#M454271</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2020-01-28T15:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 : ERS API : Reload command</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019510#M454273</link>
      <description>Nice idea.&lt;BR /&gt;&lt;BR /&gt;I am just wondering how to override the confirmations that you are asked.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;When you type reload, you are asked :&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Save the current ADE-OS running configuration? (yes/no) [yes] ?&lt;BR /&gt;&lt;BR /&gt;Generating configuration...&lt;BR /&gt;&lt;BR /&gt;Saved the ADE-OS running configuration to startup successfully&lt;BR /&gt;&lt;BR /&gt;Continue with reboot? [y/n]</description>
      <pubDate>Tue, 28 Jan 2020 13:54:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019510#M454273</guid>
      <dc:creator>gillessapene</dc:creator>
      <dc:date>2020-01-28T13:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 : ERS API : Reload command</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019582#M454276</link>
      <description>Honestly now that I am thinking about it more you probably would not want to do this.  Reason being is the fact that there is an order of operations you should take when rebooting nodes.  You should stop services prior to rebooting.  My recommendation would be to manually handle this and work with TAC to identify why they get hung.</description>
      <pubDate>Tue, 28 Jan 2020 15:16:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019582#M454276</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2020-01-28T15:16:39Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 : ERS API : Reload command</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019609#M454279</link>
      <description>I would suggest an alternate solution which isn't an immediate fix, but the correct way to go about this.  Work with TAC and ensure that this is a logged bug and drive a resolution to the problem in future patches.  If it is production impacting you would be able to ask TAC for an interim hotfix to address the issue.&lt;BR /&gt;&lt;BR /&gt;You should not have to rely on reloading nodes as a fix to an issue, no one here would consider that a viable workaround to the issue.  &lt;BR /&gt;&lt;BR /&gt;Reloads are not accessible via the API as you found out.  You also cannot force a reload on the CLI without prompts.  A python script could easily handle the input from the SSH session and automate this for you though.</description>
      <pubDate>Tue, 28 Jan 2020 15:48:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-ers-api-reload-command/m-p/4019609#M454279</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2020-01-28T15:48:15Z</dc:date>
    </item>
  </channel>
</rss>

