<?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 Re: IP addressing in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611163#M212734</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One first example could be the fact that APs by default are not configured for any syslog server and they will just broadcast syslog messages on the same subnet.&lt;/P&gt;&lt;P&gt;If using too many APs on the same subnet as the management interface, this could create extra traffic load hitting the WLC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, by keeping the management IP of the WLC on a different subnet from the APs, you may be able to implement more granular security policies in terms of access to the devices for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fede&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;If&amp;nbsp; this helps you and/or answers your question please mark the question as&amp;nbsp; "answered" and/or rate it, so other users can easily find it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 04 Jan 2011 11:09:14 GMT</pubDate>
    <dc:creator>Federico Ziliotto</dc:creator>
    <dc:date>2011-01-04T11:09:14Z</dc:date>
    <item>
      <title>IP addressing</title>
      <link>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611162#M212733</link>
      <description>&lt;P&gt;we are going to install 20 AP with 2 WC.&lt;/P&gt;&lt;P&gt;the company that will install the devices said: it is a best practice to choose the management IPs of the AP in one subnet and the management IPs of the controllers in another subnet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is this true? any explanation why ?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 02:37:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611162#M212733</guid>
      <dc:creator>ohassairi</dc:creator>
      <dc:date>2021-07-04T02:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: IP addressing</title>
      <link>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611163#M212734</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One first example could be the fact that APs by default are not configured for any syslog server and they will just broadcast syslog messages on the same subnet.&lt;/P&gt;&lt;P&gt;If using too many APs on the same subnet as the management interface, this could create extra traffic load hitting the WLC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, by keeping the management IP of the WLC on a different subnet from the APs, you may be able to implement more granular security policies in terms of access to the devices for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fede&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;If&amp;nbsp; this helps you and/or answers your question please mark the question as&amp;nbsp; "answered" and/or rate it, so other users can easily find it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 04 Jan 2011 11:09:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611163#M212734</guid>
      <dc:creator>Federico Ziliotto</dc:creator>
      <dc:date>2011-01-04T11:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: IP addressing</title>
      <link>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611164#M212735</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you configure APs and WLC management IPs in the same subnet, the APs won't be able to join the WLC as layer 2 CAPWAP mode is no longer supported:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/customer/docs/wireless/controller/7.0/configuration/guide/c70ovrv.html#wp1069102"&gt;http://www.cisco.com/en/US/customer/docs/wireless/controller/7.0/configuration/guide/c70ovrv.html#wp1069102&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Zhenning&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jan 2011 03:05:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611164#M212735</guid>
      <dc:creator>zhenningx</dc:creator>
      <dc:date>2011-01-05T03:05:28Z</dc:date>
    </item>
    <item>
      <title>Re: IP addressing</title>
      <link>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611165#M212736</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;/PRE&gt;&lt;/P&gt;&lt;P&gt;it is a best practice to choose the management IPs of the AP in one subnet and the management IPs of the controllers in another subnet.&lt;/P&gt;Whoever in management said this needs to read the deployment guide.&amp;nbsp; Cisco recommends the Management IP address and the AP-Manager IP address to be IN THE SAME SUBNET.&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jan 2011 03:31:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611165#M212736</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2011-01-05T03:31:52Z</dc:date>
    </item>
    <item>
      <title>Re: IP addressing</title>
      <link>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611166#M212737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the ratings.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Jan 2011 08:31:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ip-addressing/m-p/1611166#M212737</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2011-01-05T08:31:05Z</dc:date>
    </item>
  </channel>
</rss>

