<?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 MAC hash or round robin in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/mac-hash-or-round-robin/m-p/2007460#M33800</link>
    <description>&lt;P&gt;I am in the process of revamping our wireless solution. I am interested in VLAN pooling and am wondering if it is done round robin or with a hash. it is important for us to keep the same IP addresses so the MAC hash would be ideal over round robin in my attempts to keep users in the same VLAN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 05:16:54 GMT</pubDate>
    <dc:creator>Robert Steers</dc:creator>
    <dc:date>2021-07-04T05:16:54Z</dc:date>
    <item>
      <title>MAC hash or round robin</title>
      <link>https://community.cisco.com/t5/wireless/mac-hash-or-round-robin/m-p/2007460#M33800</link>
      <description>&lt;P&gt;I am in the process of revamping our wireless solution. I am interested in VLAN pooling and am wondering if it is done round robin or with a hash. it is important for us to keep the same IP addresses so the MAC hash would be ideal over round robin in my attempts to keep users in the same VLAN. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sent from Cisco Technical Support iPad App&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 05:16:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mac-hash-or-round-robin/m-p/2007460#M33800</guid>
      <dc:creator>Robert Steers</dc:creator>
      <dc:date>2021-07-04T05:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: MAC hash or round robin</title>
      <link>https://community.cisco.com/t5/wireless/mac-hash-or-round-robin/m-p/2007461#M33801</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Robert,&lt;/P&gt;&lt;P&gt;It all depends on the code version on your WLC.&lt;/P&gt;&lt;P&gt;If you are using 7.0.116.0 or 7.0.220.0 it will use round robin. (need to confirm for 7.0.220.0 though).&lt;/P&gt;&lt;P&gt;If you use 7.2 or 7.0.230.0 (or later) it will use an index and same clients will be mapped to same interface as long as the DHCP process is going fine.&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;Integration of VLAN Pooling or the VLAN Select feature in release 7.0.116 provided a solution to the restriction where the WLAN can be mapped to a single interface or multiple interfaces using an interface group. Wireless clients associating to this WLAN receive an IP address from a pool of subnets identified by the interfaces in a round robin fashion.&lt;/P&gt;&lt;P&gt;In WLC release 7.2, the VLAN Select feature (which is supported only on the newer WLCs like 5508, WiSM-2, 7500, and 2500) was modified and now supports VLAN Select with a new modified algorithm. In the previous implementation, using the round robin algorithm was causing clients to obtain new IP addresses on every re-association, thus depleting IP addresses fast from the available DHCP pools. The new algorithm is based on the Client’s MAC address and operates in this way:&lt;/P&gt;&lt;P&gt;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;Based on this index, an interface is assigned to the client.&lt;/P&gt;&lt;P&gt;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;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;If that interface is still dirty, then a fall back to round robin implementation occurs.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Note&lt;/STRONG&gt;: &lt;SPAN style="text-decoration: underline;"&gt;In order to support the new VLAN Select feature on legacy controllers (such as the 4400 Series, WiSM, and 2100 Series) with the same MAC-based algorithm, the VLAN Select feature was modified in release 7.0.230 and now operates in the same fashion as release 7.2.&lt;/SPAN&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Reference:&lt;A class="active_link" href="http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bb4900.shtml" rel="nofollow"&gt;http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080bb4900.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note please in underlined quote above it is metnioend that 7.0.230.0 uses same method as 7.2. having 7.0.220.0 not mentioned then I suppose that it follows same round robin as 7.0.116.0 but this needs to be confirmed in practice because documents are not always 100% accurate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, for your benefit, here is the link specified for hte feature for 7.0.116.0 version:&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://www.cisco.com/en/US/products/ps10315/products_tech_note09186a0080b78900.shtml" rel="nofollow"&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;&lt;/P&gt;&lt;P&gt;Amjad&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jun 2012 05:35:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/mac-hash-or-round-robin/m-p/2007461#M33801</guid>
      <dc:creator>Amjad Abdullah</dc:creator>
      <dc:date>2012-06-11T05:35:56Z</dc:date>
    </item>
  </channel>
</rss>

