<?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 WiSM Service IP vs Management IP in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wism-service-ip-vs-management-ip/m-p/1758278#M162443</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Hamilan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please check the following two links:&lt;/P&gt;&lt;P&gt;1) management interface&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117168"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117168&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&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="wp1326669"&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;2) service &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/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117020"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117020&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;he 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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- now with WISM the situation is little bit different.&lt;/P&gt;&lt;P&gt;WISM Service port is used also for carrying communication between WISM module and 720 Supervisor.&lt;/P&gt;&lt;P&gt;the communication is carried using WCP protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- managment , is the WLC access IP that you can telnet / HTTP. and also all intercontroller communication carried over management IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trying to answer your questions:&lt;/P&gt;&lt;P&gt;1) Which IP is uded to communicate AP and which used for data? &lt;/P&gt;&lt;P&gt;the communication between AP's and WLC is done using AP-Manager interface.&lt;/P&gt;&lt;P&gt;except discovery request sent on management.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now data clients are carried inside LWAPP/CAPWAP tunnel.&lt;/P&gt;&lt;P&gt;so client connect to AP.&lt;/P&gt;&lt;P&gt;AP tunnel that client to WLC using the LWAPP/CAPWAP tunnel. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) which range wireless client will get? &lt;/P&gt;&lt;P&gt;this depends on which VLAN's you configure on WLC.&lt;/P&gt;&lt;P&gt;you can map the WLAN to managment interface -&amp;gt;&amp;gt; so clients are in same VLAN as management.&lt;/P&gt;&lt;P&gt;or you can map it to any dynamic interface (new VLAN) you create. so they take IP from That VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Talal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;===&lt;/P&gt;&lt;P&gt;please rate answers that you find useful , and mark as answered - when it is &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; - so others can find it easily&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Nov 2011 08:38:47 GMT</pubDate>
    <dc:creator>tfraij</dc:creator>
    <dc:date>2011-11-09T08:38:47Z</dc:date>
    <item>
      <title>WiSM Service IP vs Management IP</title>
      <link>https://community.cisco.com/t5/wireless/wism-service-ip-vs-management-ip/m-p/1758277#M162442</link>
      <description>&lt;P&gt;What is the difference between WiSM Service IP vs Management IP in #show wism status?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which IP is uded to communicate AP and which used for data? which range wireless client will get? &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 04:03:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism-service-ip-vs-management-ip/m-p/1758277#M162442</guid>
      <dc:creator>Hamilan Gnanabaskaran</dc:creator>
      <dc:date>2021-07-04T04:03:04Z</dc:date>
    </item>
    <item>
      <title>WiSM Service IP vs Management IP</title>
      <link>https://community.cisco.com/t5/wireless/wism-service-ip-vs-management-ip/m-p/1758278#M162443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Hamilan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;please check the following two links:&lt;/P&gt;&lt;P&gt;1) management interface&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117168"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117168&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&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="wp1326669"&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;2) service &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/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117020"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1117020&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;he 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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- now with WISM the situation is little bit different.&lt;/P&gt;&lt;P&gt;WISM Service port is used also for carrying communication between WISM module and 720 Supervisor.&lt;/P&gt;&lt;P&gt;the communication is carried using WCP protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- managment , is the WLC access IP that you can telnet / HTTP. and also all intercontroller communication carried over management IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trying to answer your questions:&lt;/P&gt;&lt;P&gt;1) Which IP is uded to communicate AP and which used for data? &lt;/P&gt;&lt;P&gt;the communication between AP's and WLC is done using AP-Manager interface.&lt;/P&gt;&lt;P&gt;except discovery request sent on management.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;now data clients are carried inside LWAPP/CAPWAP tunnel.&lt;/P&gt;&lt;P&gt;so client connect to AP.&lt;/P&gt;&lt;P&gt;AP tunnel that client to WLC using the LWAPP/CAPWAP tunnel. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) which range wireless client will get? &lt;/P&gt;&lt;P&gt;this depends on which VLAN's you configure on WLC.&lt;/P&gt;&lt;P&gt;you can map the WLAN to managment interface -&amp;gt;&amp;gt; so clients are in same VLAN as management.&lt;/P&gt;&lt;P&gt;or you can map it to any dynamic interface (new VLAN) you create. so they take IP from That VLAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;Talal&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;===&lt;/P&gt;&lt;P&gt;please rate answers that you find useful , and mark as answered - when it is &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; - so others can find it easily&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Nov 2011 08:38:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism-service-ip-vs-management-ip/m-p/1758278#M162443</guid>
      <dc:creator>tfraij</dc:creator>
      <dc:date>2011-11-09T08:38:47Z</dc:date>
    </item>
  </channel>
</rss>

