WLC 2125 Rebooting

Hi guys, we are having some trouble with a WLC 2125 with only 6 APs, but like 40 clients trying to associate.
Version: 5.1.151.0
The issue here is that the WLC reboots every 6 or 8 hours for no apparent reason. CPU is always at 0% - 1% and mem usage is at 35% - 40%. I've heard in this forums that this kind of WLC is not recommended for more than 20 clients.. so I don't know if we are over using the box.
Maybe is an issue of software version or something, but in cisco.com there is only one version for this model of controller.
I'm adding an attachment with the crash file:
thanks!

Reboots usually occur to one of three reasons on a 2100 series controller. First is power. The power supply is very susceptible to power spikes and brownouts. If the power spikes, the controller will reboot. Second, memory leaks on the controller. When using Web Auth the controllers CPU and memory resources are consumed fairly quickly. If the code does not effectively release those resources the system will eventually crash. There will be a record of this in the Tech Support section under management on the controller. Third and lastly, thermal issues around the controller. This will show in the event logs as a warning that the controller has exceeded it temperature threshold. If it gets too hot it will shut down completely.
We are just completing the largest single deployment of 2100 series controllers in Cisco's history deploying of 200 2125s and a number of other 2100 series controllers and these are the major reboot issues we have seen.

Similar Messages

WLC 5508 rebooted but still showing high uptime

Hi all,
I had to reboot our production WLC 5508 last night to apply a new adder license, which increased our AP count by 25.
We run a DMZ mobility controller alongside the primary controller, which handles our mobile/guest WLANs using a Mobility Anchor. Normally we would reboot both of these due to issues with the anchor after the primary is rebooted.
So last night I rebooted the primary after installing the new adder license. Once it came back up, I checked the license count and it had increased as per the new license. After that I rebooted the mobility controller, and waited to ensure that this came back up.
Almost straight away, all the AP's had re-associated with the primary (all 96 of them), and clients were starting to show up. I checked the same on the mobility controller (although this does not manage any AP's) and I could see mobility clients associating with this also.
The problem came this morning, when none of the mobility clients that were connected to the mobiltiy WLANs were able to get to the Internet, or any kind of outside connection. This is the typical issue we see when our core switch gets rebooted, or the primary on its own, without rebooting the secondary.
So to troubleshoot this morning the first thing I suddenly noticed was the uptime on the primary controller. It showed 298 days!!
Anyone seen this behaviour before? The WLC DID reboot - I watched it go down and POST again. Why would the uptime counter not reset?
We're on firmware 7.2.111.3 - which I realise is pretty old, but due to CIsco screwing us over with a limited upgrade path, we are not able to upgrade it yet (AP hardware not supported on any of the newer code above this version).
Any help appreciated!

In response to Sandeep, here's the sh sysinfo output:
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.2.111.3
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... UK***********
System Location.................................. Slough CoLo
System Contact................................... Greg Dent
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
IP Address....................................... 172.17.1.40
Last Reset....................................... Software reset
System Up Time................................... 0 days 3 hrs 42 mins 23 secs
System Timezone Location.........................
Configured Country............................... Multiple Countries:GB,RU,US
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +44 C
External Temperature............................. +26 C
--More-- or (q)uit
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 7
Number of Active Clients......................... 794
Burned-in MAC Address............................ **************
Power Supply 1................................... Present, OK
Power Supply 2................................... Present, OK
Maximum number of APs supported.................. 125
As you may notice, the uptime has now reset, but thats because I had to reboot it again this morning. I didnt grab the output before the second reboot. It seems whatever issue caused the uptime counter not to reset didnt occur this time.
Very odd.

WLC is rebooting whenver WAN goes down

Hi,
I came across with one issue repetitively. Whenever we have issue with WAN disconnection issue, after some time our LAN WLC gets rebooted .
As I gone through the logs, found that we will have disconnection with Mobility group member <ip address> . Based on that , suspecting we have some policies or some parameter configured therefore whenever we have issue with mobility controller member ( such as disconnection ) .
We have mobility group configured whereas one of our mobility member is on WAN ( other location ).
so whenever we have disconnection issue with mobility member which is there in head-office location , our local LAN WLC gets rebooted.
can anybody look into this? It would be great to know , if we have enabled any feature unknowingly.

Is the reason you require the same mobility group name for a remote site is because you are doing failover between the two? Usually you don't require the same mobility group name unless you want the AP's to be able to failover between multiple WLC's.
I don't think that would fix your issue though. Maybe setup syslog so you can see if the wlc reboots due to another issue or error.
Sent from Cisco Technical Support iPhone App

WLC 2125 Upgrade

Hi guys, I have a customer with a WLC 2125, with the version 6.0.199.4 and I will now upgrade to the version 7.0.250.0 but i wondering if it´s possible to make a backup for the old image, (i already download the configuration, but not the image) It´s is possible via console or web?
Or it´s safety do the upgrade directly?
Thanks
Gonzalo

Hi,
As per my knowledge you can download old image from wlc. To get the same imgae its better to download from cisco.
Here is the link:
http://software.cisco.com/download/release.html?mdfid=282210723&flowid=7011&softwareid=280926587&release=7.0.250.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
Regards
Dont forget to rate helpful posts

AAA Authorization Fail between WLC 2125 & LWAP 1042n

In my Wireless environment, WLC 2125 is connected to a LWAP 1042n. The WLC is succesfully providing DHCP IP to the AP but is unable to discover it. All are connected. During debug mode following error message is encountered in WLC 2125, "AAA Authorization Fail....".
Please suggest what to do.

Here is a good doc that explains different errors:
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml

WLC 5508 reboots itself after upgrading to 7.5.102.0

Hello all.
We have two WLC 5508 and we upgraded both to software release 7.5.102.0 two weeks ago. We also upgrade the FUS to version 1.7.
Since then both WLC reboot randomly once or twice a day with no obvious reason.
Is anyone else facing the same issue?
Many thanks.

Ok, in that case it is very difficult to pin-point the cause for these sorts reboots. It may be due to a unknown bug. Go through below 7.5.102.0 release notes and see any unresolved caveats related to your issue
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn75.html#wp1030058
Have you configure syslog on your WLC ? If so see what is the last syslog message sent by WLC before reloading, it may indicate something.
Do more observation & see whetehr controller reboot every time it hit 1k client limit. Try to narrow down the criteria to identify under what conditions this will trigger.
In my controller I do not have that many clients & cannot comment if it is related.
HTH
Rasika

WLC 2125 with 2x 1520 Mesh Points - Ethernet Bridging

Hi - I'm looking for assistance with a new Mesh set up we are deploying, the solutions consists of:
1x Wireless LAN Controller 2125
2x 1520 AP/Mesh Points
What we are trying to achieve is to bridge two networks together, I have followed the Cisco configuration guide and I simply can't get the traffic to cross from one side to the other. The WLC can see both 1520's on either side of the mesh network and I appear to have set it up right.
Here is how everything is set up:
- Local network (Class B, 10.0.0.0/16) connected to Port 1 on the WLC.
- 1520 is connected to Port 2 on the WLC via g0/0 with an IP address of 10.0.3.110 (management network, 10.0.3.111 for the wlan-management network) - this is set up as the RootAP, with ethernet bridging enabled and the bridging group set to rsqmesh.
- 2nd 1520 is around 800ft away set up as a MeshAP with ethernet bridging enabled and the bridging group set to rsqmesh. Small 5-port switch (non-cisco) connect to g0/0 on this 1520 with a device attached which has the IP of 10.0.3.37.
All help is appreciated.
Thanks,
Craig.

Bridging will not work if the RAP is directly connected to the controller. But CSCsk15792 is filed on this issue. If you put a switch between the controller and RAP traffic should start flowing.

WLC 5508 reboot cause switch port link flap error disable

Hi All
today my customer call me saied after reboot WLC , the switch port was err-disable , the cause is link flap
after we reboot 3 times , the switch port link flap err-disable every time
does anyone to meet the same problem??
we don't know why the WLC rebboot will cause it , it just normal action on device
the WLC version is 7.4.100.0
link switch with access port , no port channel , no portfast
Asa Hung 2013/05/30

Hello Asa,
As per your query i can suggest you the following solution-
Complete these steps to reset the WLC to factory default settings using the CLI:
Enter reset system at the command prompt.
At the prompt that asks whether you need to save changes to the configuration, enter Y or N. The unit reboots.
When you are prompted for a username, enter recover-config to restore the factory default configuration.
The WLC reboots and displays the Welcome to the Cisco WLAN Solution Wizard Configuration Tool message.
Use the configuration wizard to enter configuration settings.
Note: Once the WLC is reset to defaults, you need a serial connection to the WLC in order to use the configuration wizard.
Hope this will help you.

Wlc automatic reboot

Hi everybody,
I'm trying to find an automatic method to periodically reboot my wlc-4402 (ver 4.2). I also have a wcs (ver. 4.2) that manages it.
I search in wcs menus like "Controller template" and "Background tasks" but I find nothing useful.
I try with cli commands on wlc but it seems there isn't commands like "reboot at".
Do you have any idea to do this job?
Many thanks.
Michel

None.

Cisco WLC 2125 and AIR-LAP1252AG-A-K9 access points

We are running into a little issue here and looking for some help. We have the Controller configured and it appears to be working properly the issue we are running into is that we can only get the above mentioned access points to only join the controller if they are plugged directly into the controller. I would assume that we should be able to plug these access points into any of our switches and they should be able to join the controller correct? Obviously there has to be a configuration issue somewhere and am hoping someone can point us in the right direction.

WAP to Switch - Access port
WLC to Switch - dot1Q trunk on the switch and tagged on the WLC side

Cisco WLC 2125 configuration help

So in a nutshell, from My computer I can ping all VLANS - everything seems to in workding order.
when telnet to the HP 5406zl core routing switch I can ping all VLANs and other parts of the network
But when logged into the Cisco wireless Lan Controller I cant ping VLAN 108 gateway IP (172.24.156.2 ) from the neighbour switch or other services on this VLAN
for example cant ping the DHCP on this vlan from WLC.
The neighbour switch can ping IP of the management interface created on the WLC
WLC cant ping VLAN 108
WLC can ping all other VLAN 102,104,106
Not sure where the problem is ??
Configure Dynamic Interfaces on the WLC for the Guest and Internal Users - DONE
Create WLANs for the Guest and Internal Users - DONE
Configure the 5406zl Layer 2/3 Switch Port that Connects to the WLC as Trunk Port allowing the relevant vlans i.e. management vlan, vlan 102 and Vlan 108 - DONE
Configure the Switch Port that Connects to the AP to VLAN 102 - DONE
configure virtual interface IP 1.1.1.1 - DONE
Configure the Router for the WLANs - DONE
LAP is registered to the WLC - DONE
WLAN and SSID broadcast - OK

Not at present it is not, the port on the 5406zl that the WLC is connected was setup as a trunk group and All VLAN tagged. When I tried this I lost all connectivity to the WLC. Is there something on the WLC that need changing also?.

WLC 2125 - Country code selection

WLC Mode: AIR-WLC2125-K9
Version: 7.0.116.0
Here is the scenario, we have two WLC, one is located at SG and the other is located at MY (In test stage).
Both WLC has configured with three Country Codes CN,MY and SG , as well as the Regulatory Domain 802.11a -CS and 802.11bg -ACE).
Yesterday we did perform WLC failover test and it was successful but we noticed some of the APs country code are incorrect set as before, we are tried into the AP config, and pull up the Advanced Tab and select the Country where the AP is physically located but the weird issue happened whereby there are only one country code available and the other two country code are missing.
Here is the AP model we used.
AIR-LAP1142N-N-K9 (CN)
AIR-LAP1242AG-S-K9 (SG and MY)
Could someone help to advise what would be the cause how to resolve this issue.
Thanks in advanced.

With the -E there are many profiles that can be selected, as most tend to be very close to the same restrictions.
However I would contact your local regulatory domain group and ask them which country is the same as Mongolia. Explain what you are doing and have them tell you, and get it in writing. that way you are covered on your choice.
Steve
Sent from Cisco Technical Support iPad App

WLC 2125 IOS version for L3 ap-mode?

hi,
i tried to search about this but still no sucess. can someone please tell me if what correct version of IOS for wlc that i can use to support L3 ap-mode?
here is my current version;
NAME: "Chassis" , DESCR: "Cisco Wireless Controller"
PID: AIR-WLC2125-K9, VID: V05, SN:
Burned-in MAC Address............................ 68:EF:BD:04:55:2A
Press Enter to continue or <Ctrl-Z> to abort
System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 6.0.188.0
RTOS Version..................................... 6.0.188.0
Bootloader Version............................... 4.0.191.0
Emergency Image Version.......................... N/A
Build Type....................................... DATA + WPS
thanks in advanced!
cheers,
reymon

Hi Reymon,
The below link will answer your question...
http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52ovrv.html#wp1069102
that is..
Controller software release 5.2 or later supports only Layer 3 CAPWAP mode, controller software releases 5.0 and 5.1 support only Layer 3 LWAPP mode, and controller software releases prior to 5.0 support Layer 2 or Layer 3 LWAPP mode.
Regards
Surendra

WLC 2125 - Lab setup

Good Afternoon,
I'm trying to setup a WLC lab here at work and I'm having a few issues. I'm trying to plug an AP directly into the WLC and I'm having issues with the AP getting an IP using the Internal DHCP server option.
Is this setup not going to work without a switch involved? Unfortunately, I don't have a switch available for use, but I'm trying to find anyway to setup this controller to have DHCP that can serve my AP an IP address to join the controller.
Any advice or help will be grateful. I can also provide my management and ap-manager information if needed. Also, I do have DHCP proxy enabled.
Matt Cooper

Hi.
the internal DHCP server is for clients. it can provide IPs to clients that connect over wireless. It does not provide IPs to anything on the wired side. So, its not going to work with your situation.
If you can't set up a switch and configure it with a DHCP pool to serve the APs what you can do is to configure a static ip on the AP.
check here: http://goo.gl/tEOdAa
Note: in the commands in the above link, if the keyord "lwapp" didn't work with you you try using the keyword "capwap". (using of either keywords depends on your AP model).
Regards,
Amjad

WLC 7.4 with ACS 4.1

Hi All
Has anyone any experience of using a Cisco 5508 controller (code version 7.4.100.0) with an ACS appliance running version 4.1 or 4.2?
I've found that the ACS constantly reports a 'Bad request from NAS' (Invalid message authenticator in EAP request). message. This usually indicates a mismatched shared secret but this isn't the case.
The controller works fine opposite a Microsoft NPS Radius Server.
Regards
Roger

By default the NAS-ID on the WLAN is the hostname of the WLC. If that is changed and the WLC was rebooted, then the NAS-ID that will be seen by the radius is that under the WLAN. The Radius server Overwrite interface will change the NAS-ID to the dynamic interface and not the management interface.
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

WLC 2125 Rebooting

Similar Messages

Maybe you are looking for