<?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 and restart the second ISE server which hasn't been active in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216281#M592735</link>
    <description>&lt;P&gt;it's a budget thing and keep been getting delay and need to restore secondary for now&lt;/P&gt;</description>
    <pubDate>Mon, 28 Oct 2024 16:41:35 GMT</pubDate>
    <dc:creator>MonkeyBear007</dc:creator>
    <dc:date>2024-10-28T16:41:35Z</dc:date>
    <item>
      <title>ISE 2.4 and restart the second ISE server which hasn't been active for</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216261#M592728</link>
      <description>&lt;P&gt;We have one primary PAN ISE in 2.4 one blade server is is Admin / Monitor and Second blade has the policy&lt;BR /&gt;Don't ask why we are still using 2.4&lt;/P&gt;&lt;P&gt;I want to add the Secondary PAN which hasn't been active over 1 year&amp;nbsp;&lt;BR /&gt;I should just be able connect the secondary ISE Admin/monitor and Policy to the network&amp;nbsp;&lt;BR /&gt;It should auto&amp;nbsp; see each other and start using Both primary and secondary?&lt;BR /&gt;Anything I need to watch out for since they have been disconnect so long?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 16:11:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216261#M592728</guid>
      <dc:creator>MonkeyBear007</dc:creator>
      <dc:date>2024-10-28T16:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and restart the second ISE server which hasn't been active</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216264#M592730</link>
      <description>&lt;P&gt;I have no idea how it will behave after that long time. But as a precaution I would reinstall the secondary and add it back to the deployment. Or even better, use this opportunity to build a new deployment based on 3.2 and move to that.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 16:19:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216264#M592730</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2024-10-28T16:19:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and restart the second ISE server which hasn't been active</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216272#M592731</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;U&gt;&lt;FONT color="#FF6600"&gt;&lt;EM&gt; &amp;nbsp;&amp;gt;....Don't ask why we are still using 2.4&lt;/EM&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;BR /&gt;&amp;nbsp; We should actually , because it is an important point&amp;nbsp;&lt;BR /&gt;&amp;nbsp; You risk new network equipment becoming incompatible with ISE ; or software&lt;BR /&gt;&amp;nbsp; For instance modern 9800 wireless controller with latest software is only validated&lt;BR /&gt;&amp;nbsp; against the current ISE versions (this may start to happen to other equipment which you have too&lt;BR /&gt;&amp;nbsp; or perhaps has already happened)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;U&gt;&lt;FONT color="#FF6600"&gt;&lt;EM&gt; &amp;gt;...I want to add the Secondary PAN which hasn't been active over 1 year&amp;nbsp;&lt;/EM&gt;&lt;/FONT&gt;&lt;/U&gt;&lt;BR /&gt;&amp;nbsp;And we should seriously wonder about that too , because standard ISE&amp;nbsp; production use then becomes&lt;BR /&gt;&amp;nbsp;not valid&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; - There is no way out then trying (which with decent network management , including&amp;nbsp; ISE should not have happened).&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;First scrutinize the &lt;STRONG&gt;boot process&lt;/STRONG&gt; of the secondary through a (the)&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;STRONG&gt; &amp;nbsp; &amp;nbsp;console&lt;/STRONG&gt; ; check if there are no fatal errors or indicators for that during the boot process&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Once it has booted without problems , check the status of the applications using :&amp;nbsp;&lt;STRONG&gt;show application status ise&lt;BR /&gt;&lt;/STRONG&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Then look at the primary and check if the secondary has become available ,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 16:29:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216272#M592731</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-10-28T16:29:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and restart the second ISE server which hasn't been active</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216281#M592735</link>
      <description>&lt;P&gt;it's a budget thing and keep been getting delay and need to restore secondary for now&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 16:41:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216281#M592735</guid>
      <dc:creator>MonkeyBear007</dc:creator>
      <dc:date>2024-10-28T16:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and restart the second ISE server which hasn't been active</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216336#M592736</link>
      <description>&lt;P&gt;it's the way it is here&lt;BR /&gt;They should of went with 2.7 before license model change&lt;BR /&gt;We are waiting budget for ISE 3.x and we don't use cisco wireless controller and switch to Cisco Merial wireless.&lt;BR /&gt;Budget is a big factory&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 17:50:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216336#M592736</guid>
      <dc:creator>MonkeyBear007</dc:creator>
      <dc:date>2024-10-28T17:50:35Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and restart the second ISE server which hasn't been active</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216341#M592737</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &lt;U&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;gt;...Budget is a big factory&lt;/EM&gt;&lt;/U&gt;&lt;BR /&gt;&amp;nbsp; - Yeah but a failing and incompatible NAC deployment becomes a collapsing factory....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;M.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 17:56:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-and-restart-the-second-ise-server-which-hasn-t-been/m-p/5216341#M592737</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2024-10-28T17:56:18Z</dc:date>
    </item>
  </channel>
</rss>

