<?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 Another way to determine in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677810#M55261</link>
    <description>&lt;P&gt;Another way to determine where the wifi client is located is to use a nas-identifier which you can specify on an AP group or&amp;nbsp; WLAN (by default it's the WLC name) and you can use rules in ISE that make use of the nas-identifier radius attribute. The disadvantages with NAS-Identifier is that you have to configure the AP group nas identifier on the WLC, it cannot be done by template from PI and you cannot do a report in ISE using a nas identifier.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Jun 2015 15:16:51 GMT</pubDate>
    <dc:creator>M. Wisely</dc:creator>
    <dc:date>2015-06-08T15:16:51Z</dc:date>
    <item>
      <title>ISE - Network Devices - Split larger IP range into smaller ones</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677809#M55256</link>
      <description>&lt;P&gt;Hi.&lt;/P&gt;&lt;P&gt;We have several businesses, each of them have assigned a class B subnet, for example 172.21.xx /16, 172.27.xx /16, etc.&lt;/P&gt;&lt;P&gt;But each business has several locations, that normally has a class C subnet assigned to it&lt;/P&gt;&lt;P&gt;This is a structure I would very much like to build in ISE also.&lt;BR /&gt;This is very practical when making authorization profiles and you need to pinpoint where the customer are trying to access the WIFI. You know, to assign the correct VLAN, etc.&lt;/P&gt;&lt;P&gt;But when I try to do just that, I get this error:&lt;BR /&gt;Failed to create network device - given IP subnet overlaps with existing network device: Business1.&lt;/P&gt;&lt;P&gt;Why oh why?&lt;/P&gt;&lt;P&gt;Is there a way around this? If not, PLEASE implement this feature!&lt;/P&gt;&lt;P&gt;It was no problem doing this in ACS, so why should it be a problem here?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:47:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677809#M55256</guid>
      <dc:creator>dal</dc:creator>
      <dc:date>2019-03-11T05:47:21Z</dc:date>
    </item>
    <item>
      <title>Another way to determine</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677810#M55261</link>
      <description>&lt;P&gt;Another way to determine where the wifi client is located is to use a nas-identifier which you can specify on an AP group or&amp;nbsp; WLAN (by default it's the WLC name) and you can use rules in ISE that make use of the nas-identifier radius attribute. The disadvantages with NAS-Identifier is that you have to configure the AP group nas identifier on the WLC, it cannot be done by template from PI and you cannot do a report in ISE using a nas identifier.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2015 15:16:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677810#M55261</guid>
      <dc:creator>M. Wisely</dc:creator>
      <dc:date>2015-06-08T15:16:51Z</dc:date>
    </item>
    <item>
      <title>Hello.This is an excellent</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677811#M55266</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;This is an excellent tip! I was not aware of this, and I will try it out for sure. If it works as intended, it will solve my problem.&lt;BR /&gt;It would of course be easier to split the subnet, I cannot understand why this is not possible.&lt;/P&gt;&lt;P&gt;But I guess that is a feature we have to wait for, and I need a solution now.&lt;/P&gt;&lt;P&gt;Doing it from the WLC's is OK, since I have trouble assigning AP's into AP Groups made in PI anyway (from PI, not in the WLC's)&lt;/P&gt;&lt;P&gt;Thanks again, I will let you know how it turned out.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Jun 2015 15:29:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677811#M55266</guid>
      <dc:creator>dal</dc:creator>
      <dc:date>2015-06-08T15:29:19Z</dc:date>
    </item>
    <item>
      <title>you can also have a option of</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677812#M55269</link>
      <description>&lt;P&gt;you can also have a option of location to group NAD&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jun 2015 10:53:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677812#M55269</guid>
      <dc:creator>Venkatesh Attuluri</dc:creator>
      <dc:date>2015-06-11T10:53:29Z</dc:date>
    </item>
    <item>
      <title>Hello.Thanks for the tip.But</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677813#M55274</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;&lt;P&gt;Thanks for the tip.&lt;/P&gt;&lt;P&gt;But how do I do that, exactly?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jun 2015 18:58:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677813#M55274</guid>
      <dc:creator>dal</dc:creator>
      <dc:date>2015-06-15T18:58:45Z</dc:date>
    </item>
    <item>
      <title>This worked like a charm! :</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677814#M55275</link>
      <description>&lt;P&gt;This worked like a charm! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Thanks again.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Aug 2015 09:36:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677814#M55275</guid>
      <dc:creator>dal</dc:creator>
      <dc:date>2015-08-25T09:36:53Z</dc:date>
    </item>
    <item>
      <title>I add all my NADs with a /32</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677815#M55278</link>
      <description>&lt;P&gt;I add all my NADs with a /32 address to limit auth access. I also add them to a group and then use the group in my authz rules.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Sep 2015 10:28:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-network-devices-split-larger-ip-range-into-smaller-ones/m-p/2677815#M55278</guid>
      <dc:creator>phosawyer</dc:creator>
      <dc:date>2015-09-02T10:28:02Z</dc:date>
    </item>
  </channel>
</rss>

