<?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 DHCP issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5016407#M266553</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have setup WLC as showing in drawing below;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DHCP (10.133.139.0/24)&amp;nbsp; on wlc, and this is working fine with DMLZ Area.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dyunanda_0-1707725368977.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/210080i6135D4A9A6FD4754/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dyunanda_0-1707725368977.png" alt="dyunanda_0-1707725368977.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;and we have issue when we want to add new segment in GBC area with segment 10.133.136.0/24. client in GBC tenant AP still get same ip addres with DMLZ area. 10.133.139.0/24 from DHCP in WLC (even we add new pool in WLC DHCP for 10.133.136.0/24 ).&amp;nbsp; do you have any advise to solve this issue ? where to put DHCP ? may be other solution.&amp;nbsp;&lt;/P&gt;&lt;P&gt;currently we have 3 network segment (10.133.139.0, 10.133.138.0 and 10.133.136.0 ) with same vlan210. we cannot change this VLAN configuration becuase client only give us 1 vlan for 3 segment above.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards&amp;nbsp;&lt;/P&gt;&lt;P&gt;DY&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 12 Feb 2024 08:18:22 GMT</pubDate>
    <dc:creator>dyunanda</dc:creator>
    <dc:date>2024-02-12T08:18:22Z</dc:date>
    <item>
      <title>DHCP issue</title>
      <link>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5016407#M266553</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have setup WLC as showing in drawing below;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DHCP (10.133.139.0/24)&amp;nbsp; on wlc, and this is working fine with DMLZ Area.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="dyunanda_0-1707725368977.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/210080i6135D4A9A6FD4754/image-size/medium?v=v2&amp;amp;px=400" role="button" title="dyunanda_0-1707725368977.png" alt="dyunanda_0-1707725368977.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;and we have issue when we want to add new segment in GBC area with segment 10.133.136.0/24. client in GBC tenant AP still get same ip addres with DMLZ area. 10.133.139.0/24 from DHCP in WLC (even we add new pool in WLC DHCP for 10.133.136.0/24 ).&amp;nbsp; do you have any advise to solve this issue ? where to put DHCP ? may be other solution.&amp;nbsp;&lt;/P&gt;&lt;P&gt;currently we have 3 network segment (10.133.139.0, 10.133.138.0 and 10.133.136.0 ) with same vlan210. we cannot change this VLAN configuration becuase client only give us 1 vlan for 3 segment above.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards&amp;nbsp;&lt;/P&gt;&lt;P&gt;DY&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 08:18:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5016407#M266553</guid>
      <dc:creator>dyunanda</dc:creator>
      <dc:date>2024-02-12T08:18:22Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP issue</title>
      <link>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5016522#M266560</link>
      <description>&lt;P&gt;Since all APs managed by same WLC and that WLC SVI for vlan 210 is in 10.133.139.0/24 range you always get IP address from same range. Without creating 3 SVI (vlans on WLC) I do no think you can solve it easily.&lt;/P&gt;
&lt;P&gt;HTH&lt;BR /&gt;Rasika&lt;BR /&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Mon, 12 Feb 2024 12:00:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5016522#M266560</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2024-02-12T12:00:51Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP issue</title>
      <link>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5017004#M266598</link>
      <description>&lt;P&gt;Hi Rasika,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for reply,&amp;nbsp;&lt;/P&gt;&lt;P&gt;if we move DHCP server from WLC to windows server and put ip helper address in Client switch (10.133.136.252 and 139.252 ) and disable DHCP centeral . is it possible to solve it ? or please advise me if you have any?&amp;nbsp;&lt;/P&gt;&lt;P&gt;it's really appreciated your help .&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&amp;nbsp;&lt;/P&gt;&lt;P&gt;DY&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 01:55:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5017004#M266598</guid>
      <dc:creator>dyunanda</dc:creator>
      <dc:date>2024-02-13T01:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: DHCP issue</title>
      <link>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5017596#M266614</link>
      <description>&lt;P&gt;I believe traffic is centrally switched. That is those APs are in local mode and traffic is tunnel to that WLC.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In that scenario, you have to have 3 dynamic interfaces on your WLC in order to assign users into 3 different subnets&lt;/P&gt;
&lt;P&gt;HTH&lt;BR /&gt;Rasika&lt;BR /&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2024 12:08:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/dhcp-issue/m-p/5017596#M266614</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2024-02-13T12:08:46Z</dc:date>
    </item>
  </channel>
</rss>

