<?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 MSM422 taking IP from DHCP despite being set for static in M and MSM Series</title>
    <link>https://community.hpe.com/t5/m-and-msm-series/msm422-taking-ip-from-dhcp-despite-being-set-for-static/m-p/2389083#M122</link>
    <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm new to these forums so I hope this has gone into the right spot...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have been running an MSM765 with 16 MSM422s for a long time now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Every time i do a firmware update, we have all the addressing go screwy on the APs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have VLAN 2111 &lt;EM&gt;untagged&lt;/EM&gt; on the AP ports, and VLAN 3011 &lt;EM&gt;tagged&lt;/EM&gt; on the AP ports.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The APs all have reserved IPs on our DHCP server on VLAN 2111.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They all have the same static addresses configured under APName -&amp;gt; Provisioning -&amp;gt; Connectivity as the reservation on the DHCP server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Despite this, the APs are still chosing to take a DHCP address from VLAN 3011, instead of the untagged VLAN via either reservation or the static configuration that has been indicated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This has now become more than an inconvenience as we must update our firmware to support controller teaming, and my wireless network is unusable until I can get the APs sending RADIUS requests via the correct IP and VLAN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only thing that I can see that could be plausible, is that the DHCP system for the untagged VLAN is issuing IPs in the 172.21.129.0/255.255.255.128 range and IPs in the 172.21.0.0/255.255.255.128 range for the tagged VLAN... is it possible that the APs would be preferring the lower (numerically) address?&lt;/P&gt;</description>
    <pubDate>Sat, 11 Jun 2011 05:16:20 GMT</pubDate>
    <dc:creator>TGa</dc:creator>
    <dc:date>2011-06-11T05:16:20Z</dc:date>
    <item>
      <title>MSM422 taking IP from DHCP despite being set for static</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm422-taking-ip-from-dhcp-despite-being-set-for-static/m-p/2389083#M122</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm new to these forums so I hope this has gone into the right spot...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have been running an MSM765 with 16 MSM422s for a long time now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Every time i do a firmware update, we have all the addressing go screwy on the APs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have VLAN 2111 &lt;EM&gt;untagged&lt;/EM&gt; on the AP ports, and VLAN 3011 &lt;EM&gt;tagged&lt;/EM&gt; on the AP ports.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The APs all have reserved IPs on our DHCP server on VLAN 2111.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They all have the same static addresses configured under APName -&amp;gt; Provisioning -&amp;gt; Connectivity as the reservation on the DHCP server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Despite this, the APs are still chosing to take a DHCP address from VLAN 3011, instead of the untagged VLAN via either reservation or the static configuration that has been indicated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This has now become more than an inconvenience as we must update our firmware to support controller teaming, and my wireless network is unusable until I can get the APs sending RADIUS requests via the correct IP and VLAN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The only thing that I can see that could be plausible, is that the DHCP system for the untagged VLAN is issuing IPs in the 172.21.129.0/255.255.255.128 range and IPs in the 172.21.0.0/255.255.255.128 range for the tagged VLAN... is it possible that the APs would be preferring the lower (numerically) address?&lt;/P&gt;</description>
      <pubDate>Sat, 11 Jun 2011 05:16:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm422-taking-ip-from-dhcp-despite-being-set-for-static/m-p/2389083#M122</guid>
      <dc:creator>TGa</dc:creator>
      <dc:date>2011-06-11T05:16:20Z</dc:date>
    </item>
    <item>
      <title>Re: MSM422 taking IP from DHCP despite being set for static</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm422-taking-ip-from-dhcp-despite-being-set-for-static/m-p/2389087#M123</link>
      <description>Corretion on those addresses in the last paragraph... the subnet masks should be 255.255.128.0.</description>
      <pubDate>Sat, 11 Jun 2011 05:32:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm422-taking-ip-from-dhcp-despite-being-set-for-static/m-p/2389087#M123</guid>
      <dc:creator>TGa</dc:creator>
      <dc:date>2011-06-11T05:32:59Z</dc:date>
    </item>
  </channel>
</rss>

