WLC-2006 and 1242 APs

Hello.
I have a 2006 with 2 1242 APs connected to it. The problem I have is the 2 APs keep rebooting. they come up, get a DHCP address, stay up for a minute or so and restart. The log on the controller shows this each time it happens:
Thu Apr 20 10:54:39 2006 [ERROR] spam_lrad.c 2544: Security processing of Image Data failed from AP 00:16:47:b2:0a:48
Thu Apr 20 10:54:39 2006 [ERROR] spam_crypto.c 653: Failed decryption of message from AP 00:16:47:B2:0A:48
Thu Apr 20 10:54:24 2006 [ERROR] spam_lrad.c 5973: Refusing image download to AP 00:16:47:b2:0a:48 - Unable to open file /bsn/ap//c1240
Any ideas?
Thanks

I had the same problem with some 1231 APs with a 4402 controller. If you watch the APs console while it is rebooting, you'll notice that it can't get a certificate. I finally figured out that the time was different (wrong time zone) wrong on the controller compared to what I gave the APs when I upgraded them to LWAPP.
FYI

Similar Messages

  • Wlc 4402 and 1010 Aps

    Hi,
    I have 2 vlans (wired-side) in my corporation: the first one for Data (vlan 1, native) and the second one for voice (vlan 2). We've just get a wlc 4402 with 1010 Aps and I would like to know one thing:
    Could I create 2 Ssids(one for voice and another for Data) and map each one to its wired Vlan?.
    Does the 1010 Ap support 802.1q?
    Thanks in advance for your help

    The 1010 aps connect to the switches as hosts
    (switchport mode access; switchport access vlan ...)
    The controller has 2 ports that connect to the network as trunks. You can connect them as port 1 and 2, or put them in a lag group [aka etherchannel)
    All the vlan trunking is done at the controller port to switch port. The AP sends the info down to the controller over the vlan specified for the aps
    In your case, you should create another vlan for the APS.
    The 4402 controller mgmt interface would sit in the same vlan as the APs. You would then create dynamic interfaces on the controller that have a vlan id and ip address for the desired network per your needs. You would then create a wlan on the controller and then bind it to the dynamic interface you just created.
    I am oversimplfying this process quite a bit, but it should get you started. There is now a good bit of info on cisco.com for the wireless products

  • WLC 5508 and 1242 associating

    I have a 5508 running 6.0.196.0 and have a few 1142's currently associated to it.  I've been trying to get a 1242 to associate but it will not.
    My WLC hands out DHCP to a wireless VLAN (950) and the 1242 gets an IP in this VLAN, but will not associate or showup as an AP.
    Additionally,  I have a console cable connected and attached the output from the boot, but cannot get my settings to allow (via Hyperterm) to let me CLI.  I'm set at 9600, 8,N,1 and tried a few other settings.
    Layer 1 - Good
    Layer 2 - Good
    Layer 3 - Good
    1142
    1142
    1142
    1252
    The DHCP leases are above and can ping any of these, but only show the three 1142s in the controller.
    Any thoughts as to why this won't showup?  How bout my hyperterm settings?
    Thanks!

    Most likely the you have flow control enabled in hyperterm which is why the AP won't respond to your input.  Make sure the terminal emulation program has flow control set to off.
    As far as the 1252 not joining, the reason is because it is running an autonomous AP image, not a LWAPP/CAPWAP image.  This is seen if you look at the image name.  This has k9w7 which is autonomous images.  K9w8 are lightweight images.  You just need to convert this AP to lightweight.

  • WLC 5508 and 1142 APs

    Hi ! How can I view the WPA passwords that was set on my APs ? I have web access to the WLC. Thanks.

    You can use a program called wz Cook on windows boxes to pull the wep and wpa keys ..
    "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."

  • WLC 4400 and supported APs

    Hello.
    Does anyone know which indoor APs are still sold by Cisco and supported by a 4400 WLC? From my research I only found 3500.
    Thanks in advance,
    João.

    The complete list of APs which can be supported on the 4400 can be found here.

  • WLC 5508 and LightWeight APs Deployment question

    Hi There,
    Can you please wit the following question in regards to the deployment of a new WLC and new LAPs,
    I have configured and connected a 5508 WLC and 3500 series LAP.
    LAG is enabled in the WLC and successfully connected to the neighboring switch (using etherchannel) and to the network.
    The port-channel port is set to trunk mode obviously and certain vlan ids are currently allowed (3-5)
    The management interface has this IP address 192.168.5.250/24
    I created a WLAN with WLAN ID 3, Interface set to Management and say SSID test1
    I have connected a new LAP to the network, which switchport interface is set to access mode and assigned with vlan id 3. The LAP is able to join the WLC successfully with an IP address, such as, 192.168.3.100 (assigned via DHCP).
    When I try connecting a mobile client to the wireless LAN, it can successfully detect and connect to the WLAN, created in the WLC (test1) however it gets an IP address by DHCP, in the 192.168.5.0/24 network, which is the IP range of the management interface's IP address.
    What can I do to get the clients connecting on network 192.168.3.0/24? I thought this would be the case since I allocated the WLAN Id of 3 in the WLAN test1 configuration and since the LAP switchport is set to access mode with vlan ID 3.
    Cheers,
    egua5261

    Hi,
    The WLAN ID has no effect with the VLAN ID. WLAN ID is just an identifier for the WLAN.
    you said "Interface set to Management and say SSID test1" and here is your issue.
    You set the interface of the WLAN to the management. So, the WLAN will be mapped to the VLAN to which the management interface is mapped to.
    What you need to do is to create a dynamic interface with ip range in 192.168.3.0/24 and provide VLAN ID for that interface and assign your WLAN to this new interface. This way your clients will get an IP from this specified range.
    HTH
    Amjad

  • Updated WLCs shows wierd log messages and most APs do not associate

    Hi, I recently updated my 4402 WLC to latest Software Version                 (7.0.98.0).
    This first seamed to have worked fine. WLCs rebooted fine, then APs rebooted and upgraded their software images.
    All fine as it seamed.
    The I went on to also upgrade to latest Emergency Image Version(5.2.157.0).
    After rebooting the WLCs most APs won't associate again.
    Logs from WLCs shows a lot of messages like:
    Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:38 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:38 wlc-1 WLC-1:
    Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:38 wlc-1 WLC-1: *mmListen: Oct 07 22:11:38.857: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:38 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:38 wlc-1 WLC-1:
    Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:39 wlc-1 WLC-1:
    Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:39 wlc-1 WLC-1:
    Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:40 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:40 wlc-1 WLC-1:
    Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:40 wlc-1 WLC-1: *mmListen: Oct 07 22:11:40.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:40 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:40 wlc-1 WLC-1:
    Oct  7 20:11:40 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:40.905: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
    Oct  7 20:11:40 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:40 wlc-1 WLC-1:
    Oct  7 20:11:43 wlc-1 WLC-1: *mmMobility: Oct 07 22:11:43.210: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:43 wlc-1 WLC-1: -Traceback:  105fbe18 102d8be0 102bc81c 102d5d20 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:43 wlc-1 WLC-1:
    Oct  7 20:11:43 wlc-1 WLC-1: *mmListen: Oct 07 22:11:43.210: %MM-3-INVALID_PKT_RECVD: mm_listen.c:6691 Received an invalid packet from 192.168.128.18. Source member:0.0.0.0. source member unknown.
    Oct  7 20:11:43 wlc-1 WLC-1: *mmListen: Oct 07 22:11:43.211: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:43 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:43 wlc-1 WLC-1:
    Oct  7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
    Oct  7 20:11:50 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
    When looking back a bit in the logs it looks like this started after upgrading the Software version. But after this first reload it the APs came back and worked. Now they don't.
    The case seams to be the same with both my WLCs.
    What could have gone wrong?
    Please advice.

    Not sure which messages are concerning you the most...
    Regarding the message:
    Oct  7 20:11:39 wlc-1 WLC-1: *mmListen: Oct 07 22:11:39.749: %OSAPI-5-OSAPI_INVALID_TIMER: timerlib.c:542 Failed to retrive timer.
    Oct  7 20:11:39 wlc-1 WLC-1: -Traceback:  105fbe18 102cb318 105f3ab0 10c0d250 111cd0cc
    Oct  7 20:11:39 wlc-1 WLC-1:
    There is already a bug for it: CSCth64522
    And for:
    Oct  7 20:11:50 wlc-1 WLC-1: *osapiReaper: Oct 07 22:11:50.913: %OSAPI-6-FILE_DOES_NOT_EXIST: osapi_file.c:348 File : /proc/755/stat does not exist.(errno 2)
    Oct  7 20:11:50 wlc-1 WLC-1: -Traceback:  105eaae4 105f4d44 105f7848 105fa648 105f3ab0 10c0d250 111cd0cc
    Looks like it's matching CSCtf39550
    Both bug fixes should be included in the next 7.0 release and should not impact the WLC behavior.
    Hope this helps...

  • WLC-2100 with LWAPP APs in headquarter and branch?

    Hello,
    can one controller 2100 be used to manage APs in the headquarter and in branches?
    We plan to use 6 APs-1131 in the HQ and 4 APs-1131 in the branch. Is this scenario supported by a AIR-WLC2112-K9 in the HQ?
    What do I have to check regarding the WAN (bandwidth, delay) and the LANs (Switches, VLANs,...)?
    Thanks and regards
    Matthias

    Sure.  You can use H-REAP.
    H-Reap Design and Deployment Guide
    http://www.cisco.com/en/US/products/ps6087/products_tech_note09186a0080736123.shtml
    H-REAP Modes of Operation Configuration Example
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00807cc3b8.shtml
    Hybrid Remote Edge Access Point (H-REAP) Basic Troubleshooting
    http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a008081103d.shtml

  • An issue with WLC 5508 and 7921 phone

    Hello all!
    I have a system with WLC 5508 and some 1242 APs. And I use a lot of 7921 phones.
    One of 7921 phones was in trouble. It loses registration, disconnect conversations...
    I installed the trial WLC and run voice diagnostics.
    I  saw some of "Potentially degraded QoS in downlink direction because of  incorrect packet classification" messages and one "Fair upstream packet  loss ratio: 1,2%, which is less than threshold 2.5%"
    As I understand all of 7921 phones in these area are affected.
    what  does it mean? I set up Platinum QoS for voice WLAN. I don't have any qos  configuration string for AP and WLC ports on switches...
    any ideas?
    thanx in advance

    Sergey:
    There is one application called "WLC Config analyzer". You save your "show run-config" from your WLC in a text file and import it by this application. it will analyze the file for you and tell you what recommendations for voice are missing so you improve them.
    When importing a config file you choose what voice clinets you are using, so you need to choose cisco 7921 to it tells you what config improvemetns is needed based on 7921 needs.
    Here is the link to download the application:
    https://supportforums.cisco.com/docs/DOC-1373
    download the latest versoin.
    BTW, how many voice/data clients are connected to one AP in that area? if I remember correctly if you are utilizing voice then the max number of clients connected to one AP should not exceed 17. If you have more than this number per AP try to minimize the number of users concurrently connected to the AP then try again.
    Hope you'll find the config analyzer useful.
    If useful please don't forget to rate.
    Amjad

  • Best practices for network design on WLC 2504 and 5508

    Dear all:
    I'm looking for some recommendations on WLC 2504 and 5508 about the the following:
    Maximum amount of AP per port
    The scenario when to use all ports in both WLC
    Maximum number of clients(users) per port
    Bandwidth comsumption of  management vs data in order to assign one port for management
    I've just found this:
    Cisco 5508 controllers have eight Gigabit Ethernet distribution system ports, through which the controller can manage multiple access points. The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller. Cisco 5508 controllers have no restrictions on the number of access points per port. However, Cisco recommends using link aggregation (LAG) or configuring dynamic AP-manager interfaces on each Gigabit Ethernet port to automatically balance the load. If more than 100 access points are connected to the 5500 series controller, make sure that more than one gigabit Ethernet interface is connected to the upstream switch.
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/6-0/configuration/guide/Controller60CG/c60mint.html
    Thanks for your help.

    The 5508-12, 5508-25, 5508-50, 5508-100, and 5508-250 models allow a total of 12, 25, 50, 100, or 250 access points to join the controller.
    This is an old document.  5508 can now support up to 500 APs if you run firmware 7.X.  2504 can support up to 75 APs if you run firmware 7.4.X.
    I'm looking for some recommendations on WLC 2504 and 5508 about the the following:
    Best practice and recommendation is to LAG all ports so you will be able to form a link redundancy.  If one link goes down, you have other link to push traffic. 

  • WLC 5508 and associated AP's

    Hi,
    I have a problem with a poor signal. I have two WLC 5508 and 10 ap's 3502. So, that I have two wlc on the network I decided to divide this 10 ap's.
    WLC 5508 has 7.0.98 software version.
    The 5 first ap was associated to one wlc and the other 5 to second controller.
    Two problems was observed, first that some clients which try connect to AP associated  to second controller have problem to obtain IP address from DHCP pool on first wlc.
    The second problem is that on this two WLC was configured two DHCP pool. One controller assigns address for a dedicated WLAN and the second wlc assigns address for a second WLAN.
    This two WLAN's is broadcast on two wlc.
    Kamil

    Hi Nicolas,
    The APs are 3502I model and now are located on the lower ceiling.
    From Thursday all APs are associated to only one WLC the second one is just only as a backup and from this time there are not any problems with a signal. This information is directly from clients.
    The DHCP pool is located on the first WLC now.
    Also, I considered to use switch or other machine as a DHCP pool but it's problematic to deploy now.
    Kamil

  • WLC 5508 and LAP1310 - Not syncing up!

    As the title states I have a WLC 5508 and a LAP1310 that will not sync up.
    The error stated in the traps log is "AP with MAC (xxxx.xxxx.xxxx.xxxx) is unknown."
    WLC software release is : 7.2.103.0
    IOS on the AP is : 12.4(18a)JA2
    Upon some investigation I found that the "AP with MAC is unknown" error usually points to one of two things:
    A.  WLC firmware needs to be updated
    B.  AP needs to be updated.
    C. The AP is not compatible with the WLC.
    I am leaning toward solution C and I am looking for a conformation or a correction, if anyone could help out that would be greatly appreciated!
    I've tried reading the compatibility matrix released by Cisco, but I found it mildly confusing as to what is and isn't supported by each software release.
    Sources - http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml#lap1250
    Problem 11: 1250 LAP Not Able to Join WLC
    The setup consists of a 2106 WLC that runs version 4.1.185.0. A Cisco 1250 AP is not able to join the controller.
    The log on the WLC shows this:
    Mon Jun 2 21:19:37 2008 AP with MAC f0:2x:cf:2x:1d:3x (APf02x.cf2x.1d3x) is unknown.
    Mon Jun 2 21:19:37 2008 AP Associated. Base Radio MAC: f0:2x:cf:2x:1d:3x 
    Mon Jun 2 21:19:26 2008 AP Disassociated. Base Radio MAC:f0:2x:cf:2x:1d:3x
    Mon Jun 2 21:19:20 2008 AP with MAC f0:2x:cf:2x:1d:3x (APf02x.cf2x.1d3x) is unknown.
    Mon Jun 2 21:19:20 2008 AP Associated. Base Radio MAC: f0:2x:cf:2x:1d:3x 
    Mon Jun 2 21:19:09 2008 AP Disassociated. Base Radio MAC:f0:2x:cf:2x:1d:3x
    Mon Jun 2 21:19:03 2008 AP with MAC f0:2x:cf:2x:1d:3x (APf02x.cf2x.1d3x) is unknown.
    Solution: This is because the Cisco 1250 series LAP is not supported on version 4.1. The Cisco Aironet 1250 Series AP is supported from controller versions 4.2.61 and later. In order to fix this issue, upgrade the controller software to 4.2.61.0 or later.
    Problem 16: 1000 series LAPs not able to join the Wireless LAN controller, WLC runs version 5.0
    This is because WLC software release 5.0.148.0 or later is not compatible with Cisco Aironet 1000 series APs. If you have a Cisco 1000 series LAP in a network, which runs WLC versions 5.0.48.0, the 1000 series LAP does not join the controller and you see this trap message on the WLC.
    "AP with MAC xx:xx:xx:xx:xx:xx is unkown"

    videoaudiojack
    What version of Premiere Elements are you using and on what computer operating system is it running?
    What are the properties of this .mp4 video import (video and audio compressions, frame size, frame rate, interlaced or progressive, pixel aspect ratio)?
    If you have any information about the video bitrate and audio bitrate of the file, that would be good to know.
    What is the audio - stereo 2 channel or 5.1 channel?
    What are you (manually) or the project automatically setting as the project preset to match the properties of your source video?
    Let us start here and then decide what next.
    Thank you.
    ATR

  • Anchor mobility between WLC 5508 and Aruba/Clearpass

    Hello. I have a question regarding the abiltiy to configure anchor mobility between a 5508 WLC and an Aruba controller. To date, my understanding is it has never been possible and I have never found any documentation that says it can be done.
    Scenario: My organization and a partner organization co-own a hospital. We coexist on a large campus, with each org having a number of buildings that the owning org maintains the network presence in. We also maintain back-to-back firewalls between us and do not hand-off any direct layer 2 interfaces to each other. However, the two orgs do partner to provide each others business SSID's in each other's WiFi networks using anchor mobility. Our current solution utilizes an A/M tunnel between my org's 5508 controllers and the partner orgs 2504 controller and we explicitly permit the tunnel traffic between partner controllers for A/M to work. Last year, the partner org retired some old WiSM's and changed their wireless solution to Aruba and recently implemented Clearpass. In order to maintain A/M with us they left a 4404 operational, but due to the newer code we were running they were forced to purchase a 2504. So now they are only maintaining a limited footprint in their network with a few Cisco AP's and the rest of their coverage areas use Aruba AP's and they have indicated that they want to completely retire their Cisco WLC's. Because we host some of their SSID's on our controllers and can tunnel them to their 2504, they get all of their WiFi traffic coming from our network, however my org can only connect to our SSIDs on their campus in certain areas.
    The solution I have been asked to provide is to find a way to continue providing some sort of anchor mobility services between our WLC's and their Aruba controllers. My org maintains that we do not want to simply hand them a layer 2 interface for security reasons, but they want our SSIDs to be available in all areas of the partner org's campus and vice versa. So far I have stalled the partner org's plans to retire their WLC's by telling them that retiring their WLC's will completely break WiFi between orgs, but they are adamant that some sort of A/M solution must be found.
    Is there any way to do some sort of A/M between a WLC and Aruba controller and if so, is there any documentation showing configuration examples etc?
    Thanks,
    John

    Hi John,
    I do not think it will work. Even if it get working somehow, it will be operation nightmare to troubleshoot & fix a issue since both vendor will say it is NOT supported solution.
    What about if you ask them to advertise your SSID (assuming it is dot1x) on their APs as another SSID on their network, but pointing it to your RADIUS & DHCP for IP connectivity (you do not have layer 2 requiremnt for this & can do this as long as you have L3 communication between each other)
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • Issues upgrading WLC-2006

    I cannot seem to get past the "transfer download start" (CLI) or "download" (GUI) phase of the upgrade on a WLC-2006 -- from 3.2.171.5 to 4.2.209.0. The transfer consistently times out at about 76% complete and I receive an error message, either "error writing to flash" or "error writing output file" (or something similar). Any suggestions/recommendations would be greatly appreciated.

    You can't upgrade from 3.X to 4.2.209 direct.  You need to upgrade to 4.0.206.0 first before going anyware.  It's specified in the Release Notes.
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn422090.html#wp233853

  • WLC 2112 and WLC 2504

    This might be a really stupid question but I need to ask just so that I get a definitive answer. I have a customer that is using a WLC 2112 and has maxed out the licenses for the WLC. I have suggested for him to purchase a 2504 with 30 or 40 licenses to replace the existing 2112. He doesn't want to purchase 30 to 40 licenses and doesn't want to remove the 2112 from the network environment. He would rather purchase a WLC 2504 with 15 licenses and just add that into the network.
    My question is, will there be a problem running a 2504 and a 2112 on the same network? Or can I just make one a primary and one a secondary?

    That should be fine. Just make sure the WLCs are running the same code version and everything should work fine. This is required for APs failover from one WLC to another. You don't want the APs upgrading or downgrading code versions every time the ap moves from the primary to the secondary WLC.
    Sent from Cisco Technical Support iPhone App

Maybe you are looking for