<?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 Radius fallback on 2960 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434705#M88092</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;You hve to take care of the following rules before applying the active-standby node in ISE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;You can specify two Monitoring ISE nodes on an ISE network and create an active-standby pair. Once the active-standby pair is defined, the following rules apply:&lt;/P&gt;&lt;P&gt; &lt;A name="wp1101530" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;All configuration changes must be made on the primary Monitoring ISE node. The secondary node is read-only.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1101531" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;Configuration changes made to the primary node are automatically replicated on the secondary node.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1101532" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;Both the primary and secondary nodes are listed as log collectors to which all other nodes send logs.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1151751" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;The ISE dashboard is the main entry point for monitoring and troubleshooting. Monitoring information is displayed on the dashboard from the primary Monitoring ISE node. If the primary node goes down, the information is served from the secondary node.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1176498" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;Backing up and purging monitoring data is not part of a standard ISE node backup process. You must configure repositories for backup and data purging on both the primary and secondary Monitoring ISE nodes, using the same repositories for each.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more details, Kindly look:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_dis_deploy.html"&gt;http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_dis_deploy.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;BR /&gt;Gurpreet S Puri &lt;BR /&gt; &lt;BR /&gt;**************************** &lt;BR /&gt;Keep Smiling, Peace &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; &lt;BR /&gt;**************************** &lt;BR /&gt; &lt;BR /&gt;(Please Rate Helpful Post)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Feb 2014 11:12:04 GMT</pubDate>
    <dc:creator>Gurpreet Puri</dc:creator>
    <dc:date>2014-02-12T11:12:04Z</dc:date>
    <item>
      <title>Radius fallback on 2960</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434704#M88089</link>
      <description>&lt;P&gt;Hi, I have ISE 1.2 and catalyst 2960&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 2 ISE node, the 2 ISE is PSN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normaly user are authenticated on ISE1(192.168.1.1), if ISE1 is not available, user must be authenticated on ISE2(&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;192.168.5.1)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once ISE1 become available, the user must be authenticated on ISE1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the command that I used, but it does not work&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;radius-server dead-criteria time 5 tries 3&lt;/P&gt;&lt;P&gt;radius-server host 192.168.1.1 auth-port 1812 acct-port 1813 key Abcd123&lt;/P&gt;&lt;P&gt;radius-server host 192.168.5.1 auth-port 1812 acct-port 1813 key Abcd123&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please how can I configure it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 04:23:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434704#M88089</guid>
      <dc:creator>nicanor00</dc:creator>
      <dc:date>2019-03-11T04:23:38Z</dc:date>
    </item>
    <item>
      <title>Radius fallback on 2960</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434705#M88092</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;You hve to take care of the following rules before applying the active-standby node in ISE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;You can specify two Monitoring ISE nodes on an ISE network and create an active-standby pair. Once the active-standby pair is defined, the following rules apply:&lt;/P&gt;&lt;P&gt; &lt;A name="wp1101530" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;All configuration changes must be made on the primary Monitoring ISE node. The secondary node is read-only.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1101531" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;Configuration changes made to the primary node are automatically replicated on the secondary node.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1101532" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;Both the primary and secondary nodes are listed as log collectors to which all other nodes send logs.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1151751" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;The ISE dashboard is the main entry point for monitoring and troubleshooting. Monitoring information is displayed on the dashboard from the primary Monitoring ISE node. If the primary node goes down, the information is served from the secondary node.&lt;/P&gt;&lt;P&gt; &lt;A name="wp1176498" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 0px 0em 7px 0.25in; text-indent: -0.25in; background-color: #ffffff;"&gt;•&lt;IMG border="0" height="2" src="http://www.cisco.com/en/US/i/templates/blank.gif" width="19" /&gt;Backing up and purging monitoring data is not part of a standard ISE node backup process. You must configure repositories for backup and data purging on both the primary and secondary Monitoring ISE nodes, using the same repositories for each.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more details, Kindly look:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_dis_deploy.html"&gt;http://www.cisco.com/en/US/docs/security/ise/1.0/user_guide/ise10_dis_deploy.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;BR /&gt;Gurpreet S Puri &lt;BR /&gt; &lt;BR /&gt;**************************** &lt;BR /&gt;Keep Smiling, Peace &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; &lt;BR /&gt;**************************** &lt;BR /&gt; &lt;BR /&gt;(Please Rate Helpful Post)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Feb 2014 11:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434705#M88092</guid>
      <dc:creator>Gurpreet Puri</dc:creator>
      <dc:date>2014-02-12T11:12:04Z</dc:date>
    </item>
    <item>
      <title>Radius fallback on 2960</title>
      <link>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434706#M88094</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All this have been already done&lt;/P&gt;&lt;P&gt;Configuration is OK on the 2 ISE distributed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISE1 : primary admin primary monitoring and PSN&lt;/P&gt;&lt;P&gt;ISE2 : secondary admin secondary monitoring and PSN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The goal now is to configure the switch to send authentication on the right ISE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;The primary PSN should be ISE1, then when ISE1 is not available ISE2 become primary&amp;nbsp; then once ISE1 become available, ISE1 must become primary again&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hw can I configure it ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Feb 2014 14:26:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/radius-fallback-on-2960/m-p/2434706#M88094</guid>
      <dc:creator>nicanor00</dc:creator>
      <dc:date>2014-02-12T14:26:35Z</dc:date>
    </item>
  </channel>
</rss>

