<?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 ISE mab authentication  with Avaya/Nortel switches in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045843#M209824</link>
    <description>&lt;P&gt;Currently using Cisco ISE 1.1 to authentication both dot1x and mab from Cisco switches. Both features are authenticating properly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we use a Nortel/Avaya switch for the authenticator, we are unable to authenticate using mac bypass (non-eap (or neap) in Avaya talk..). The correct authentication policy is found in the ISE, but the mac address is not found in the database. We know it is there because the same mac is authenticating with the Cisco switch. Dot1x authenticates properly from both the Cisco and Avaya authenticators. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could this be an issues with the username/password format in the Radius packet from the Cisco? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any assistance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kurt&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 02:27:10 GMT</pubDate>
    <dc:creator>Glnc66inc</dc:creator>
    <dc:date>2019-03-11T02:27:10Z</dc:date>
    <item>
      <title>ISE mab authentication  with Avaya/Nortel switches</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045843#M209824</link>
      <description>&lt;P&gt;Currently using Cisco ISE 1.1 to authentication both dot1x and mab from Cisco switches. Both features are authenticating properly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When we use a Nortel/Avaya switch for the authenticator, we are unable to authenticate using mac bypass (non-eap (or neap) in Avaya talk..). The correct authentication policy is found in the ISE, but the mac address is not found in the database. We know it is there because the same mac is authenticating with the Cisco switch. Dot1x authenticates properly from both the Cisco and Avaya authenticators. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could this be an issues with the username/password format in the Radius packet from the Cisco? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any assistance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kurt&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:27:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045843#M209824</guid>
      <dc:creator>Glnc66inc</dc:creator>
      <dc:date>2019-03-11T02:27:10Z</dc:date>
    </item>
    <item>
      <title>ISE mab authentication  with Avaya/Nortel switches</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045844#M209922</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kurt,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On your probe configuration do you have the radius probe configured? If so, one way to take a look at the radus packet and to decrypt the password will be to compare the two transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can take a capture by using the tcpdump tool under the Operations &amp;gt; Diagnostic tools &amp;gt; General Tools &amp;gt; TCPDump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can enter the filter "ip host &lt;SWITCHRADIUSSOURCEINTERF&gt;" after setting the option for raw packet data, once you are able to test with the Cisco switch, then stop the capture, download and do it again using the avaya switch.&lt;/SWITCHRADIUSSOURCEINTERF&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can then open the packet capture using wireshark, and in the preferences tab you can select the radius protocol and set the shared secret which will decrypt the password to see what it is, you can also do a comparison as to how the packet is being sent from to the other.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Aug 2012 20:17:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045844#M209922</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-08-22T20:17:56Z</dc:date>
    </item>
    <item>
      <title>ISE mab authentication  with Avaya/Nortel switches</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045845#M210009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The problem is with the ISE platform. As it turns out, Cisco is not using the correct radius attribute (as stated in the radius RFC).They are using a cisco attribute that other vendors are not using.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This bug will be fixed in the 2.x release this spring.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Feb 2013 20:32:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045845#M210009</guid>
      <dc:creator>Glnc66inc</dc:creator>
      <dc:date>2013-02-28T20:32:14Z</dc:date>
    </item>
    <item>
      <title>ISE mab authentication  with Avaya/Nortel switches</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045846#M210085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kurt, do you have a bug ID for this? It will be nice to have this reference&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 16:51:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045846#M210085</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2013-03-01T16:51:17Z</dc:date>
    </item>
    <item>
      <title>ISE mab authentication  with Avaya/Nortel switches</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045847#M210172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; As requested...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;SPAN style="font-family: Courier New; font-size: 14pt;"&gt;&lt;A href="https://mail.ex2.secureserver.net/owa/redir.aspx?C=Wa9A9fW0NkKmJNxEsf2FHyY6wt5D6s8IDcwl7dCG2_KUn_6roDm53alGmJcGk-4zSUPjprmkRqU.&amp;amp;URL=http%3a%2f%2ftools.cisco.com%2fSupport%2fBugToolKit%2fsearch%2fgetBugDetails.do%3fmethod%3dfetchBugDetails%26bugId%3dCSCuc22732" target="_blank"&gt;&lt;SPAN style="font-size: 10pt;"&gt;http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fet&lt;/SPAN&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="font-family: Courier New; font-size: 14pt;"&gt;&lt;A href="https://mail.ex2.secureserver.net/owa/redir.aspx?C=Wa9A9fW0NkKmJNxEsf2FHyY6wt5D6s8IDcwl7dCG2_KUn_6roDm53alGmJcGk-4zSUPjprmkRqU.&amp;amp;URL=http%3a%2f%2ftools.cisco.com%2fSupport%2fBugToolKit%2fsearch%2fgetBugDetails.do%3fmethod%3dfetchBugDetails%26bugId%3dCSCuc22732" target="_blank"&gt;&lt;SPAN style="font-size: 10pt;"&gt;chBugDetails&amp;amp;bugId=&lt;/SPAN&gt;&lt;/A&gt;&lt;A href="https://www.cisco.com/cisco/psn/bssprt/bss?searchType=bstbugidsearch&amp;amp;page=bstBugDetail&amp;amp;BugID=CSCuc22732" target="_blank"&gt;CSCuc22732&lt;/A&gt;&lt;/SPAN&gt;&lt;/PRE&gt;&lt;PRE&gt;&lt;SPAN style="font-size: 10pt; font-family: Courier New; "&gt; &lt;/SPAN&gt;&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;MAB works from a cisco switch because the cisco switch places the mac address in the calling-station-attribute and the user-name attribute. The Cisco ISE platform is looking at the calling-station attribute to find the user name.This is the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The radius RFC says the user name must be in the user-name attribute. The calling-station-attribute is not a required field and is used for the phone number of a voip phone. Basically, the ISE platform is looking at the wrong field for the mac address. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Mar 2013 18:59:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045847#M210172</guid>
      <dc:creator>Glnc66inc</dc:creator>
      <dc:date>2013-03-01T18:59:17Z</dc:date>
    </item>
    <item>
      <title>ISE mab authentication  with Avaya/Nortel switches</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045848#M210259</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for sharing that Kurt (+5) from me. Also, if your issue is resolved please mark the thread as close.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Mar 2013 02:28:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-mab-authentication-with-avaya-nortel-switches/m-p/2045848#M210259</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2013-03-08T02:28:11Z</dc:date>
    </item>
  </channel>
</rss>

