<?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 Profiling using NMAP with L2 Adjacent Endpoints in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-profiling-using-nmap-with-l2-adjacent-endpoints/m-p/3517491#M496900</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Per direct email response to same query...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;I believe the info provided for origin al guide is still valid, although honestly I have not tested such in years.&amp;nbsp; The assumption is that PSN is rarely or never L2 adjacent to the endpoints it supports.&amp;nbsp; I would not rely on that assumption to avoid basic profiling.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;If RADIUS is configured to ISE, then ISE will acquire MAC and IPs via Calling Station ID and Framed IP.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;ARP cache alone will not acquire DHCP data.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;I do not understand the need to upgrade switches to collect profile data.&amp;nbsp; You may be confusing basic profile collection with Device Sensor feature, an advanced option to optimize profile data collection from switches/wireless controllers.&amp;nbsp; Device Sensor is not a requirement, although it is recommended to optimize collection and reduce ISE load.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jun 2018 12:35:24 GMT</pubDate>
    <dc:creator>Craig Hyps</dc:creator>
    <dc:date>2018-06-19T12:35:24Z</dc:date>
    <item>
      <title>ISE Profiling using NMAP with L2 Adjacent Endpoints</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-using-nmap-with-l2-adjacent-endpoints/m-p/3517490#M496899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;&amp;nbsp;&amp;nbsp; I have a quick question. Can ISE (PSN) gather IP-to-MAC address bindings using its own local ARP table if it is directly connected (L2 adjacent or same VLAN/subnet) to end-points it is scanning with NMAP, hence avoid having configuring switches and probes for profiling?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;If that can happen could customers use this as an alternative design if they don’t want to configure any commands for ISE probes on switches? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;I have read the below from the ISE Profiling Design Guide – not sure I have interpreted this correctly hence my question to you. Can we view the local ARP cache of a PSN node by the way?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;""" START """"&lt;/P&gt;&lt;DIV class="section" style="background-color: rgb(100.000000%, 100.000000%, 100.000000%);"&gt;&lt;DIV class="column"&gt;&lt;OL start="0" style="list-style-type: none;"&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11.000000pt; font-family: 'Times';"&gt;NMAP is based on a known IP address. If the NMAP probe collects attributes for an endpoint but cannot correlate that to a specific MAC address, that data is discarded. If the Policy Service node is on the same segment as the endpoint it is scanning, it can learn the IP-to-MAC address binding from its local ARP cache and add the endpoint directly into the Internal Endpoints database. Consequently, it is required to learn the IP-to-MAC address binding via another probe &lt;/SPAN&gt;&lt;SPAN style="font-size: 11.000000pt; font-family: 'Times'; font-weight: bold;"&gt;prior &lt;/SPAN&gt;&lt;SPAN style="font-size: 11.000000pt; font-family: 'Times';"&gt;to collecting NMAP probe data. Probes that can be used to provide this information include the following: &lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11.000000pt; font-family: 'Times';"&gt;RADIUS (via Framed-IP-Address) &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11.000000pt; font-family: 'Times';"&gt;DHCP (via dhcp-requested-address) &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 11.000000pt; font-family: 'Times';"&gt;SNMP Query (via SNMP polling) &lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;""""&amp;nbsp; END '""""&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Kind Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 11.0pt;"&gt;Kostas&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2018 22:13:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-using-nmap-with-l2-adjacent-endpoints/m-p/3517490#M496899</guid>
      <dc:creator>kpapadop@cisco.com</dc:creator>
      <dc:date>2018-06-18T22:13:07Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiling using NMAP with L2 Adjacent Endpoints</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiling-using-nmap-with-l2-adjacent-endpoints/m-p/3517491#M496900</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Per direct email response to same query...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;I believe the info provided for origin al guide is still valid, although honestly I have not tested such in years.&amp;nbsp; The assumption is that PSN is rarely or never L2 adjacent to the endpoints it supports.&amp;nbsp; I would not rely on that assumption to avoid basic profiling.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;If RADIUS is configured to ISE, then ISE will acquire MAC and IPs via Calling Station ID and Framed IP.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;ARP cache alone will not acquire DHCP data.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-GB" style="font-size: 11.0pt; color: #1f497d;"&gt;I do not understand the need to upgrade switches to collect profile data.&amp;nbsp; You may be confusing basic profile collection with Device Sensor feature, an advanced option to optimize profile data collection from switches/wireless controllers.&amp;nbsp; Device Sensor is not a requirement, although it is recommended to optimize collection and reduce ISE load.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 12:35:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiling-using-nmap-with-l2-adjacent-endpoints/m-p/3517491#M496900</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2018-06-19T12:35:24Z</dc:date>
    </item>
  </channel>
</rss>

