<?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: AP Manager interface and Virtual Interface in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077548#M63780</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well from a WLC, the management is used to access and manage the wlc.  It is also used for communication with the mobility group.  AP-Manager is the interface the wlc and the ap's use and the virtual interface is used by internal dhcp, mobility group, webauth, etc.  The virtual interface is not routable in your network, it is mainly used by the wlc's for various features.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is from a Cisco Doc:&lt;/P&gt;&lt;P&gt;The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA server. If the service port is in use, the management interface must be on a different subnet than the service port. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The AP-Manager interface is used as the source IP address for all Layer 3 communications between the controller and the lightweight access points. The AP-Manager must have a unique IP address and should be on the same subnet as the management interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The virtual gateway interface is used to support mobility management, DHCP relay, and embedded Layer 3 security, like guest web authentication and VPN termination. The virtual interface must be configured with an unassigned and unused gateway IP address. If multiple controllers are configured in a mobility group, the virtual interface must be the same on all controllers for seamless roaming. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The service-port interface is mapped only to the physical service port. The service port interface must have an IP address on a different subnet from the management and AP-Manager interfaces. A default-gateway cannot be assigned to the service-port interface, but static routes can be defined through the controller command-line interface for remote network access to the service port. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Aug 2008 20:54:46 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2008-08-04T20:54:46Z</dc:date>
    <item>
      <title>AP Manager interface and Virtual Interface</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077547#M63779</link>
      <description>&lt;P&gt;What do each of these interfaces do on the 526 WMAC?  I am not sure I understand the functionality and did not find the answer to this in the documentation.  &lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:15:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077547#M63779</guid>
      <dc:creator>Kevin Melton</dc:creator>
      <dc:date>2021-07-03T23:15:08Z</dc:date>
    </item>
    <item>
      <title>Re: AP Manager interface and Virtual Interface</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077548#M63780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well from a WLC, the management is used to access and manage the wlc.  It is also used for communication with the mobility group.  AP-Manager is the interface the wlc and the ap's use and the virtual interface is used by internal dhcp, mobility group, webauth, etc.  The virtual interface is not routable in your network, it is mainly used by the wlc's for various features.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is from a Cisco Doc:&lt;/P&gt;&lt;P&gt;The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA server. If the service port is in use, the management interface must be on a different subnet than the service port. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The AP-Manager interface is used as the source IP address for all Layer 3 communications between the controller and the lightweight access points. The AP-Manager must have a unique IP address and should be on the same subnet as the management interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The virtual gateway interface is used to support mobility management, DHCP relay, and embedded Layer 3 security, like guest web authentication and VPN termination. The virtual interface must be configured with an unassigned and unused gateway IP address. If multiple controllers are configured in a mobility group, the virtual interface must be the same on all controllers for seamless roaming. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The service-port interface is mapped only to the physical service port. The service port interface must have an IP address on a different subnet from the management and AP-Manager interfaces. A default-gateway cannot be assigned to the service-port interface, but static routes can be defined through the controller command-line interface for remote network access to the service port. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 20:54:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077548#M63780</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2008-08-04T20:54:46Z</dc:date>
    </item>
    <item>
      <title>Re: AP Manager interface and Virtual Interface</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077549#M63781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is the "Service Port" that you are referencing?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 12:22:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077549#M63781</guid>
      <dc:creator>Kevin Melton</dc:creator>
      <dc:date>2008-08-05T12:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: AP Manager interface and Virtual Interface</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077550#M63782</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the service port is used with other wlc's. You don't have to worry about that &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 12:26:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077550#M63782</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2008-08-05T12:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: AP Manager interface and Virtual Interface</title>
      <link>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077551#M63783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, I agree.  there does not seem to be a Service Port on the 526 Controller...&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Aug 2008 12:29:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ap-manager-interface-and-virtual-interface/m-p/1077551#M63783</guid>
      <dc:creator>Kevin Melton</dc:creator>
      <dc:date>2008-08-05T12:29:40Z</dc:date>
    </item>
  </channel>
</rss>

