<?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 - Cisco IP Phone profiling in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216420#M176710</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; According to the release notes, the 2960 don't support this feature, only the 3750 and 3560.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/15.0_2_se/release/notes/OL25301.html#wp1047686"&gt;http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/15.0_2_se/release/notes/OL25301.html#wp1047686&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been using 3750-X and 3560 with device sensor for a month now, and it profiles Cisco IP phones in less than a minute, most of the times in 20 seconds or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if it helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Jul 2013 21:12:22 GMT</pubDate>
    <dc:creator>Eduardo Aliaga</dc:creator>
    <dc:date>2013-07-04T21:12:22Z</dc:date>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216419#M176698</link>
      <description>&lt;P&gt;Dears&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i have issues profiling the Cisco ip phones , it's profiled as "PROFILED"&amp;nbsp; the only probes i enabled on switches and ISE is Radius and now i know the i need to enable CDP device sensor so it can be sent via Radius accounting but i can't find the commend "device-sensor account"&amp;nbsp; on my switch , i use "&lt;/P&gt;&lt;P&gt;Version 15.0(2)SE3" and WS-C2960S-24PS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;any ideas ?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Mar 2019 00:42:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216419#M176698</guid>
      <dc:creator>eng.malak</dc:creator>
      <dc:date>2019-03-13T00:42:00Z</dc:date>
    </item>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216420#M176710</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; According to the release notes, the 2960 don't support this feature, only the 3750 and 3560.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/15.0_2_se/release/notes/OL25301.html#wp1047686"&gt;http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/15.0_2_se/release/notes/OL25301.html#wp1047686&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been using 3750-X and 3560 with device sensor for a month now, and it profiles Cisco IP phones in less than a minute, most of the times in 20 seconds or so.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate if it helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Jul 2013 21:12:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216420#M176710</guid>
      <dc:creator>Eduardo Aliaga</dc:creator>
      <dc:date>2013-07-04T21:12:22Z</dc:date>
    </item>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216421#M176731</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so what is the alternative ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jul 2013 20:05:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216421#M176731</guid>
      <dc:creator>eng.malak</dc:creator>
      <dc:date>2013-07-05T20:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216422#M176808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you could use another type of profiling, for example, DHCP profiling, then you would have to use DHCP relay pointing to your ISE&amp;nbsp; to collect the information, but I have never tested it and don't know how reliable and how fast to profile it's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would recommend to use static profiling, you could get the list of all MAC addresses from your Call Manager and then import them into ISE. The benefit it's that static profiling doens't use advanced licenses, only standard licenses, so it's cheaper to do it this way&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate it helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: Eduardo Aliaga&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Jul 2013 20:24:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216422#M176808</guid>
      <dc:creator>Eduardo Aliaga</dc:creator>
      <dc:date>2013-07-05T20:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216423#M176867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;You should be able to use the dhcp relay feature because the hostname of the phone is contained in the dhcp request, I am sure that there is a condition already identified for the cisco ip phone hostname, and if there isnt you should be able to write one yourself.&lt;BR /&gt;&lt;BR /&gt;Event though the device sensor isnt really supported on the 2960s i have had good luck with in the labs, however I havent proposed this as a solution for either of my customers, just a real head scratcher I wanted to share with you.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Jul 2013 05:54:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216423#M176867</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-07-07T05:54:55Z</dc:date>
    </item>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216424#M176967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;i read once that i should let the ISE to updates its profiler via Internet , any idea about how to do this ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Jul 2013 09:34:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216424#M176967</guid>
      <dc:creator>eng.malak</dc:creator>
      <dc:date>2013-07-07T09:34:32Z</dc:date>
    </item>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216425#M177034</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ISE will update automatically it's OUI database, using Profiler Feed Service in version 1.2 that should be released this month.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Jul 2013 13:17:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216425#M177034</guid>
      <dc:creator>Octavian Szolga</dc:creator>
      <dc:date>2013-07-07T13:17:45Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216426#M177098</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What about ISE 1.1.4. ?&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Jul 2013 13:47:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216426#M177098</guid>
      <dc:creator>eng.malak</dc:creator>
      <dc:date>2013-07-07T13:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216427#M177183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;At this point I dont think the feed service is a critical issue for any cisco ip phone deployments that have been in service for quite some time, Where the feed service really comes into play is the latest smartphones and the profiling characteristics they fall under. For cisco ip phones you should be able to write a simple policy and have this tested fairly easily. If you go to the profiling conditions you should be able to see which attributes (or checks) that ISE performs for each cisco ip phone. I am sure the dhcp atttribute is one of the checks that you can leverage.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 07 Jul 2013 21:24:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216427#M177183</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2013-07-07T21:24:36Z</dc:date>
    </item>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216428#M177252</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would like to inform you that 2960 does not support this feature. For profiling IP phones on ISE please follow the instruction given in the below link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://techzone.cisco.com/t5/Unified-Controller-Based-WLC/Wireless-BYOD-for-FlexConnect-Deployment-Guide/ta-p/239326"&gt;https://techzone.cisco.com/t5/Unified-Controller-Based-WLC/Wireless-BYOD-for-FlexConnect-Deployment-Guide/ta-p/239326&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Jul 2013 02:25:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216428#M177252</guid>
      <dc:creator>Ravi Singh</dc:creator>
      <dc:date>2013-07-08T02:25:19Z</dc:date>
    </item>
    <item>
      <title>ISE - Cisco IP Phone profiling</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216429#M177300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With ISE Release 1.2*, Cisco is delivering,&amp;nbsp; a unique feed service that provides new and updated profiles for various IP&amp;nbsp; enabled devices when vendors release new devices. So ISE customers will be able&amp;nbsp; to recognize new devices, in addition to a multitude of other network attached&amp;nbsp; devices such as printers, video cameras, and specialized mobile computing&amp;nbsp; devices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco works with various vendors, partners,&amp;nbsp; customers, etc. to profile the multitude of IP enabled devices that are expected&amp;nbsp; to be deployed in various customer environments and create profiles for these.&amp;nbsp; These profiles are made available through the Cisco Feed Service. An ISE server*&amp;nbsp; that is configured to connect to the Feed Service establishes a secure&amp;nbsp; connection with cloud based Feed Service. The various profiles on the Feed&amp;nbsp; Service are then automatically downloaded to the ISE server, thus providing ISE&amp;nbsp; customers the ability to stay abreast and detect various IP enabled devices that&amp;nbsp; connect to their network. The Feed Service will be available with the release of&amp;nbsp; ISE 1.2* software release and is part of the Advanced&amp;nbsp; License.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Jul 2013 12:10:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cisco-ip-phone-profiling/m-p/2216429#M177300</guid>
      <dc:creator>Venkatesh Attuluri</dc:creator>
      <dc:date>2013-07-09T12:10:02Z</dc:date>
    </item>
  </channel>
</rss>

