<?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: Cisco ISE MAB Authentication Problem in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845749#M473599</link>
    <description>&lt;P&gt;Thank you Timothy, so how do I write a policy set specifically for the SG500 MAB. Because the positive sign&amp;nbsp; here is that ISE successfully receives the MAC addresses.&amp;nbsp; Like how do you think the custom device profile should be created with conditions that will match MAC addresses from SG500 switches.&lt;/P&gt;</description>
    <pubDate>Fri, 26 Apr 2019 06:57:53 GMT</pubDate>
    <dc:creator>andrew.agaba</dc:creator>
    <dc:date>2019-04-26T06:57:53Z</dc:date>
    <item>
      <title>Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844865#M473592</link>
      <description>&lt;P&gt;Hello Colleagues,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The challenge I have this is authenticating and authorising devices connected to SG500-52P switches using MAB.&lt;/P&gt;&lt;P&gt;The ISE v2.3 receives the MAC addresses but does not process any defined policy set but the default deny.&lt;/P&gt;&lt;P&gt;Yet when these same devices are connected to other switches, ISE v2.3 receives the MAC addresses and successfully authenticates and authorises them against policy sets defined.&lt;/P&gt;&lt;P&gt;Question is, how can I create get ISE v2.3 to authenticate and authorise devices connected to these SG500-52P switches using MAB.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2019 07:57:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844865#M473592</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-25T07:57:36Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844951#M473593</link>
      <description />
      <pubDate>Thu, 25 Apr 2019 09:54:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844951#M473593</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-25T09:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844953#M473594</link>
      <description />
      <pubDate>Thu, 25 Apr 2019 09:55:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844953#M473594</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-25T09:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844957#M473595</link>
      <description>This is a radius log for when a device connected to the SG500 switch fails</description>
      <pubDate>Thu, 25 Apr 2019 09:57:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844957#M473595</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-25T09:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844958#M473596</link>
      <description>This is a radius log for the same device connected to another switch succeeds with MAB</description>
      <pubDate>Thu, 25 Apr 2019 09:58:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3844958#M473596</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-25T09:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845201#M473598</link>
      <description>&lt;P&gt;MAB fails on the SG500 because Internal Endpoints is not queried as the identity store and I suspect it is because of the RADIUS attribute the switch is sending to ISE.&amp;nbsp; It succeeds because other switches are sending RADIUS: Service-type = Callcheck.&amp;nbsp; You'll have to create a custom device profile for the SG500 that describes how that particular switch does MAB.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Apr 2019 15:10:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845201#M473598</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2019-04-25T15:10:15Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845749#M473599</link>
      <description>&lt;P&gt;Thank you Timothy, so how do I write a policy set specifically for the SG500 MAB. Because the positive sign&amp;nbsp; here is that ISE successfully receives the MAC addresses.&amp;nbsp; Like how do you think the custom device profile should be created with conditions that will match MAC addresses from SG500 switches.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 06:57:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845749#M473599</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-26T06:57:53Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845921#M473601</link>
      <description>&lt;P&gt;It finally worked, thanks again Timothy.&amp;nbsp;I had to create a custom policy set for Devices with MAC addresses originating from SG500 switches as you said. The policy set was created using help from this post as well:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/sg500-nad-config/ta-p/3643438" target="_blank"&gt;https://community.cisco.com/t5/security-documents/sg500-nad-config/ta-p/3643438&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Apr 2019 10:15:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845921#M473601</guid>
      <dc:creator>andrew.agaba</dc:creator>
      <dc:date>2019-04-26T10:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE MAB Authentication Problem</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845940#M473603</link>
      <description>Have you looked at this&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.cisco.com/t5/security-documents/ise-third-party-nad-profiles-and-configs/ta-p/3648719" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-third-party-nad-profiles-and-configs/ta-p/3648719&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Apr 2019 10:44:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mab-authentication-problem/m-p/3845940#M473603</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-04-26T10:44:09Z</dc:date>
    </item>
  </channel>
</rss>

