WLAN controller redundancy

We have a site with 3 controllers it's serveral miles between them. And have think about to deploy a N+1 solution. My question is if the controllers must have same RF group. I know they must have same mobility group!. Can you have several mobilty groups on one controller?

Hi Klas,
Have a look at this good doc for RRM Management. Hopefully this will clear things up;
In a scenario where multiple controllers are configured with the same RF Group Name, but their respective APs cannot hear each other's neighbor messages, two separate, top-level RF Groups are formed.
RF Grouping happens at the controller level. This means that once APs report information to their controllers on the other APs they hear, and the controllers to which those APs are connected, each respective WLC communicates directly with the other WLCs to form a system-wide grouping. Within a single system-wide group, or RF Group, many subsets of APs can have their RF parameters set independently of each other. For instance, consider a scenario where one central WLC has individual APs at remote sites. In this case, each AP has its RF parameters set separately of the others. While each AP belongs to the same controller RF Grouping, each individual AP in this example is in its own logical RF sub-Group.
APs each compile and maintain a list of up to 34 neighboring APs per radio. This list is then reported up to their respective controllers. Each WLC maintains a list of 24 neighbors per AP radio from the neighbor messages sent by each AP. Once at the controller level, this per-AP, per-radio neighbor list of up to 34 APs is pruned. The ten APs with the weakest signals are dropped. WLCs then forward each AP neighbor list up to the RF Group Leader, the WLC elected by the RF Group in order to perform all RRM configuration decision-making.
From this good doc;
Radio Resource Management under Unified Wireless Networks
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008072c759.shtml
These are the Group settings available through the WLC GUI:
Group Mode The Group Mode setting allows RF Grouping to be disabled. When this feature is disabled, the WLC cannot group with other controllers in order to perform system-wide RRM functionality. Disabled, all RRM features are implemented locally on each controller. RF Grouping is enabled by default and the MAC addresses of other WLCs in the same RF Group are listed to the right of the Group Mode checkbox.
Group Update Interval The group update interval value indicates how often the RF Grouping algorithm is run. This is a display-only field and cannot be modified.
Group Leader This field displays the MAC Address of the WLC that is currently the RF Group Leader. Because RF Grouping is performed per-AP, per-radio, this value can be different for the 802.11a and 802.11b/g networks.
Is this controller a Group Leader When the controller is the RF Group Leader, the value of this field is yes. If the WLC is not the leader, the previous field indicates which WLC in the group is the leader.
Last Group Update The RF Grouping algorithm runs every 600 seconds (ten minutes). This field only indicates the time (in seconds) since the algorithm last ran and not necessarily the last time a new RF Group Leader was elected.
Hope this helps!
Rob
Please remember to rate helpful posts.....

Similar Messages

  • WLAN controller redundancy over IP VPN

    Customer currently has a Cisco 5500 WLAN controller at one of our datacenters. They want to add a WLAN controller as redundancy at their local site which shall be used as a secondary failover controller. This site is reachable over VPN. Which redundancy options do I have here? As i understand with HA functions the controllers has to be within the same L2 network and have low latency. Is my only option here to manually configure a new controller, buy double the AP licenses and copy the config from the old one? And if the first fail the APs would need to reboot and reassociate with the secondary controller?
    Would be really greatful if someone could point me in the right direction :)

    You have a few options .. 
    1. Buy two fully licensed controllers. One primary one secondary and configure as such.
    2. HA N+1 where you buy one fully licensed controller and one HA controller or a controller with a minimum of 50 licenses. Put the secondary controller into ha mode and it will go to max licenses. 
    http://www.cisco.com/c/en/us/td/docs/wireless/technology/hi_avail/N1_High_Availability_Deployment_Guide/Licensing.html
    3. APSSO AND CLIENT SSO this is where you need layer 2. There is a data base that syncs between the
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf

  • Single WLAN Controller Limitations

    Aside from redundancy, are there any other limitations to deploying a single Cisco 5508 WLAN Controller that I should be aware of?   The configuration guide states you need multiple controllers for the following:
    A multiple-controller system has the following additional features:
    •Autodetecting and autoconfiguring RF parameters as the controllers are added to the network.
    •Same-subnet (Layer 2) roaming and inter-subnet (Layer 3) roaming.
    •Automatic access point failover to any redundant controller with a reduced
    Is it true you can't have those roaming capabilities with a single controller?

    No... You have all those except for redundancy.
    Sent from my iPhone

  • WLAN Controller can configure as ACTIVE-ACTIVE

    Customer is looking for two numbers WLAN Controller (AIR-AP1242AG-E-K9). And they want to configure as ACTIVE-ACTIVE. I would like to know whether it can be configuring as ACTIVE-ACTIVE.
    And Is really require WLAN Controller for AIR-AP1242AG-E-K9 access point ? or it can be configure without WLAN controller ?
    Please revert me ASAP
    Regards,
    Manoj

    Hi Manoj,
    Although WLC Controllers can be configured in an Active-Active type redundancy, you don't need the WLC for small deployments. The AIR-AP1242AG-E-K9 access point can be setup in Autonomous or Stand-alone mode as well :)
    Cisco IOS Software Configuration Guide for Cisco Aironet Access Points 12.3(7)JA
    http://www.cisco.com/en/US/docs/wireless/access_point/12.3_7_JA/configuration/guide/i1237sc.html
    Cisco Aironet 1200 Series Access Point Hardware Installation Guide
    http://www.cisco.com/en/US/docs/wireless/access_point/1200/installation/guide/1200-TD-Book-Wrapper.html
    Hope this helps!
    Rob

  • Communication between : AP and WLAN controller

    Hi,
    The communication between AP and WLAN Controller is ( Data and Control ) UDP.
    Source port 1024 and destination port 12222 and 12223. Actually which device listen to which port or both should listen as control and data can be generated from both the devices.
    How does the user ( wireless client) traffic is switched - if user traffic is a TCP traffic. It will be sent to WLANC and then WLANC forwards it to respective VLAN or default gateway ( depending upon the destination in the packet ).
    Please explain / share the experience.
    any link on cisco.com
    Thanka in advance
    Subodh

    "the LWAPP Control and Data messages are encapsulated in UDP packets that are carried over the IP network. The only requirement is established IP connectivity between the access points and the WLC. The LWAPP tunnel uses the access point's IP address and the WLC's AP Manager interface IP address as endpoints. The AP Manager interface is explained in further detail in the
    implementation section. On the access point side, both LWAPP Control and Data messages use an ephemeral port that is derived from a hash of the access point MAC address as the UDP port. On the WLC side, LWAPP Data messages always use UDP port 12222. On the WLC side, LWAPP Control messages always use UDP port 12223.
    The mechanics and sequencing of Layer 3 LWAPP are similar to Layer 2 LWAPP except that the packets are carried in UDP packets instead of being encapsulated in Ethernet frames."
    Taken from "Cisco 440X Series Wireless LAN Controllers Deployment Guide"

  • AIR-LAP1310G-E-K9 acces point not joining to 5508 wlan controller

    Hi,
    I have Cisco AIR-LAP1310G-E-K9 access point and 5508 wlan controller with version 7.0.220 and it is joining to the WLAN controller.  I have enabled dhcp in the lan controller and i dont have external dns server. How to fix this issue?  Can this LAN controller version will support this access point? 
    My Lan Controller Management IP Address is 10.10.10.5
    Please find the below configuration of 1300 access point.
    AP001d.4513.dd68#reload
    Proceed with reload? [confirm]
    %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.
    %LWAPP-5-CHANGED: LWAPP changed state to DOWNXmodem file system is available.
    flashfs[0]: 4 files, 2 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 7741440
    flashfs[0]: Bytes used: 2052608
    flashfs[0]: Bytes available: 5688832
    flashfs[0]: flashfs fsck took 14 seconds.
    Base ethernet MAC Address: 00:1d:45:13:dd:68
    Initializing ethernet port 0...
    Reset ethernet port 0...
    Reset done!
    ethernet link up, 100 mbps, full-duplex
    Ethernet port 0 initialized: link is up
    Unable to get our ip address: no "IP_ADDR" variable set
    The system has been encountered and error initializing
    tftp file system. The system is ignoring the error and
    continuing boot. If you interrupt the system boot process,
    the following commands will set IP_ADDR, DEFAULT_ROUTER
    and NETMASK environment variables, initializing tftp file
    system, and finish loading the operating system software:
        set IP_ADDR
        set DEFAULT_ROUTER
        set NETMASK
        tftp_init
        boot
    Loading "flash:/c1310-rcvk9w8-mx/c1310-rcvk9w8-mx"...############################################################################################################################################################################################
    File "flash:/c1310-rcvk9w8-mx/c1310-rcvk9w8-mx" uncompressed and installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1310 Software (C1310-RCVK9W8-M), Version 12.4(10b)JA3, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2008 by Cisco Systems, Inc.
    Compiled Wed 19-Mar-08 19:09 by prod_rel_team
    Image text-base: 0x00003000, data-base: 0x003BE9E0
    Initializing flashfs...
    flashfs[1]: 4 files, 2 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 7741440
    flashfs[1]: Bytes used: 2052608
    flashfs[1]: Bytes available: 5688832
    flashfs[1]: flashfs fsck took 2 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    cisco AIR-LAP1310G-E-K9R   (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
    Processor board ID FHK1133E002
    PowerPCElvis CPU at 262Mhz, revision number 0x0950
    Last reset from reload
    LWAPP image version 3.0.51.0
    1 FastEthernet interface
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:1D:45:13:DD:68
    Part Number                          : 73-8960-09
    PCA Assembly Number                  : 800-24963-06
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC113000V7
    Top Assembly Part Number             : 800-28479-05
    Top Assembly Serial Number           : FHK1133E002
    Top Revision Number                  : B0
    Product/Model Number                 : AIR-LAP1310G-E-K9R
    The name for the keys will be: ap.cisco.com
    % The key modulus size is 1024 bits
    % Generating 1024 bit RSA keys, keys will be non-exportable...[OK]
    ip ssh version 2
        ^
    % Invalid input detected at '^' marker.
    transport input ssh
                     ^
    % Invalid input detected at '^' marker.
    aaa new-model
    ^
    % Invalid input detected at '^' marker.
    aaa authentication login default enable local none
    ^
    % Invalid input detected at '^' marker.
    o
    ^
    % Invalid input detected at '^' marker.
    Press RETURN to get started!
    *Mar  1 00:00:05.442: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
    *Mar  1 00:00:06.473: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
    *Mar  1 00:00:07.817: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1310 Software (C1310-RCVK9W8-M), Version 12.4(10b)JA3, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2008 by Cisco Systems, Inc.
    Compiled Wed 19-Mar-08 19:09 by prod_rel_team
    Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
    transport input ssh
                     ^
    % Invalid input detected at '^' marker.
    *Mar  1 00:00:33.860: %LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER
    *Mar  1 00:00:33.860: %LWAPP-3-CLIENTERRORLOG: DNS Name Lookup: could not resolve CISCO-LWAPP-CONTROLLER
    *Mar  1 00:00:33.861: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    logging origin-id string AP:001d.4513.dd68
             ^
    % Invalid input detected at '^' marker.
    logging 255.255.255.255
            ^
    % Invalid input detected at '^' marker.
    logging trap 3
            ^
    % Invalid input detected at '^' marker.
    *Mar  1 00:00:37.440: Logging LWAPP message to 255.255.255.255.
    AP001d.4513.dd68>
    %LWAPP-3-CLIENTEVENTLOG: Forcing AP to obtain IP address using DHCP
    %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.10.10.46, mask 255.255.255.0, hostname AP001d.4513.dd68
    Translating "CISCO-LWAPP-CONTROLLER.CISCO-LWAPP-CONTROLLER.mydomain.com"...domain server (10.10.10.5)
    %LWAPP-3-CLIENTEVENTLOG: Did not get vendor specific options from DHCP.
    %LWAPP-3-CLIENTEVENTLOG: Did not get log server settings from DHCP.
    %LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER.CISCO-LWAPP-CONTROLLER.mydomain.com
    %LWAPP-3-CLIENTERRORLOG: DNS Name Lookup: could not resolve CISCO-LWAPP-CONTROLLER.CISCO-LWAPP-CONTROLLER.mydomain.com
    AP001d.4513.dd68>

    Your debug is very telling ..
    AP001d.4513.dd68>
    %LWAPP-3-CLIENTEVENTLOG: Forcing AP to obtain IP address using DHCP
    %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.10.10.46, mask 255.255.255.0, hostname AP001d.4513.dd68
    Translating "CISCO-LWAPP-CONTROLLER.CISCO-LWAPP-CONTROLLER.mydomain.com"...domain server (10.10.10.5)
    %LWAPP-3-CLIENTEVENTLOG: Did not get vendor specific options from DHCP.
    %LWAPP-3-CLIENTEVENTLOG: Did not get log server settings from DHCP.
    %LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER.CISCO-LWAPP-CONTROLLER.mydomain.com
    %LWAPP-3-CLIENTERRORLOG: DNS Name Lookup: could not resolve CISCO-LWAPP-CONTROLLER.CISCO-LWAPP-CONTROLLER.mydomain.com
    AP001d.4513.dd68>
    What are you using to tell the AP where the contoller lives ? Since you are consoled into the ap you can use the -> capwap ap controller ip address
    This will point the ap to your controller
    "Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
    ‎"I'm in a serious relationship with my Wi-Fi. You could say we have a connection."

  • How can I copy a PSK from one WLAN Controller to another

    I'm trying to replace a WLAN controller with a new one.  One WLAN is configured with WPA-PSK.  Nobody seems to know the key that was used.
    Anyone know if there is a way to extract the encrypted key out of a controller and put it into the new WLAN Controller?
    Thanks in advance.

    No can do ...
    https://supportforums.cisco.com/discussion/11364566/view-psks-wlans-wlc 
    However, if any users are on a MAC Book and has iCloud enabled you can see the key under the "keys". If you have a windows 7 box and uses the native supplicant you can expose the key on the supplicant ..

  • WAP4410N Access point and 4404 WLAN Controller.

    Hello to all,
    I am planning to setup a new WLAN using WAP4410N Wireless N Access Point. Is it possible to manage the AP using 4404 WLAN controller ?
    I need to buy arround 42 AP for covering the entire building.
    Regards,
    Aslam

    leolaohoo
    Could u please tell me which series can be used with 4404 WLANC ?
    Also the AP Should support Bridging or Mesh.

  • Can Wlan Controller work with Third party Aps

    Can Cisco Wlan Controller work for 3rd party Aps which does not have LWAPP running. If yes How.If no then how we can manage existing Ap's of say 3com in the network...

    Hi Friend,
    No, Cisco WLC will not support any third party APs. Even if Cisco APs are not lwapp AP then WLC will not be able to manage them.
    We need to have Cisco Lwapp APs only for wireless lan controller to manage them.
    For 3com Aps you need to talk to 3com guys or any third party tool if available to manage these APs.
    HTH
    Ankur

  • Cisco LWAP & WLAN Controller Flexconnect Across HP Switches

    Hello All, I'm looking for a little guidance in making the needed routing and switching configuration changes on our Corporate Network to accomadate flex connect functionality for Cisco Lightweight Access Points (LWAPs).  The LWAPs that are currently configured on our network only work when our WLAN Controller is up and running and I need for them to be disconnectable so that we can move the WLAN Controller to our virtual co-lo.  It should be known that I inhereted this network from the previous admin and have been working hard to map everything out to the best of my ability.  Also, the WLAN controller is already operating in our production network so it limits my ability to do much testing. 
    Just FYI, I'm a new Systems Admin promoted from a Desktop Support role and have my CCENT (Currently working on CCNA & MCITP Server Admin) so I have some knowledge but it is limited on the networking and switching side of things.  Unfortunately, the Senior Systems Admin has even less knowledge of networking than me and I don't really have anyone to turn to which is why I'm posting here.  I would have utilized GNS to help me simulate the configuration however there are HP switches in the mix and no means of emulating them.
    -Relevant Device List-
    (CONSA251) Sonicwall  NSA 240 - 10.1.1.251
      Interface Information 
    Interface    IP Address    Description   
    X0  ->  LAN
      10.1.1.251   LAN Interface  
    X1  ->  WAN
      *************   Time Warner WAN  
    X2  ->  DMZ
      *************   DMZ Interface  
    X3  ->  WAN
      *************   Sprint WAN  
    X0-V20  ->  LAN
      10.1.101.1   Corporate WLAN  
    X0-V30  ->  LAN
      192.168.1.1   Guest WLAN 
    (CORT250) Cisco 3845 - 10.1.1.250
    (CO-WLAN-CTRLER) Cisco 5508 Wireless Controller - 10.1.1.2
    (COSW240) HP Procurve 4108GL - 10.1.1.240
    (COSW238) HP Procurve 2510B-24 - 10.1.20.238
    (CORP-AP-MIS) AIR-LAP1131AG-A-K9 - 10.1.1.79
    (COSW239) HP1810G-24 - No IP (Inaccesible but being replaced)
    I will now go on to explain our network topology as it pertains to the WAPs and WLAN Controller and how I believe it needs to be configured in order to operate from my perspective. 
    Our Corporate and Guest Wireless Access is provided via the Sonicwall CONSA251 through a connection from the X0 interface to HP Switch COSW239 which is then connected to WLAN Controller CO-WLAN-CTRLER as detailed below:
    Device - Interface Name/Port
    CONSA251 - X0
    COSW239  - 2
    COSW239  - 18,19
    CO-WLAN-CTRLER - 2,3
    The WLAN Controller currently communicates with all the LWAPs via Layer 3 TCP\IP as I understand it and then routes all DHCP requests and traffic destine for the 10.1.101.1 (corporate WLAN) and 192.168.1.1 (Guest WLAN) to the Sonicwall and vice versa.
    Now what I am trying to do is VLAN the LWAP CORP-AP-MIS across the HP Switches to the X0 interface on the Sonicwall NSA240 where it will be able to route traffic via VLAN 20 & 30.  The problem lies in my inexperience with HP VLAN configurations and how the ports need to be configured on each device so it can route traffic to the Sonicwall when the WLAN Controller is shutdown.
    The LWAP CORP-AP-MIS layer 2 trace to the WLAN Controller is as shown below:
    Device - Interface Name/Port
    CORP-AP-MIS -  FA/0
    COSW238     - 16
    COSW238     - 25
    COSW240     - B4
    COSW240     - H6
    CORT250     - GigabitEthernet0/0
    CORT250     - Se1/0
    CONSA251    - X0
    Now for all intesive purposes the Corporate Router CORT250 should probably be handling the routing for our Corporate and Guest Wireless network however that was not the way it was originally setup and I have to work with what was inhereted.  The Corporate Router CORT250 has a default route to the Sonicwall and the Sonicwall CONSA251 has all the routing already in place for the Corporate & Guest WLANs.
    What I would like to do is VLAN off the X0-V20&V30 accross multiple switches and switchports to each LWAP in our building.  I do have the LWAP I'm testing on configured with Flex Connect which I understand is required for it to be disconnectable.
    Any guidance on how I would go about configuring this accross devices would be appreciated.  I know there are some difference between HP and Cisco Switching terms and how tagging, untagging, and trunking works however I lack the experience to apply this in practice especially in a production environment. 
    I will be happy to provide any additional information or clarification that is needed.  Thank you in advance for the help.

    Just to add about the ISE... you can profile, but having only one ssid might or might not work in your situation.  Also if you end up with remote sites or ap's in h-reap mode, currently ISE cant do any profiling.  If you go with the 7500 or 5508/WiSM2, they don't really do an active-active or active backup. They are both up and you can split the load or put all ap's on one, its up to you.  I usually split the load just to make sure both are working.  I don't want to all of a sudden loose the primary and then find out my secondary/backup is not working.

  • I need to bridge a printer off a wireless bridge using a 4402 WLAN Controller

    I need to bridge a printer off a wireless bridge using a 4402 WLAN Controller.  Would I need to make any changes on the 4402 WLAN Controller?

    One options is to take a cisco autonmous access point and configure it as a WGB. And no, you would not have to do anything special to the WLC in thay deisgn. The WGB would act as a wireless client.
    Make sense?

  • Data flow using a WLAN controller

    Can someone explain the flow of data from wireless client to some destination in the internal network (or the Internet) using a WLAN Controller? Use a 4402 as an example.
    Specifically, I am wondering if client traffic actually passes thru the WLAN Controller (4402). I am reading the configuration guide and it doesn't seem to be explicitly stated one way or the other.

    Hi Ken,
    This is a very common question these days.
    Here is a recent thread as well as an excerpt from a good doc:
    http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=Getting%20Started%20with%20Wireless&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddaca5d
    In the Cisco Centralized WLAN architecture, LWAPP-enabled access points operate in the lightweight mode (as opposed to the autonomous mode). The access points associate to a Cisco WLAN controller. The controller manages the configuration, firmware, and control transactions such as 802.1x authentication. In addition, all wireless traffic is tunneled through the controller.
    LWAPP is an IETF draft protocol that defines the control messaging for setup and path authentication and run-time operations. LWAPP also defines the tunneling mechanism for data traffic.
    In an LWAPP environment, a Cisco Aironet LWAPP-enabled access point discovers a controller by using LWAPP discovery mechanisms and then sends it an LWAPP join request. The controller sends the access point an LWAPP join response allowing the access point to join the controller. When the access point is joined, the controller downloads its software if the versions on the access point and controller do not match.
    LWAPP secures the control communication between the access point and controller by means of a secure key distribution, utilizing X.509 certificates on both the access point and controller.
    From this doc:
    http://www.cisco.com/en/US/products/hw/wireless/ps430/products_quick_start09186a00805100f5.html#wp47092
    Hope this helps!
    Rob
    Please remember to rate helpful posts.........

  • Cisco 1010AP Can't find 4402 WLAN controller

    Hi folks,
    I'm running a 4402 WLAN controller running 5.2 code. I've got some 1010APs that don't associate with the WLC. I'm trying to keep the setup basic. The access points are plugged into the same VLAN as the native vlan for port1 on the controller. I've setup a DHCP server in the manner documented. The WLAN controller is configured as a master server. This is the message that I get in the web interface for WLC:
    AP with MAC 00:0b:85:6e:4a:90 (AP 1010 #1) is unknown.
    Any clues as to what I'm doing wrong?

    Hi Daniel,
    You won't like this I'm sure, but this is why the 1010 is not working;
    **Note: Controller software release 5.0.148.0 or later is not compatible with Cisco Aironet 1000 series access points.
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn52.html
    Hope this helps!
    Rob

  • Virtual WLAN Controller Guest Anchor

    We are planning a WLAN upgrade and the security policy is to forward wireless Guest user traffic to the DMZ controllers. We are now considering the Virtual WLAN Controller and all AP's will register with the virtual controllers and we will use Flexconnect for Staff and internal traffic that will switch their traffic onto the local switch.
    We wish to forward the guest traffic to the DMZ Guest Anchor controller which will be a 5508 controller. This will also offer Office Extend AP service.
    I have looked at teh virtual controller docs and not very clear if this deployment model is supported. Below is a diagram of what we wish to deploy and can anyone advise if thsi is a supprted deployment model.

    Well you can use the vWLC to anchor to a 5508, but not the other way around. So if you use the DMZ 5508 for OfficeExtend, you will not be able to anchor the traffic back to the inside. Cisco doesn't support reverse anchoring for a Remote-LAN in OfficeExtend and requires you to actually have the OfficeExtend AP's connect to an inside WLC. In v7.0.x you were able to do this reverse anchor, but it was removed on later codes.
    Sent from Cisco Technical Support iPhone App

  • 1510 Mesh A.P with 5508 WLAN Controller

    Hi everyone,
    I got a situation. We had our wireless mesh network running with 4400 Controller and 1510 A.Ps. Now that we have bought new 5508 Controller (with SW: 7.2) and 3600 Indoor APs, we are unable to add legacy APs on our new controller. After a wild googling I have found that for 1510 APs i need to be on SW ver: 4.0. But that will lead into another situation i-e I wont be able to have my 3600 APs on WLAN Controller.
    Any suggessions/wise words will be very very obliged....
    Thanks,
    Azhar...

    You would have to keep those 440's up and have all the WLC in the same mobility group. That is the only way to keep those 1510's up and running. Cusco usually supports mobility between different version but only really as far back as 2 versions. Might work though.
    Here is a compatibility guide that explains what devices work with what code.
    http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
    Sent from Cisco Technical Support iPhone App

Maybe you are looking for