2106 WLC replacement

Hi everybody,
thanks for a super forum!
I just had a 2106 WLC die on me, there is a backup controller so everything is still running. BUT i have a replacement unit here on my desk.
Dead WLC
Software version: 4.0.206.0
Replacement WLC:
Software version: 4.1.185.0
The APs are set up with primary / secondary controllers, and there might be a default mobility group. The plan is to use the replacement WLC as the new secondary WLC. And this is where my insight is a bit vague...
I read somewhere that mobility groups could consist of misc. platforms and i assume versions...
So what happens if the primary (running the older firmware) dies and all APs register with their secondary (running a newer firmware)? Will they then start upgrading and be offline for the time that takes. And will they downgrade again once the primary comes back online?
Cheers

If you choose upgrade option, then you have to do this it in following manner (see table 1 of the below release note) as a step by step upgrade.(assuming you go for 7.0MR1 which is 7.0.116.0)
4.1.185.0 ->4.2.176.0 ->4.2.209.0 -> 7.0.116.0
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn7_0_116_0.html
Safer approach would be restore the config to the new 2106 (if you already have a backup of the dead wlc config) while it is on the software code 4.1.185.0. Then upgrade the controller (offline) to 7.0.116.0 & bring it online.
If that is the primary WLC, then your AP should register for that controller. Once all APs register to that controller you can upgrade the 2nd WLC to the same image following the same process.
HTH
Rasika
*** Pls rate all useful responses ***

Similar Messages

2106 wlc different vlan accessibility

I have 1 2106 wlc 6 1131AG LAPs that are going to be placed in three vlans. All three vlans are created and configured on a 3550G switch.
I created two additional virtual interfaces on the WLC, tagged it with appropriate vlan number and connected the port with untagged vlan identifier to a dot1q enabled trunk port on the 3550 switch. That is,
man int - untagged, port 1
vlan2, tagged -2, port 2,3
vlan3, tagged -3, port 4,5
vlan4, tagged - 3, port 6
and port 1 is connected to a trunk port on the 3550G switch with dot1q.
I am not able to reach the created vlan interfaces on the WLC !?1?!
Kindly help?

jeff.velten, wouldn't that break the very use of the WLC? documents I referred from cisco recommend to connect the WLC to a trunked port. Like here: http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a00805e7a24.shtml
So how are the vlan tags from the wlc not passed on to the trunk port? Is there something I missed, somewhere?

2106 WLC and 4 LWAPP (1252G)

I have a 2106 WLC with 4 AP's (AIR-LAP1252AG-A-K9)
One of the AP's (port 4) is only connecting at 10Mbps, not 100Mbps and I don't know why?
All the ;ports are set on the controller to AUTO, When I try to force that port to 100Mbps, the link drops.
Could it be a cabling issue... or could I have a bad port on the 2106?    How to I troubleshoot this. It's odd, because
that particular AP is about 100ft from thte WLC and the closest to it.
Any ideas?
Joe
Primary Software Version   7.0.116.0
Predownload Retry Count
Boot Version   12.4.18.1
IOS Version   12.4(23c)JA2
Mini IOS Version 3.0.51.0
Primary Software Version   7.0.116.0
Predownload Retry Count
Boot Version   12.4.18.1
IOS Version   12.4(23c)JA2
Mini IOS Version 3.0.51.0

Interesting... I unplugged the LAP (data and power) and removed it from the wall of our training room 75ft from our computer room, walked the AP into the computer room and with a 15' patch cord and power supply plugged it back into the WLC 2106. Waited a min for the AP to reboot and now my port speed is showing 100Mbps connection.
The issue must be with the cable run...? Thanks for pointing out the obvious.   This now begs another questions regarding 2106 best practices and the idea of connecting our 4 AP's directly into network switches and not the WLC 2106 itself. That seems to be the recommendation. Any comments?
Joe

2106 WLC Software Upgrade

Hi Guys,
I bought a brand new 2106 WLC and a 1142AP. After going through the standard setup, the 1142 LAP was blinking red, yellow and green. I checked the logs and found the following message;
*Apr 18 10:20:29.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.219.1.26 peer_port: 5246
*Apr 18 10:20:29.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Apr 18 10:20:30.392: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.219.1.26 peer_port: 5246
*Apr 18 10:20:30.394: %CAPWAP-5-SENDJOIN: sending Join Request to 10.219.1.26
*Apr 18 10:20:30.394: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Apr 18 10:20:30.405: %CAPWAP-3-ERRORLOG: This AP is not supported in controller version 6.0.196.0
*Apr 18 10:20:30.489: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Apr 18 10:20:30.490: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.219.1.26:5246
I requested the latest IOS and Boot image for the controller from the supplier but he has provided only
AIR-WLC2100-K9-7-0-220-0.aes, no equivalent boot image and has insisted that it is enough to upgrade the controller.
My question is this: Is the AIR-WLC2100-K9-7-0-220-0.aes compatible with the 1142 LAP? And would I be able to upgrade the controller with only the
AIR-WLC2100-K9-7-0-220-0.aes IOS and no equivalent boot image?
Thanks for your promt response.
Regards,
FON

The time and date are correct. April 18 was the day I got the logs.
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 6.0.196.0
RTOS Version..................................... 6.0.196.0
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... N/A
Build Type....................................... DATA + WPS
System Name...................................... WLAN
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.828
IP Address....................................... 10.219.1.25
System Up Time................................... 2 days 21 hrs 45 mins 1 secs
System Timezone Location.........................
Configured Country............................... Multiple Countries:US,BE
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +49 C
--More-- or (q)uit
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
3rd Party Access Point Support................... Disabled
Number of Active Clients......................... 0
Burned-in MAC Address............................ 40:55:39:8D:D4:62
APc471.fe8f.f3dc>sh version
Cisco IOS Software, C1040 Software (C1140-RCVK9W8-M), Version 12.4(23c)JA, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 01-Jun-10 12:53 by prod_rel_team
ROM: Bootstrap program is C1040 boot loader
BOOTLDR: C1040 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA, RELEASE SOFTWARE (fc3)
APc471.fe8f.f3dc uptime is 0 minutes
System returned to ROM by power-on
System image file is "flash:/c1140-rcvk9w8-mx/c1140-rcvk9w8-mx"
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-LAP1042N-E-K9    (PowerPC405ex) processor with 98294K/32768K bytes of memory.
Processor board ID FGL1527S1LS
PowerPC405ex CPU at 333Mhz, revision number 0x147E
Last reset from power-on
LWAPP image version 7.0.94.21
1 Gigabit Ethernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: C4:71:FE:8F:F3:DC
Part Number                          : 73-12836-04
PCA Assembly Number                  : 800-33767-04
PCA Revision Number                  : A0
PCB Serial Number                    : FOC14425AJ2
Top Assembly Part Number             : 800-33775-01
Top Assembly Serial Number           : FGL1527S1LS
Top Revision Number                  : A0
Product/Model Number                 : AIR-LAP1042N-E-K9
Configuration register is 0xF
APc471.fe8f.f3dc>sh inventory
APc471.fe8f.f3dc>

AIR-LAP1242AG-K9 could not join a 2106 WLC: i ma getting ready for a deployment, how can i resolve this?

Hi,
I setup a mini wireless LAN network lab with a not for resale 2106 wireless lan controller and a sales air-lap1242ag access point. I do not have a DHCP and DNS in my lab environment. I have configured the WLC with the basic configuration using the CLI wizard, i also configured the WLC as a DHCP server for clients that will be connecting to the APs associated to the controller.
I powered up the AP and connect the ethernet port directly to the controller, the controller issued an IP address to the AP, the AP downloaded a new operating system from the controller but failed to join the controller.
I check both debug message on the controller console and the trap messages on the controller's GUI and it say the AP could not download a configuration from the controller and it is beacuse of invalid license. Below is the trap message:
Configuration Phase Statistics
Requests Received
Responses Sent
Unsuccessful Request Processed
Reason For Last Unsuccessful Attempt
Last Successful Attempt Time
Last Unsuccessful Attempt Time
Last Error Summary
Last AP Message Decryption Failure
Last AP Connection Failure
Last Error Occurred
Last Error Occurred Reason
Last Join Error Timestamp
Also, I tried to log into the GUI of the AP using the both the username and password ''Cisco'' but I cannot get into the device. I can only get in through the CLI. In the CLI, almost all the commands I enter gives an error the it is disabled. I don't know what to do any more, I want to know if the access point is faulty or i am not doing the right thing.
PLEASE HELP!!!!!!!!!!!!!!!!!!!

Thank you for the quick response.
The controller is running firmware version:
Software Version 6.0.199.4
Emergency Image Version 6.0.199.4
The AP can ping the Management IP address of the controller successfully via console. I have also entered in the AP the WLC's Management IP address information and it is still the same. Below is the message I'm getting on the console of the AP it self:
*Jul 9 13:06:09.803: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Jul 9 13:06:10.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip:
192.168.50.246 peer_port: 5246
*Jul 9 13:06:10.001: %CAPWAP-5-CHANGED: CAPWAP changed state to
*Jul 9 13:06:11.636: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully
peer_ip: 192.168.50.246 peer_port: 5246
*Jul 9 13:06:11.638: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.50.246
*Jul 9 13:06:11.638: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
*Jul 9 13:06:11.724: %CAPWAP-5-CHANGED: CAPWAP changed state to CFG
*Jul 9 13:06:11.726: %DTLS-5-ALERT: Received WARNING : Close notify alert from
192.168.50.246
*Jul 9 13:06:11.727: %DTLS-5-PEER_DISCONNECT: Peer 192.168.50.246 has closed conne
ction.
*Jul 9 13:06:11.727: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 1
92.168.50.246:5246
*Jul 9 13:06:11.772: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Jul 9 13:06:11.772: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
I will also like to know if AIR-LAP1242AG is compatible with WLC 2106 controller.
Any help will be greatly appreciated, i really need to resolve this issue in my LAB now so that I don't go to my customer site to fumble.
thanks in advance.

External Authentication 2106 WLC help

Hello,
We have setup a 2160 WLC for external authentication so that we can control the look and feel of the web pages a bit better.
I wanted to better understand how to setup the page to handle errors. I'm trying to determine how the errors get posted back to the external web page.
My understanding is that the form is "POST" to the 1.1.1.1, when it redirects to the external web auth due to an error are the values (error codes, redirect url, etc) appended to the query string?
If they are appeded to the query string...what are the variable names we should be looking for?
Thanks in advance

Josh,
I would recommend reviewing the source within the Web Authentication templates for info on customizable error codes... available on Cisco.com:
Wireless -> WLCs -> Select a model -> Web Authentication Bundle
Best,
Drew
Sent from Cisco Technical Support
iPhone App

Cisco 526 WLC and 2106 WLC in one Mobility Group

Hi,
is it possbile to build a solution with one Cisco 526 Wireless Express Mobility Controller and one Cisco 2106 Wireless LAN Controller in one Mobility Group regarding seamless roaming??
Thank for your answers
Best regards
Stephan

I don't know if it is possible, but I would think if you had any issues, TAC wouldn't support it. Try opening a case with TAC to see.

Does the 2106 WLC support multiple interfaces?

I am trying to lab something up and I believe I am doing something incorrectly. My management VLAN works fine, the AP on port 7 finds the controller fine, but my VLAN 80 doesn't seem to be mapped to port 2. I mapped a test WLAN to the VLAN, and setup a DHCP scope, and a client can get on the WLAN, acquire an IP address, etc. I thought I coudl then map that VLAN (80) to port 2 and have it go out a cable modem. Doesn't seem to be working that way, however.
Anyone know if this is supported, or what am I doing wrong?
Thanks in advance!

You are getting FANCY Tim!
For starters you should really use a switch because sometimes you may get odd behavior connecting right to the WLC. Also the WLC is like a layer 2 switch and doesnt route. Ive done something similar in fact. We call it offnet. We break out the ports and have 1 going external. We used a switch inbetween the ap and comcast line.
"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 2106 - What does a VLAN need an IP Address

Likely a rookie questions, but I'm assigning WLANs to VLANs on a 2106 WLC and when I create the VLAN I'm actually creating an interface that needs layer 3 parameters such as an IP address. Why is this, i.e. whey do I need to create a layer 3 interface vs. just creating a VLAN like I would have done on an autonomous AP?
thanks in advance,
Simon

The main purpose of the full ip address subnet and gateway information for each dynamic interface (vlan) is in order to:
1) Manage VLAN traffic.
2) Manage other communications between other controllers.
3) DHCP relay (WLCs interface will be like the proxy for all the wireless clients)
4) Other stuff, like anchor controllers, web authentication, etc..

Wlc 2106 mDns bonjour AirPlay AirTunes apple??? help

Hi guys,
Long time reader, first time poster.. I'm after some advice.
I'm failing dismally trying to configure a 2106 Wlc to allow apple device (iPhone, iPads) to stream AirPlay to an apple tv 2.
Now, I have this working perfectly with a 5508 WLC.
I understand that the apple devices all need to be on the same subnet (they are), that multicast needs to be enabled, and I've tried a variety of multicast addresses as mentioned in many posts.. Also the wired infrastructure is not the problem (as connecting net gear access points into the same wired infrastructure works fine).
I've also read posts where some people say the 2100series doesn't support AirPlay/bonjour/mDns and others saying they have had it work.
But I can't find a definitive answer.
Can anyone confirm or deny which WLC support AirPlay, as if I need to switch I want to make sure they do.
The 5508 works fine.
Anybody able to shed some wisdom?
Thanks Wayne.
Sent from Cisco Technical Support iPad App

I have a 2106 in the lab and it works fine. Here are a few screen shots and a link that may help..
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfmulti.html

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

Max. number of WLCs per WCS

Hi,
I know this is a fairly basic question but I can't find answer in WCS Q&A's etc.
I'm looking at a deployment where there will be many small sites with only 5 or 6 APs and a 2106 WLC. Each site will be in a different mobility group.
I know WCS licensing counts APs, but is there a max. number of WLCs?
Thanks, MH

Hi Mark,
The supported number of WLC's per WCS is based on the WCS Platform used :)
Minimum server requirements
Cisco WCS High-End Server
â¢ 3000 lightweight access points, 1250 standalone access points, 750 wireless LAN controllers
â¢ Two IntelÂ® Xeon Dual Core CPU's; 3.0 GHz, 8 GB RAM, 200 GB HDD
Cisco WCS Standard Server
â¢ 2000 lightweight access points, 1000 standalone access points, 150 wireless LAN controllers
â¢ IntelÂ® Dual Core CPU; 3.2 GHz, 4 GB RAM, 80 GB HDD
Cisco WCS Low-End Server
â¢ 500 lightweight access points, 200 standalone access points, 50 wireless LAN controllers
â¢ IntelÂ® CPU; 3.06 GHz, 2 GB RAM, 30 GB HDD
CiscoWorks WLSE Models 1130-19 or 1133 running Cisco WCS
â¢ 1500 lightweight access points, 100 wireless LAN controllers
â¢ Intel Pentium 4 CPU; 3 GHz, 3 GB RAM, 38 GB HDD
http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd802570d0.html
Hope this helps!
Rob

Error Joining the AP-1242AG with 2106 controller

i have converted Autonomous 1242AG series Ap into lightweight mode.i am using 2106 WLC with software version 4.1.185.the Ap doesn't associate the controller .its produce the following error:
Mar 1 00:00:38.071: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER
*Mar 1 00:00:48.098: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:48.099: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:00:48.099: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Mar 1 00:00:49.098: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:49.098: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Oct 6 12:30:57.289: %LWAPP-5-CHANGED: LWAPP changed state to CFG
*Oct 6 12:31:02.289: LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response
*Oct 6 12:31:02.998: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.
*Oct 6 12:31:02.998: %LWAPP-5-CHANGED: LWAPP changed state to DOWN

Hi
I think we have experienced something similar and we did a 'more' on the env_vars file and found that the env_vars contained out of date IP default gateway information.
For example:
We established that the env_vars file contents have not been updating correctly. Documentation on the Cisco site suggests that changes to IP configuration information should be reflected in env_vars after a reload of the WAP.
This does not always seem to happen.
As an example, this env_vars contains the incorrect information that the static IP is XX.11.60.100, which is incorrect and at least least a year out of date, despite having undergone reloads since being reconfigured. Obviously, if the WAP comes up using this info, the gateway address etc. will not work...and the WAP is unable to contact the WiSM. We have also had a case where the incorrect DNS address is stored and used, which might be more of an issue for you looking at your output above.
WAPXXX#more flash:/env_vars
DEFAULT_ROUTER=10.0.0.1
ENABLE_BREAK=no
IOS_DEFAULT_DOMAIN_NAME=XXXXXXXXX
IOS_NAME_SERVER_ADDR=XX.11.159.122
IOS_STATIC_DEFAULT_GATEWAY=10.11.63.250
IOS_STATIC_IP_ADDR=XX.11.60.100
IOS_STATIC_NETMASK=255.255.252.0
IP_ADDR=10.0.0.1
MANUAL_BOOT=no
NETMASK=255.255.255.224
TERMLINES=0
We wrote a script to go around and delete all the env_vars files on the 1240 WAP but then discovered that the LWAPP migration tool forces a reload of the WAP that auto-generates the env_vars file that we just deleted, complete with the wrong information again!
I can offer no solution on how to stop the old information being written to env_vars, as I cannot find where it is stored in the first place, it must be somewhere in the flash, but am aware that other people in UK educational establishments have also experienced this issue without a proper fix being provided.
The usual solution appears to be to get the WAP on your desk, delete the env_vars file and then pull the plug on the power. DO NOT SAVE/RELOAD. Put the power lead back in and the WAP should come up without refering to the env_vars file and will take all and any DHCP info you are providing.

Cisco 1131 Cannot Associate to WLC Following WCS Install

Greetings, i have had a small wireless deployment up and running for several months consisting of 3 1131 and a 1242 lightweight ap's registered with a 2106 WLC.
Ive had no problems up until i installed WCS on a separate server for testing, ive added the controller successfully and can see all access points up until a day ago.
Following a re-boot of one of our PoE switches two of the 1132 access points failed to re-register with the controller whilst the other two ap's reconnect without issue.
On the Ap themselves lwapp comes with then goes into cfg mode but fails to pull down the config of the controller and then resets.
The controller is giving the message for one of the Ap's
Aug 06 18:03:34.861 spam_lrad.c:2286 LWAPP-3-RD_ERR4: Invalid regulatory domain 802.11bg:-E 802.11a:-E for AP 00:1d:e5:55:df:1a
Previous message occurred 3 times.
Aug 06 18:03:34.861 spam_lrad.c:8055 LWAPP-3-RD_ERR7: Invalid country code () for AP 00:1d:e5:55:df:1a
I have tried resetting both ap's using the mode button at power on but cant figure out what is causing the issue.
Any help would be appreciated!
Regards

This is the response im getting when i add a DNS entry for the lwapp controller into DNS.
cisco AIR-LAP1131AG-E-K9 (PowerPCElvis) processor (revision A0) with 24566K/8192K bytes of memory.
Processor board ID FCZ1213Q1Z8
PowerPCElvis CPU at 262Mhz, revision number 0x0950
Last reset from reload
LWAPP image version 5.1.151.0
1 FastEthernet interface
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:1E:7A:BE:63:60
Part Number : 73-8962-12
PCA Assembly Number : 800-24818-11
PCA Revision Number : B0
PCB Serial Number : FOC12112BWJ
Top Assembly Part Number : 800-29144-02
Top Assembly Serial Number : FCZ1213Q1Z8
Top Revision Number : A0
Product/Model Number : AIR-LAP1131AG-E-K9
The name for the keys will be: AP001e.7abe.6360.cisco.com
% The key modulus size is 1024 bits
% Generating 1024 bit RSA keys, keys will be non-exportable...[OK]
Press RETURN to get started!
*Mar 1 00:00:05.344: soap_prepare_new_image_crash: mini ios flash:/c1130-rcvk9w8-mx/c1130-rcvk9w8-mx
*Mar 1 00:00:05.345: set boothlpr to mini ios
*Mar 1 00:00:05.697: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
*Mar 1 00:00:05.904: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 53 messages)
*Mar 1 00:00:07.990: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:08.992: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:11.955: %SYS-5-RESTART: System restarted --
Cisco IOS Software, C1130 Software (C1130-K9W8-M), Version 12.4(16b)JA, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Mon 07-Jul-08 18:08 by prod_rel_team
*Mar 1 00:00:11.956: %SNMP-5-COLDSTART: SNMP agent on host AP001e.7abe.6360 is undergoing a cold start
*Mar 1 00:00:12.001: %SSH-5-ENABLED: SSH 2.0 has been enabled
*Mar 1 00:00:27.743: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:27.745: bsnInitRcbSlot: slot 0 has NO radio
*Mar 1 00:00:27.745: bsnInitRcbSlot: slot 1 has NO radio
*Mar 1 00:00:27.763: bsnUnlockDevice: not bring radio up: radio 0 is in admin disable state
*Mar 1 00:00:27.764: bsnUnlockDevice: not bring radio up: radio 1 is in admin disable state
*Mar 1 00:00:28.272: Logging LWAPP message to 255.255.255.255.
%DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 172.29.255.51, mask 255.255.255.0, hostname AP001e.7abe.6360
Translating "CISCO-LWAPP-CONTROLLER..********************..local"...domain server (172.29.255.25) [OK]
%LWAPP-3-CLIENTEVENTLOG: Did not get vendor specific options from DHCP.
%LWAPP-3-CLIENTEVENTLOG: Did not get log server settings from DHCP.
%SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
%LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER..********************..local
%LWAPP-3-CLIENTEVENTLOG: Controller address 172.29.255.5 obtained through DNS
%CDP_PD-4-POWER_OK: Full power - NEGOTIATED inline power source
%LWAPP-5-CHANGED: LWAPP changed state to JOINEncoding the APType as 0
Encoding the RSSI threshhold as 0
Encoding the APType as 0
Encoding the RSSI threshhold as 0
%LWAPP-5-CHANGED: LWAPP changed state to CFG
Writing out the event log to nvram...
%LWAPP-3-CLIENTERRORLOG: Config Request Timer: did not recieve config response (controller - it-wlc-2106)
%SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.

2106 1131AP and mesh mode

Hi guys,
i have a 2106 WLC with three 1131AP LWAPP.
I should cover a zone where there is no network cabling and i was thinking about another 1131 in mesh mode.
Do I need particular software release?
Can anyone provide documentation from which i can start to configure the system(WLC)?
thx....

Unfortunately, the only access point that can handle Mesh is the 1500-series. Mesh isn't meant for indoor applications like the 1131AG is meant for. Mesh is meant for city-wide deployments and wireless coverage.
Your only option using 1131AGs is to get a cable out there somewhere. If you purchase a couple of 1242AGs in autonomous mode, you can set up a mesh-like link using link-role flexibility. You can configure your A-radio to be a bridge link, and configure the G-radio to service clients. This can only be done 1-to-1, though, so you'll need two APs for every one you need in an area without cabling. Hopefully that makes sense.

2106 WLC replacement

Similar Messages

Maybe you are looking for