<?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 6504 WISM 2 - Interface group and how it load balances in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019384#M32308</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking for some guidance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Due to network consideration I need to apply 1x /22 and 1x&amp;nbsp; /24 dynamic interfaces in an interface group.&lt;/P&gt;&lt;P&gt;My understanding is that the WISM will assign clients to a VLAN/Dynamic interface on a Round Robin basis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question is what will happen when the /24 subnet becomes full?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How does the WISM understand that the /24 subnet is full and will it then only assign clients to the /22 vlan/dynamic interface?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 18:36:37 GMT</pubDate>
    <dc:creator>bigbobmcquade</dc:creator>
    <dc:date>2021-07-05T18:36:37Z</dc:date>
    <item>
      <title>6504 WISM 2 - Interface group and how it load balances</title>
      <link>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019384#M32308</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking for some guidance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Due to network consideration I need to apply 1x /22 and 1x&amp;nbsp; /24 dynamic interfaces in an interface group.&lt;/P&gt;&lt;P&gt;My understanding is that the WISM will assign clients to a VLAN/Dynamic interface on a Round Robin basis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question is what will happen when the /24 subnet becomes full?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How does the WISM understand that the /24 subnet is full and will it then only assign clients to the /22 vlan/dynamic interface?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 18:36:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019384#M32308</guid>
      <dc:creator>bigbobmcquade</dc:creator>
      <dc:date>2021-07-05T18:36:37Z</dc:date>
    </item>
    <item>
      <title>Re: 6504 WISM 2 - Interface group and how it load balances</title>
      <link>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019479#M32309</link>
      <description>Hi There,&lt;BR /&gt;&lt;BR /&gt;See explanation from Cisco below:&lt;BR /&gt;&lt;BR /&gt;Controller marks VLAN as dirty when the clients are unable to receive IP address using DHCP. The VLAN interface is marked as dirty based on two methods:&lt;BR /&gt;&lt;BR /&gt;Aggressive Method—When only one failure is counted per association per client and controller marks VLAN as dirty interface when a failure occurs three times for a client or for three different clients.&lt;BR /&gt;&lt;BR /&gt;Non-Aggressive Method—When only one failure is counted per association per client and controller marks VLAN as a dirty interface only when three or more clients fail.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_010100100.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/wireless/controller/7-4/configuration/guides/consolidated/b_cg74_CONSOLIDATED/b_cg74_CONSOLIDATED_chapter_010100100.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;lt;&amp;lt;&amp;lt; Pls remember to rate all useful responses &amp;gt;&amp;gt;&amp;gt;</description>
      <pubDate>Tue, 28 Jan 2020 13:15:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019479#M32309</guid>
      <dc:creator>Jurgens L</dc:creator>
      <dc:date>2020-01-28T13:15:07Z</dc:date>
    </item>
    <item>
      <title>Re: 6504 WISM 2 - Interface group and how it load balances</title>
      <link>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019516#M32311</link>
      <description>&lt;P&gt;Jurgens, many thanks for taking the time to respond.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The issue we are seeing is that a small number of WIndows clients are not receiving a DHCP address assignment. They get stuck in a weird state. Once I remove them from the WISM they receive IP address from /22 network as expected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would this be related with a failed DHCP assignment from /24 vlan/dynamic interface before the /24 subnet is marked as "Dirty"?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bob&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jan 2020 14:08:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019516#M32311</guid>
      <dc:creator>bigbobmcquade</dc:creator>
      <dc:date>2020-01-28T14:08:18Z</dc:date>
    </item>
    <item>
      <title>Re: 6504 WISM 2 - Interface group and how it load balances</title>
      <link>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019584#M32313</link>
      <description>I fear only a "debug client macaddressoftheclient" will show what really is happening, while it's happening.</description>
      <pubDate>Tue, 28 Jan 2020 15:18:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4019584#M32313</guid>
      <dc:creator>patoberli</dc:creator>
      <dc:date>2020-01-28T15:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: 6504 WISM 2 - Interface group and how it load balances</title>
      <link>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4040737#M32314</link>
      <description>&lt;P&gt;Thanks for taking the time to respond. Unfortunately was unable to garner logs as you suggested.&lt;/P&gt;&lt;P&gt;In the end we increased the size of the smaller subnet range to ensure the address space is not being exhausted.&lt;/P&gt;&lt;P&gt;No complaints of issue since. To be continued... &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2020 09:46:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/6504-wism-2-interface-group-and-how-it-load-balances/m-p/4040737#M32314</guid>
      <dc:creator>bigbobmcquade</dc:creator>
      <dc:date>2020-03-05T09:46:16Z</dc:date>
    </item>
  </channel>
</rss>

