<?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 - basic profiling / 802.1X with Avaya 4850 / 4950 switches ? in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-basic-profiling-802-1x-with-avaya-4850-4950-switches/m-p/3867128#M472503</link>
    <description>&lt;P&gt;Folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Got a customer inquiring about ISE basic profiling and 802.1x using Avaya 4850 / 4950 switches. If posture is feasible, that'd be even better.&amp;nbsp; Im aware they're not explicitly listed on the 2.4 interoperability matrix.&amp;nbsp; Any experiencies or suggestions are more than welcome.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Cristian Venegas&lt;/P&gt;
&lt;P&gt;Consulting Systems Engineeer&lt;/P&gt;
&lt;P&gt;Cisco&lt;/P&gt;</description>
    <pubDate>Tue, 04 Jun 2019 01:55:15 GMT</pubDate>
    <dc:creator>Cristian Venegas</dc:creator>
    <dc:date>2019-06-04T01:55:15Z</dc:date>
    <item>
      <title>ISE - basic profiling / 802.1X with Avaya 4850 / 4950 switches ?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-basic-profiling-802-1x-with-avaya-4850-4950-switches/m-p/3867128#M472503</link>
      <description>&lt;P&gt;Folks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Got a customer inquiring about ISE basic profiling and 802.1x using Avaya 4850 / 4950 switches. If posture is feasible, that'd be even better.&amp;nbsp; Im aware they're not explicitly listed on the 2.4 interoperability matrix.&amp;nbsp; Any experiencies or suggestions are more than welcome.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Cristian Venegas&lt;/P&gt;
&lt;P&gt;Consulting Systems Engineeer&lt;/P&gt;
&lt;P&gt;Cisco&lt;/P&gt;</description>
      <pubDate>Tue, 04 Jun 2019 01:55:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-basic-profiling-802-1x-with-avaya-4850-4950-switches/m-p/3867128#M472503</guid>
      <dc:creator>Cristian Venegas</dc:creator>
      <dc:date>2019-06-04T01:55:15Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - basic profiling / 802.1X with Avaya 4850 / 4950 switches ?</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-basic-profiling-802-1x-with-avaya-4850-4950-switches/m-p/3874689#M472504</link>
      <description>&lt;P&gt;Profiling is for identifying endpoints. Avaya may not support device sensors etc. But you could still use RADIUS, DHCP, SNMP, HTTP redirect/SPAN etc. Please check out the ISE profiling desing guide to understand what type of endpoints and what we need to gather from the endpoints.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/security-documents/ise-profiling-design-guide/ta-p/3739456" target="_blank"&gt;https://community.cisco.com/t5/security-documents/ise-profiling-design-guide/ta-p/3739456&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I have covered the profiling in detail in my Cisco Live presentation below.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.ciscolive.com/global/on-demand-library.html?search=ise&amp;amp;search.event=ciscoliveanz2019#/session/1540777879698001OXRU" target="_self" rel="nofollow noopener noreferrer"&gt;&lt;STRONG&gt;Are Your Endpoints/IOT Assets Safe? - BRKSEC-2725&lt;/STRONG&gt;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Krishnan&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2019 01:07:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-basic-profiling-802-1x-with-avaya-4850-4950-switches/m-p/3874689#M472504</guid>
      <dc:creator>kthiruve</dc:creator>
      <dc:date>2019-06-18T01:07:50Z</dc:date>
    </item>
  </channel>
</rss>

