<?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.0, COA and profiling access points on switch in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179814#M554932</link>
    <description>&lt;P&gt;Ideally once you connect the AP it will profiled as cisco device since its 1st time seen. ISE will then trigger nmap scan along with other checks. once all the checks completed and ap is detected&amp;nbsp; (e.g. aironet 2600) ise will trigger coa for the switch to reauthenticate the device and assign the corresponding policy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So port bouce not required generally.&amp;nbsp; now i have seen cases where this automation doesn't take place and port bouce needed. So use it as fallback.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please remember to rate useful posts&lt;/P&gt;</description>
    <pubDate>Mon, 04 Sep 2017 18:30:15 GMT</pubDate>
    <dc:creator>Mohammed al Baqari</dc:creator>
    <dc:date>2017-09-04T18:30:15Z</dc:date>
    <item>
      <title>ISE 2.0, COA and profiling access points on switch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179657#M554919</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We want to dynamically profile access-points&amp;nbsp;on 2960-switches when they are plugged in to a standard port. Were using 1832i and 2702i. The profiling seems to work fine, they access-point is profiled with the correct endpoint profile, and gets put into the right identity group. The problem is however that MAB happens first, so the access-point goes into a quaratine VLAN. I have attached a COA Port bounce to this profile, but it doesnt seem to happen. If i cant bounce the port, i cant get the access point into the vlan tied to the identity group.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have a clue as to why i cant bounce the port? The device sensor and ISE seems to be doing everything right as to classification - the question is, is it possible to get ISE to assign vlan as it profiles the device? Because here it seems MAB happens before ISE is done profiling, and then its too late, at least if the port wont bounce.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Port config:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;switchport mode access&lt;BR /&gt;authentication event fail action authorize vlan 666&lt;BR /&gt;authentication event no-response action authorize vlan 666&lt;BR /&gt;authentication order dot1x mab&lt;BR /&gt;authentication priority dot1x mab&lt;BR /&gt;authentication port-control auto&lt;BR /&gt;authentication violation protect&lt;BR /&gt;mab&lt;BR /&gt;dot1x pae authenticator&lt;BR /&gt;spanning-tree portfast&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Global:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;aaa authentication dot1x default group ISE&lt;BR /&gt;aaa authorization network default group ISE&lt;BR /&gt;aaa accounting dot1x default start-stop group ISE&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;device-sensor accounting&lt;BR /&gt;device-sensor notify all-changes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;dot1x system-auth-control&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;radius-server vsa send accounting&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:33:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179657#M554919</guid>
      <dc:creator>trondaker</dc:creator>
      <dc:date>2020-02-21T18:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.0, COA and profiling access points on switch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179723#M554920</link>
      <description>&lt;P&gt;You don't see to have CoA on your 2960 switch. Depending on your switch IOS, it might not support CoA.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sample config:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;aaa server radius dynamic-author&lt;BR /&gt; client 10.10.10.10 server-key&amp;nbsp;*******&lt;BR /&gt; server-key&amp;nbsp;*******&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check cisco feature navigator to see if your IOS version on 2960 supports CoA&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 13:10:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179723#M554920</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2017-09-04T13:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.0, COA and profiling access points on switch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179802#M554922</link>
      <description>Thanks for your reply! That is indeed missing, adding it now and testing tomorrow. This is a 2960X, but also need it on a 2960+, seems to have the command in our current IOS at least.&lt;BR /&gt;&lt;BR /&gt;But is this way of doing it correct? Or is it possible to do this without bouncing the port?&lt;BR /&gt;</description>
      <pubDate>Mon, 04 Sep 2017 17:52:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179802#M554922</guid>
      <dc:creator>trondaker</dc:creator>
      <dc:date>2017-09-04T17:52:12Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.0, COA and profiling access points on switch</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179814#M554932</link>
      <description>&lt;P&gt;Ideally once you connect the AP it will profiled as cisco device since its 1st time seen. ISE will then trigger nmap scan along with other checks. once all the checks completed and ap is detected&amp;nbsp; (e.g. aironet 2600) ise will trigger coa for the switch to reauthenticate the device and assign the corresponding policy.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So port bouce not required generally.&amp;nbsp; now i have seen cases where this automation doesn't take place and port bouce needed. So use it as fallback.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please remember to rate useful posts&lt;/P&gt;</description>
      <pubDate>Mon, 04 Sep 2017 18:30:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-0-coa-and-profiling-access-points-on-switch/m-p/3179814#M554932</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2017-09-04T18:30:15Z</dc:date>
    </item>
  </channel>
</rss>

