<?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 IBNS 2.0 two radius servers in policy in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-two-radius-servers-in-policy/m-p/3604382#M496714</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;Did somebody manage to use two radius servers in Policy for dot1x?&lt;/P&gt;&lt;P&gt;We are doing a migration of clients and ISE and it would be helpful to check both servers and act on first access-accept.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am basing the idea on slides from Cisco Live Session:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://clnv.s3.amazonaws.com/2015/anz/pdf/BRKSEC-2691.pdf" style="font-size: 10pt;" title="https://clnv.s3.amazonaws.com/2015/anz/pdf/BRKSEC-2691.pdf"&gt;https://clnv.s3.amazonaws.com/2015/anz/pdf/BRKSEC-2691.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would be Concurrent Authentication + Differentiated Authentication at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried different ideas but I did not manage to get it to work until now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 examples:&lt;/P&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;&lt;P&gt;policy-map type control subscriber POLICY_Gi1/0/1&lt;/P&gt;&lt;P&gt; event session-started match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 authenticate using dot1x aaa authc-list RADIUS_NEW authz-list RADIUS_NEW priority 10 &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20 authenticate using dot1x aaa authc-list RADIUS_OLD authz-list RADIUS_OLD priority 15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt; event authentication-success match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 10 activate service-template DEFAULT_LINKSEC_POLICY_SHOULD_SECURE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;#####################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;policy-map type control subscriber POLICY_Gi1/0/1&lt;/P&gt;&lt;P&gt; event session-started match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 authenticate using dot1x aaa authc-list RADIUS_NEW authz-list RADIUS_NEW priority 10 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; 20 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 authenticate using dot1x aaa authc-list RADIUS_OLD authz-list RADIUS_OLD priority 15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt; event authentication-success match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 10 activate service-template DEFAULT_LINKSEC_POLICY_SHOULD_SECURE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;I am wondering if this is possible at all. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Jun 2018 13:39:35 GMT</pubDate>
    <dc:creator>dawid.karol.bednarczyk</dc:creator>
    <dc:date>2018-06-26T13:39:35Z</dc:date>
    <item>
      <title>IBNS 2.0 two radius servers in policy</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-two-radius-servers-in-policy/m-p/3604382#M496714</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;Did somebody manage to use two radius servers in Policy for dot1x?&lt;/P&gt;&lt;P&gt;We are doing a migration of clients and ISE and it would be helpful to check both servers and act on first access-accept.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am basing the idea on slides from Cisco Live Session:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://clnv.s3.amazonaws.com/2015/anz/pdf/BRKSEC-2691.pdf" style="font-size: 10pt;" title="https://clnv.s3.amazonaws.com/2015/anz/pdf/BRKSEC-2691.pdf"&gt;https://clnv.s3.amazonaws.com/2015/anz/pdf/BRKSEC-2691.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This would be Concurrent Authentication + Differentiated Authentication at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried different ideas but I did not manage to get it to work until now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2 examples:&lt;/P&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;&lt;P&gt;policy-map type control subscriber POLICY_Gi1/0/1&lt;/P&gt;&lt;P&gt; event session-started match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 authenticate using dot1x aaa authc-list RADIUS_NEW authz-list RADIUS_NEW priority 10 &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 20 authenticate using dot1x aaa authc-list RADIUS_OLD authz-list RADIUS_OLD priority 15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt; event authentication-success match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 10 activate service-template DEFAULT_LINKSEC_POLICY_SHOULD_SECURE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;#####################&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;policy-map type control subscriber POLICY_Gi1/0/1&lt;/P&gt;&lt;P&gt; event session-started match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 authenticate using dot1x aaa authc-list RADIUS_NEW authz-list RADIUS_NEW priority 10 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; 20 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10 authenticate using dot1x aaa authc-list RADIUS_OLD authz-list RADIUS_OLD priority 15&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt; event authentication-success match-all&lt;/P&gt;&lt;P&gt;&amp;nbsp; 10 class always do-until-failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 10 activate service-template DEFAULT_LINKSEC_POLICY_SHOULD_SECURE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;I am wondering if this is possible at all. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jun 2018 13:39:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-two-radius-servers-in-policy/m-p/3604382#M496714</guid>
      <dc:creator>dawid.karol.bednarczyk</dc:creator>
      <dc:date>2018-06-26T13:39:35Z</dc:date>
    </item>
    <item>
      <title>Re: IBNS 2.0 two radius servers in policy</title>
      <link>https://community.cisco.com/t5/network-access-control/ibns-2-0-two-radius-servers-in-policy/m-p/3604383#M496715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It sounds creative, but not sure why one would need such setup even for migration. Differentiated Auth is for using different RADIUS server for MAB and 802.1X so would not apply to this use case and frankly I don't think you can have IOS check multiple RADIUS servers for 802.1X unless you are trying to load-balance request. Also, note that concurrent auth is not supported if using ISE as RADIUS server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can elaborate on what you are trying to achieve at a higher level, we may be able to provide other options.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Jun 2018 23:42:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ibns-2-0-two-radius-servers-in-policy/m-p/3604383#M496715</guid>
      <dc:creator>howon</dc:creator>
      <dc:date>2018-06-26T23:42:24Z</dc:date>
    </item>
  </channel>
</rss>

