<?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 Interface Groups - interfaces unevenly distributed in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229399#M210792</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anthony,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is normal behaviour from WLC 7.2.x onwards when you using "interface groups". Refer this link for more detail &amp;amp; listed the key points of algorithm used for IP allocation.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bb4900.shtml?referring_site=smartnavRD"&gt;http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bb4900.shtml?referring_site=smartnavRD&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. When a client associates to a WLAN on a controller, an index is calculated based on the MAC address of the client and the number of interfaces in the interface group using a hashing algorithm.&lt;/P&gt;&lt;P&gt;2. Based on this index, an interface is assigned to the client.&lt;/P&gt;&lt;P&gt;3. Whenever this client joins the controller, the hashing algorithm always returns the same index and the client is assigned to the same interface.&lt;/P&gt;&lt;P&gt;4. If the interface is “dirty”, then a random index is generated and the interface is assigned based on that random index.&lt;/P&gt;&lt;P&gt;5. If that interface is still dirty, then a fall back to round robin implementation occurs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using 7.x code below 7.2 then it is more or less round-robin algorithm &amp;amp; you should see equally utilized subnets. But it has some drawbacks &amp;amp; cisco modified it in 7.2 onwards.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080b78900.shtml"&gt;http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080b78900.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Rasika&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Jul 2013 23:58:52 GMT</pubDate>
    <dc:creator>Rasika Nayanajith</dc:creator>
    <dc:date>2013-07-16T23:58:52Z</dc:date>
    <item>
      <title>Interface Groups - interfaces unevenly distributed</title>
      <link>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229397#M210790</link>
      <description>&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; We're leveraging interface groups to break up broadcast domains into 24 bit nets while still providing ample IP space to clients associated to a specific WLAN.&amp;nbsp; As I understand it the WLC should round-robin the interfaces to clients as they associate, however we are seeing this unevenly skewed where some interfaces are being overutilized and others underutilized.&amp;nbsp; I've attached a screenshot of our DHCP server which demonstrates this behavior for the networks provisioned to this WLAN.&lt;/P&gt;&lt;P&gt;Has anyone else experienced this and is there any way to correct it?&amp;nbsp; &lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Anthony&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:26:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229397#M210790</guid>
      <dc:creator>Anthony Poli</dc:creator>
      <dc:date>2021-07-04T07:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: Interface Groups - interfaces unevenly distributed</title>
      <link>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229398#M210791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well the WLC will calculate which interface it will use depending on the MAC address of the client. If you have added interfaces to the group, that can cause a skew also. In order to start fresh, you can remove and recreate the interface group or reboot the WLC. I wouldn't work about it since the WLC will mark the interface dirty if a client fails to revive an IP address.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 21:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229398#M210791</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-07-16T21:17:13Z</dc:date>
    </item>
    <item>
      <title>Interface Groups - interfaces unevenly distributed</title>
      <link>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229399#M210792</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anthony,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is normal behaviour from WLC 7.2.x onwards when you using "interface groups". Refer this link for more detail &amp;amp; listed the key points of algorithm used for IP allocation.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bb4900.shtml?referring_site=smartnavRD"&gt;http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bb4900.shtml?referring_site=smartnavRD&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. When a client associates to a WLAN on a controller, an index is calculated based on the MAC address of the client and the number of interfaces in the interface group using a hashing algorithm.&lt;/P&gt;&lt;P&gt;2. Based on this index, an interface is assigned to the client.&lt;/P&gt;&lt;P&gt;3. Whenever this client joins the controller, the hashing algorithm always returns the same index and the client is assigned to the same interface.&lt;/P&gt;&lt;P&gt;4. If the interface is “dirty”, then a random index is generated and the interface is assigned based on that random index.&lt;/P&gt;&lt;P&gt;5. If that interface is still dirty, then a fall back to round robin implementation occurs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are using 7.x code below 7.2 then it is more or less round-robin algorithm &amp;amp; you should see equally utilized subnets. But it has some drawbacks &amp;amp; cisco modified it in 7.2 onwards.&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080b78900.shtml"&gt;http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080b78900.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Rasika&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jul 2013 23:58:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/interface-groups-interfaces-unevenly-distributed/m-p/2229399#M210792</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2013-07-16T23:58:52Z</dc:date>
    </item>
  </channel>
</rss>

