<?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: WLC Configuration in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213730#M43534</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So its just a predefined thing on the controllers... &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; no other reasons .... ? Any link stating this is available ..~???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 25 Jun 2013 08:59:27 GMT</pubDate>
    <dc:creator>Prasan Venky</dc:creator>
    <dc:date>2013-06-25T08:59:27Z</dc:date>
    <item>
      <title>WLC Configuration</title>
      <link>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213728#M43532</link>
      <description>&lt;P&gt;Dear All,,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Waht is the exact reason behind the Management port and Service port of the controller`s IP subnet should be different..?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;KVS&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:17:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213728#M43532</guid>
      <dc:creator>Prasan Venky</dc:creator>
      <dc:date>2021-07-04T07:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Configuration</title>
      <link>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213729#M43533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well because things will break:)&lt;BR /&gt;&lt;BR /&gt;The service port is your out of band management and the two ports should not have any connectivity between the two or else you will start seeing issues. It's just how it's designed and its part of best practices.&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, 25 Jun 2013 07:30:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213729#M43533</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-06-25T07:30:53Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Configuration</title>
      <link>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213730#M43534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So its just a predefined thing on the controllers... &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; no other reasons .... ? Any link stating this is available ..~???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 25 Jun 2013 08:59:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213730#M43534</guid>
      <dc:creator>Prasan Venky</dc:creator>
      <dc:date>2013-06-25T08:59:27Z</dc:date>
    </item>
    <item>
      <title>Re: WLC Configuration</title>
      <link>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213731#M43535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; The management interface is the default interface for in-band management&amp;nbsp; of the controller and connectivity to enterprise services such as AAA&amp;nbsp; servers. It is also used for communications between the controller and&amp;nbsp; access points. The management interface has the only consistently&amp;nbsp; "pingable" in-band interface IP address on the controller. You can&amp;nbsp; access the controller's GUI by entering the controller's management&amp;nbsp; interface IP address in Internet Explorer's or Mozilla Firefox's address&amp;nbsp; field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;A name="wp1303889"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt; For CAPWAP, the controller requires one management interface to control&amp;nbsp; all inter-controller communications and one AP-manager interface to&amp;nbsp; control all controller-to-access point communications, regardless of the&amp;nbsp; number of ports. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The service port is controlled by the service-port&amp;nbsp; interface and is reserved for out-of-band management of the controller&amp;nbsp; and system recovery and maintenance in the event of a network failure.&amp;nbsp; It is also the only port that is active when the controller is in boot&amp;nbsp; mode. The service port is not capable of carrying 802.1Q tags, so it&amp;nbsp; must be connected to an access port on the neighbor switch. Use of the&amp;nbsp; service port is optional. &lt;/P&gt;&lt;P&gt;And both have diffrent ip subnet otherwise you will face issue.Moreover two interface can not have same subnet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jun 2013 06:03:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wlc-configuration/m-p/2213731#M43535</guid>
      <dc:creator>Ravi Singh</dc:creator>
      <dc:date>2013-06-27T06:03:13Z</dc:date>
    </item>
  </channel>
</rss>

