<?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 Switch location based DACL in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700544#M507831</link>
    <description>&lt;P&gt;Hi experts&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With the variable in ISE 2.4, I can tie a name of a DACL to an attribute of an endpoint. Is there a way to tie the name of the DACL to the NAD switch location?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The goal is to implement a location based DACL. There are near 200 sites, and the DACL limit the traffic to a local site only. The easiest way to find out where the endpoint is is to use the connected switch location.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In stead of using device.location as a condition for these 200 sites, I would rather use a DACL name = Device.location in the authorization profile.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you have any recommendation?&lt;/P&gt;</description>
    <pubDate>Tue, 04 Sep 2018 16:28:53 GMT</pubDate>
    <dc:creator>harrzhan</dc:creator>
    <dc:date>2018-09-04T16:28:53Z</dc:date>
    <item>
      <title>Switch location based DACL</title>
      <link>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700544#M507831</link>
      <description>&lt;P&gt;Hi experts&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With the variable in ISE 2.4, I can tie a name of a DACL to an attribute of an endpoint. Is there a way to tie the name of the DACL to the NAD switch location?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The goal is to implement a location based DACL. There are near 200 sites, and the DACL limit the traffic to a local site only. The easiest way to find out where the endpoint is is to use the connected switch location.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In stead of using device.location as a condition for these 200 sites, I would rather use a DACL name = Device.location in the authorization profile.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you have any recommendation?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 16:28:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700544#M507831</guid>
      <dc:creator>harrzhan</dc:creator>
      <dc:date>2018-09-04T16:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: Switch location based DACL</title>
      <link>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700591#M507832</link>
      <description>&lt;P&gt;I haven't tested this out, but I have done something similar using a local ACL on the switches at each location.&amp;nbsp; The switches would have a local ACL called "Local_Access_Only" that is customized for the location and ISE would apply the ACL to the session.&amp;nbsp; So I am not applying a DACL, but applying an ACL that is on the switch.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 04 Sep 2018 17:28:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700591#M507832</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-09-04T17:28:45Z</dc:date>
    </item>
    <item>
      <title>Re: Switch location based DACL</title>
      <link>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700600#M507833</link>
      <description>Thanks for the answer. However, the number of switches is too big to make it manageable. Adding one additional line, I would have to go to all the swtiches.&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Sep 2018 17:33:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700600#M507833</guid>
      <dc:creator>harrzhan</dc:creator>
      <dc:date>2018-09-04T17:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: Switch location based DACL</title>
      <link>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700602#M507834</link>
      <description>That can all be automated assuming you are managing the switches with any modern management software.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 04 Sep 2018 17:35:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/switch-location-based-dacl/m-p/3700602#M507834</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-09-04T17:35:07Z</dc:date>
    </item>
  </channel>
</rss>

