LAP registration with ap-manager interface only

Hi, is it possible to register an APs with no visibility of the management interface? The WLC would have a separate ap-manager interface but in a different vfr then management interface. APs can see the ap-manager interface one but not the management one.

I don't mind to use for example service port for the isolated management. But i heared the service port has restrictions under HA design.
Exactly what firmware or model of WLC are you using? 
You can't use ther Service Port for production.  This port is primarily used for Out-of-Band-Management and for HA SSO.
The document is dated five years ago and describes the 4.0 SW. My question was if there is any trick or possibility to arrange it under present HW & SW.
The document may be five years old, but when you are dealing with WLC 4400, WiSM or 2000/2100 then it's still valid.  The APs talk to the controller using the AP-manager interface.  This is the main reason why AP-manager interface and management interface IP addresses is recommended to be in the same subnet.  It will work if either one is on a different subnet but you'll need to do some routing work done.

Similar Messages

  • WLC IP Conflict with AP-Manager Interface

    I am getting an error log in the WLC saying, its IP address is being used by another machine with MAC address A.B.C.D
    But this MAC address A.B.C.D is the MAC address of the AP-Manager Interface in the same controller.
    have anyone faced an issue like this ?
    The same issue is having in another controller also. But I have two more controllers with the same IOS , which are working fine.

    Hey Scott...
    Thanks for ua quick response.
    We have controller 4402.
    We have all the two ports connected to core. But we have enabled LAG as well.
    It was working perfect since almost an year and half. Recently we had an image upgradation to 6.0.182.0.
    Upgradation was done for all the 5 controllers. But two are having this error log since then.
    Its not continously coming.. Only sometimes..

  • Remote LAP registration with controller at Main office

    WLC 5508 is installed at our main office and we want to install LAP at our remote location.
    confusion is that how Remote LAP is register with main office controller?

    No need to bring to Mumbai.
    There are 2 ways: Either bring it to mumbai or keep in ahemdabad.
    Bring to Mumbai then:
     Priming the AP with a Controller and Configure H-REAP
    If you want the AP to discover a controller from a remote network where CAPWAP discovery mechanisms are not available, you can use priming. This method enables you to specify the controller to which the AP should connect.
    In order to prime an H-REAP-capable AP, connect the AP to the wired network at the main office. During its boot up, the H-REAP-capable AP first looks for an IP address for itself. Once it acquires an IP address through a DHCP server, it boots up and looks for a controller to perform the registration process.
    Keep in Ahemdabad:
    Read the HREAP Controller discovery section: DHCP option 43 is the only solution.
    http://www.cisco.com/c/en/us/support/docs/wireless/5500-series-wireless-controllers/71250-h-reap-design-deploy.html
    Regards
    Dont forget to rate helpful posts

  • Mobility group only works using management interface?

    Hello,  in order to stablish the control traffic between 2 WLC-5508, it's necessary to use the management interface??
    It's possible using a dynamic interface o service port ?
    I think it only works with management interface,  but I don't understand the meaning of this text in the Configuration Manual:
    "Mobility control packets can use any interface address as the source, based on routing table."
    Thank you,

    No... mobility communication is done only with the management interface.
    Thanks,
    Scott
    *****Help out other by using the rating system and marking answered questions as "Answered"*****

  • WLC 5508 AP-Manager interface

    Hi, I own a WLC 5508 and I (probably) do not understand AP-Manager interfaces. I have a lab with 2x 1242AG and 1x 1252AG connected to c2960. APs are in vlan 10 (192.168.10.0/24, configured via DHCP), APs are connected to "switchport mode access" interface. c2960 is connected via a trunk to c4506, and WLC is plugged in gi1/3 and gi1/4 (both through twingig). Both ports are configured as "switchport mode trunk". Management interface on WLC is on WLC port 8 (connected to gi1/4), and AP-Manager is on WLC port 1 (connected to gi1/3). Management interface on WLC has "Dynamic AP management" set to disabled, and AP-Manager has it set to enabled. Both, Management and AP-Manager interfaces are tagged, vlan id 12 and 13 (subnets 192.168.12.0/24, 192.168.13.0/24) respectively. APs receive their IP configuration via DHCP (server located in vlan 20, 192.168.20.0, ip helper-address in use), and try to discover WLC by DNS resolution (CISCO-CAPWAP-CONTROLLER.some.domain resolves to AP-Manager IP correctly). But APs do not join to controller, WLC says "Ignoring discovery request received on non-management interface", AP has "not joined" status in Monitor/Statistics/AP Join.
    But if I set management interface as "Dynamic AP enabled", and change DNS to resolve CISCO-CAPWAP-... to it's IP everything works fine - AP joins at once. Please help, how to join LAP to AP-Manager interface? Join to WLC manager is simple, but my design requires at least 2 AP-Manager interfaces.

    Hello,
    I just wanted to mention foremost; a split LAG configuration is not supported on the WLCs.  This "can" be achieved if you are splitting your LAG ports amongst VSS configuration on your two capable devices, but is not a recommended or supported configuration. I would highly suggest a LAG configuration over your individual port.  As far as the "ap-manager" concern you have of managing more than 48 APs, you are correct in that the AP-manager cannot handle more than 48 APs, however only when in an individual port configuration.  The LAG will overcome this limitation.
    George was correct about your DNS entry, this needs to point to the WLC's management interface.  This is why the AP joined when you pointed the DNS entry back to the management address-- as intended.
    This link is anchored to the mgmt, ap-manager, and dynamic interface creation for the 7.0.116.0 Config Guide: http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1286790
    "If" you want to keep an individual port configuration, and need more than 60 APs connected, you will need to create more than one "ap-manager" interface.  You will just make a new dyanamic intreface and place it on the same network as the current ap manager (ie, management interface) and mark it for dynamic ap management.  All APs will still need to only see the management interface for joining; the WLC will assign to the appropriate AP manager as needed.  The WLC will fill up the first AP manager before joining building tunnels through the next AP-manager interface, so in your lab you will not really be able to test this behavior, assuming the 3-4 APs you were using.
    1. You can keep your management interface with "dynamic ap management" enabled so this serves as the first AP manager; if you desire. 
    2. You will need to create another dynamic interface mapped to the next port.  enabled "dynamic ap management" again here, and place this new "ap-manager" interface on the same vlan as the mgmt.  Keep in mind creating a dynamic interface and designating it as an AP manager prevents mapping that interface to a WLAN, see note below.
    *NOTE (from config guide): When you enable this feature, this dynamic interface is configured as an AP-manager interface (only one AP-manager interface is allowed per physical port). A dynamic interface that is marked as an AP-manager interface cannot be used as a WLAN interface.
    I would highly suggest the LAG configuration so there is no need to worry about the ap manager interfaces, regardless of the number of APs communicating. This also allows for growth if WLC needs to be licensed for more and more APs.

  • ACL blocking traffic towards the management interface on WLC 5508

    Hello All,
    I need to apply an ACL in WLC 5508 such that it would allow https traffic on management interface only from selected clients. 
    For same, I have created an ACL permitting only the intended users while blocking the rest. Have applied the same on the management interface. 
    However still the access from all devices to management interface is not blocked. The ACL hit count too is not incremented. 
    I am on WLC code 8.0.110.0. 
    Has anyone else faced similar issue while applying ACL against management interface. 
    Highly appreciate the inputs. 
    Thanks and Regards,
    Adnan

    Hi Adnan,
    you have to apply this ACL as a CPU ACL. Then it will work.
    For your reference:
    http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109669-secure-wlc.html#t4
    Hope that helps...
    Kind regards
    Philip
    --> Pls rate useful responses <--

  • Can you buy limited subscriptions with skype manag...

    can i buy limited subscriptions with skype manager or only unlimited?
    because in skype manager it looks like i can only select unlimited plans...

    Currently, only Unlimited Subscriptions.
    That Said, if you are NOT in the U.S. you can add a normal Skype name, and give them credit so that they could purchase a Limited subscription, or if you are in the U.S. and the Skype member is a business Skype name, you could do the same.
    About Me You can also use a IP Camera as your camera for Skype video Example Instructions

  • PVCS Version Manager Interface to Jdeveloper -- need help with install

    Several of our developers are using Jdeveloper and we need to know how to install the PVCS Version Manager interface to JDeveloper.
    I have already contacted Merant, the vendor for PVCS Version Manager and they could only confirm that the interface existed but was supported by Oracle.
    I have not been able to find any documentation on installing this interface.
    Can anyone supply directions or point me to someplace to look for them.
    Any help you could give me would be greatly appreciated.
    Ward

    Hi all,
    Ward - Brian is absolutely right. As I said in my first posting on this topic (above), we have
    not yet developed an extension for JDeveloper to enable users to work with PVCS Version
    Manager, which I believe is a specific product, rather than an interface.
    This is why I'd greatly appreciate it if you could possibly provide more details of this Interface
    and indeed what Oracle support for PVCS with JDeveloper Merant referred to. Please see my
    first posting above for more details.
    Brian - I'm sorry you do not agree with our approach of using the open published SCM Framework
    to build your own extensions for using JDeveloper with other source code control tools than those
    we support.
    In an ideal world, we would have been able to offer support for every source code control tool on
    the market with our first release of 9i JDeveloper. We were very keen to be able to achieve this and
    we still plan and are currently looking into supporting more tools going forward and as many tools as
    possible in the long term.
    Unfortunately, we only have limited time available for each release and based on the feedback we
    received, after our committment to support Oracle9i SCM, CVS and ClearCase were the most requested.
    Therefore, we tried to reach a compromise to enable users to provide their own support for a specific
    tool should they wish, if they did not use any of those tools supported. Indeed, our research suggests
    that the market for source code control tools is quite fragmented and that customers use a wide range
    ot tools. So, we decided to publish our own SCM Framework, the same one we used for the SCM, CVS
    and ClearCase support, in order to help users build their own extensions in a similar way to ours.
    Hope this helps,
    Regards,
    Dominic Battiston
    JDeveloper Product Management
    Oracle Corp

  • First sync with desktop manager for mac: only 300 contacts synced instead of the 1100

    I have a Curve 8310. version 4
     I have a brand new mac with NO CONTACTS or calendar.
     I have preciously very successfully synced with my windows computer for 2 years.
    I have just tried for the first time to sync with desktop manager,.only 315 contacts synced of the 1100.
    The apple  people recommend using Mark/Space" missing Sync" but I am reluctant to do this as the reviews are mixed.
    Help?

    Hi there.
    Have been using my BB Pearl 8100 on and off since Oct 08.
    I have successfully synced with a Vaio (XP Pro) using BBDM (up to version 4.6) as well as iMac OS 10.5.8 using PocketMac for BB v4.1 and now BBDM for Mac. Have synced with iCal, Mail, Contacts (albeit 647)
    PocketMac can be a little temperamental, but not that much of a prob as when i downloaded it was free (shareware) and the only alternative was Missing Sync.
    This posting is provided as is and implies no warranties

  • Help with Cisco 5508 management interface

    Hello,
    I'm trying to verify some behaviors I'm seeing with my 5508 controller setup and forgive me for missing anything obvious, I've zero experience with this hardware and clueless on the best practices. With that said... out of the box I ran through the AutoInstall process.
    I gave my service port an IP address on my subnet, 10.10.8.0/24 vlan 100 and gave the management interface the ip address 10.10.30.5/24 vlan 130
    From my host I can ping the management interace 10.10.30.5 and the interface gateway 10.10.30.1
    I cannot connect to the controller via 10.10.30.5 either through the web GUI or telnet
    I can connect to the controller via 10.10.8.200 both through the web interface and telnet
    while connected to the service port, I can ping the management port IP but I cannot ping the 10.10.30.1 gateway.
    We have attached two test 3502I AP's and they found the controller and pulled correct ip addresses, clients can authenticate and access network resources as well as the Internet so for the most part, things are working but it concerns me that the management interface can't ping its own gateway.
    Keep in mind, I did no other configurations besides what got configured in the AutoInstall process. What should I look at to resolve?
    Thanks!
    Mike

    The service port is for out of band management and should not be connected to the network.  If connected tot he network, it should not have connectivity to the management interface of the wlc. 
    You can create an ACL to block the service port ip to the managment vlan if you want.  I normally do not connect the service port to the network.

  • Using Suri asking any localised question in the UK, it responds with 'cannot help' can only use US locations etc. and in US English. Have I missed something or set something up incorrectly? I also thought it would interface with your Facebook but it just

    Using Suri asking any localised question in the UK, it responds with 'cannot help' can only use US locations etc. and in US English. Have I missed something or set something up incorrectly? I also thought it would interface with your Facebook but it just comes back with a 'I can't help you with Facebook' message

    Yeah, Siri - a headline feature on the iPhone 4s page - is beta at the mo.
    But then anyone who's used Macs for a few years will know that most new software is pretty much still in beta when it's released anyway. Only Apple could get away with it and retain customers

  • Solution Manager Interfacing with Remedy

    How do we interface Remedy (Ticketing tool ) to Solution Manager and is it mandate to enable Solution Manager Service Desk  for an effective ChaRM implementation or  can we use the existing Remedy tool interfaced directly to Sol Man.

    Some Discussion about Remedy And Solution Manager,
    Solution Manager - Service Desk + Remedy Integration
    And Yes BMC Remedy can be integrated with solution Manager, so please Contact Remedy to guide you on this one.
    Regards
    Shailesh Mamidwar

  • WLC 5508 with 6.0.188 -- ap-manager interface..

    6.0.188 code on new 5508 WLC does not show ap-manager interface.
    6.0.188 code on 4404 wlc does have ap-manager interface.
    Both are working fine.
    Why is that?

    The 5500 controllers use the management interface to function as both the management interface and ap-manager.  There will not be an ap-manager in the 5500.

  • WLC 5508 management interface

    Hi, I have a particular wireless design that requires one WLC 5508 to be connected to two seperate swithces. Port 1 of WLC is connected trunk to Switch A and Port 2 of WLC is connected to Switch B. Each switch has its own local VLANS. When I connect 1130s LAPs they need to find the management interface initially and then use only AP management interfaces. since there is only one management interface, if I assign management interface on a vlan that is configured on switch A then APs on switch A join fine but those on switch B keep asking for management interface and from capwap debug on WLC it says that join request was received on wrong ineterface ....
    the only work around to this was to make routing between switch A and switch B for the two vlans on which APs reside... but for security purposes - client would like to avoid this
    any help much appreciated ..

    Hi thanks for your reply,
    Yes I agree perfectly with your explanation - On both switches I have UDP forward for 5246 and 5247 and everything works fine.
    You understood exactly what's happening for initial discovery the Guest AP asks for managemnt interface through WLC port 2 but managerment IP is on admin side WLC port 1 and then it drops packet saying that it was received on the wrong port. In fact that is why I put an ACL between the Admin switch and guest switch taht allows only 5426 capwap control - just to allow that initial discovery from guest AP to contact Management interface which can only be assigned to one port and in my case it is on the admin switch side. And that is why I had to make a route between the two independent switches.
    My question is to know if there is any other way with my given design to eliminate this initial discovery to the management inetrface, as my client would like the admin and guest switches to be completely seperated i.e. without the routing. Is there any way that the guest APs can make contact with the AP management interface on their side only skipping the discovery of the management interface ? the guest APs were primed on the admin side so they know the IP. After the initial discovery, if I remove the routing between admin and guest switch, guest APs keep their connectivity without any problems.

  • ASA 5515 management interface

    I started to configure a new ASA 5515 to replace an 5510.  When I attempted to remove the "management-only" command from the Management0/0 interface I was greeted with the following error:
    "ERROR: It is not allowed to make changes to this option for management interface on this platform."
    Does this mean we can't use the managment interface anymore on these newer ASAs?  I was planning on using that port when we bought it.  If this is the case, let this be a warning to whoever is counting the managment port as a 7th interface on the 5515!

    Update: I just found out that you can't use the management interface for failover purposes either.     Argggggg.
    "Management interface cannot be configured for failover on this platform."

Maybe you are looking for