<?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: SDA IP Pool limits in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538391#M1707</link>
    <description>&lt;P&gt;You can use biggest IP pool /16 like more with more VLAN for your SSID 400 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;OIther side&amp;nbsp; - i am more intrested :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;400 SSID - is very huge numbers what is the use case.&lt;/P&gt;
&lt;P&gt;how many controllers ?&lt;/P&gt;
&lt;P&gt;how big is the deployment ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 25 Jan 2022 17:25:41 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2022-01-25T17:25:41Z</dc:date>
    <item>
      <title>SDA IP Pool limits</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538354#M1706</link>
      <description>&lt;P&gt;Hello, community.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm a bit confused with terminology in the DNA-C datasheet (&lt;A href="https://www.connext.com.mx/wp-content/uploads/2020/11/DNA-Analytics-and-Assurance-1.1.pdf" target="_blank" rel="noopener"&gt;https://www.connext.com.mx/wp-content/uploads/2020/11/DNA-Analytics-and-Assurance-1.1.pdf&lt;/A&gt;), hopefully, I will find an answer here...&lt;BR /&gt;&lt;BR /&gt;There is a limit of 100x IP Pools supported by&amp;nbsp;DN2-HW-APL...does it apply to the "Global" IP Pools or the "Sub-IP Pools/Reserved Subnets" as well?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;By "Sub-IP Pool" I mean the "subnet" we "reserve" out of "Global" IP Pool for specific purposes, such as a device type, VN, etc...&lt;BR /&gt;I have a potential design where I need to accommodate nearly 400 unique SSIDs per site and not sure if I will be able to do it with SDA.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 17:10:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538354#M1706</guid>
      <dc:creator>MaxSL</dc:creator>
      <dc:date>2022-01-25T17:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: SDA IP Pool limits</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538391#M1707</link>
      <description>&lt;P&gt;You can use biggest IP pool /16 like more with more VLAN for your SSID 400 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;OIther side&amp;nbsp; - i am more intrested :&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;400 SSID - is very huge numbers what is the use case.&lt;/P&gt;
&lt;P&gt;how many controllers ?&lt;/P&gt;
&lt;P&gt;how big is the deployment ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 17:25:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538391#M1707</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-01-25T17:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: SDA IP Pool limits</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538453#M1708</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&amp;nbsp;The limit is per site. As per your box, it seems that it goes up to 500 fabric sites and 64 VN per site. Then, your intensional design will not be possible as DNAC only support one IP pool per SSID. (Each SSID must be attached to only one IP pool).&lt;/P&gt;&lt;P&gt;Look at Table 14. Scale and hardware specifications of the document:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A title="https://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/dna-center/nb-06-dna-center-data-sheet-cte-en.html" href="https://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/dna-center/nb-06-dna-center-data-sheet-cte-en.html" target="_self"&gt;https://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/dna-center/nb-06-dna-center-data-sheet-cte-en.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 18:07:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538453#M1708</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2022-01-25T18:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: SDA IP Pool limits</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538497#M1709</link>
      <description>&lt;P&gt;WLC is 9800-40.&lt;BR /&gt;The use case is the following: there is a WAP in the hotel room and I need to restrict bandwidth from that specific WAP based on the room class.&lt;/P&gt;&lt;P&gt;The original idea I had is to dedicate an SSID per room and apply "Policer" (to limit available bandwidth) per SSID...But if there is a 100 IP Pool limit on SDA I will probably have to use a single SSID/WLAN and multiple Policy profiles, so I could mix them under a Policy Tag. And then "tag" different WAPs with different Policy tags...Single SSID is not optimal due to "sticky client" though.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 18:31:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538497#M1709</guid>
      <dc:creator>MaxSL</dc:creator>
      <dc:date>2022-01-25T18:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: SDA IP Pool limits</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538614#M1710</link>
      <description>&lt;P&gt;You can do Per Client QoS on the WLC.&amp;nbsp; However, this may note available on the DNAC&amp;nbsp; profile. This is something that makes me sad about DNAC cause I expect&amp;nbsp; to see the very same option I have on WLC gui, in the DNAC gui.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A title="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/215441-configure-qos-rate-limiting-on-catalyst.html" href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/215441-configure-qos-rate-limiting-on-catalyst.html" target="_self"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/215441-configure-qos-rate-limiting-on-catalyst.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Jan 2022 18:53:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4538614#M1710</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2022-01-25T18:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: SDA IP Pool limits</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4539074#M1711</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can create an IP Pool for each bandwidth "class", and then do a IP based firewall policy with different configuration according to the IP subnet.&lt;/P&gt;&lt;P&gt;Or a better solution would be to have one SSID for the entire guest-net and then different EAP-PEAP usernames per room. Then use this to map the client to a policy or IP Pool.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jan 2022 08:18:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sda-ip-pool-limits/m-p/4539074#M1711</guid>
      <dc:creator>rasmus.elmholt</dc:creator>
      <dc:date>2022-01-26T08:18:48Z</dc:date>
    </item>
  </channel>
</rss>

