WLC 4402 upgrade to 7.0.235.3 -- high latency

Hi All,
Since we've upgraded the 4402 (from 4-2-176-0) to 7.0.235.3 many client facing very high latency.
We're having 12 x 1142 APs and they are connected in local mode to WLC.
Before the upgrade performance was good. Now, when I ping from LAN to WLAN clients it takes from 0.1ms - 20s.
64 bytes from 10.123.60.210: icmp_seq=58 ttl=127 time=4711 ms
64 bytes from 10.123.60.210: icmp_seq=59 ttl=127 time=3711 ms
64 bytes from 10.123.60.210: icmp_seq=60 ttl=127 time=2712 ms
64 bytes from 10.123.60.210: icmp_seq=61 ttl=127 time=1713 ms
64 bytes from 10.123.60.210: icmp_seq=62 ttl=127 time=754 ms
64 bytes from 10.123.60.210: icmp_seq=63 ttl=127 time=3.12 ms
64 bytes from 10.123.60.210: icmp_seq=64 ttl=127 time=1109 ms
64 bytes from 10.123.60.210: icmp_seq=65 ttl=127 time=109 ms
64 bytes from 10.123.60.210: icmp_seq=66 ttl=127 time=0.949 ms
I cant find any pattern..seems to happen to random clienst at radom time.
Any ideas..or further checks I can do?
Thanks a lot,
Stefan

All is set to auto.

Similar Messages

WLC 4404 Upgraded to 7.0.235.3 (WPA HandShake Timeout) not availbale

Greetings,
Just upgraded my Cisco 4404 WLC's to 7.0.235.3, the upgrade went just fine. My problem is when I either Telnet or SSH to my Lightweight AP's and run the "DOT11 WPA Handshake Timeout 1000" command the AP doesn't recognized this command. This is one of the reasons I upgrade my WLC's.I have several wireless printers that are passive and are heavily used and keep getting disassociated because they don't respond in time.
Any Help would be greatly appreciated.

that command is for IOS AP, not for the WLC.
Q.    How do you change the Wi-Fi Protected Access (WPA) handshake timeout   value on a Wireless LAN Controller (WLC) through CLI? I know I can do this on   Cisco IOS® Access Points (APs) with the dot11 wpa handshake   timeout value command, but how do you   perform this on a WLC?
A. The ability to configure the WPA-Handshake timeout through the WLCs was       integrated in software release 4.2 and later. You do not need this option in       earlier WLC software versions.
These commands can be used to change the WPA Handshake timeout:
    config advanced eap eapol-key-timeout
    config advanced eap eapol-key-retries
The default values continue to reflect the WLCs current       behavior.
   - the default value for eapol-key-timeout is 1 second.
   - the default value for eapol-key-retries is 2 retries
Note: On IOS APs, this setting is configurable with the dot11           wpa handshake command.
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

Rolling upgrade of WLC 4402 controllers and APs

In need to upgrade the software on two WLC 4402 controller in a hospital. Both WLCs have the same config and one is primary (has all APs connected) and the other backup (no APs connected.) The APs are placed so there is still coverage if one goes down in an area. My question - is it possible to do a rolling upgrade to have no downtime for the wireless clients? My plan would be to upgrade the backup WLC then selectively move APs to it. If I swap the primary and secondary controllers in the high availability tab on each AP, do I need to do a reset (General - Hardware Reset) or will it automatically reboot and connect to the upgraded backup controller? When I'm done, I'd upgrade the primary controller and now call that backup. Does this make sense?

I've done this same sort of thing on a slightly larger scale about 5 times now at the hospital I work at. Quick answer is "Yes, it is possible to do a rolling upgrade and have no downtime for wireless clients."
I've got 5 WLC's, and I use the high availability tab to move all the AP's off one, upgrade it, and move all the AP's from the next WLC over to it, upgrade that one, etc.
The thing you need to be careful of is your timing and your choice of APs to move.
It generally takes about a minute to move an AP between WLCs running the same version. But if there's a version change that makes the AP upgrade, you're looking at about 6 minutes.
I do them one at a time, and when they show up in the WLC as being up, running and happy for 1 minute, I do the next one. And so on. Takes me about 3 days to go through all 5 WLCs and 375 APs. Not once have I had a user notice the move.
Also, in order to test, after I do the first upgrade, I move just one area's APs into that WLC for a day and then test the various flavors of gear we have (phones, infusion pumps, laptops, etc.) to confirm that the new version doesn't have any trouble. Sometimes it does and I work with TAC to get things resolved before I do the whole hospital.
jh

Upgrading from WLC 4402-50 to WLC 5508-250

I am planning to upgrade my WLC 4402-50 (HA) to WLC 5508-250 (HA). I also have some really old 1020 Access points that I will be replacing with 1142's. Once I have completed the upgrade to the 5508s, I will repurpose the 4402's as Mobile Anchor controllers to support Guest Wireless.
Does anyone have any actual experience with this sort of upgrade? Any practical suggestions or ideas??
Thanks,

Hi,
Are you still facing this issue? if yes try checking the link if that helps
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
thanks,
Vinay

Upgrade from 7.0.235 to 7.0.240 5508 WLC

Does anyone see a reason to upgrade from 7.0.235 to 7.0.240? I can't go any higher right because we are still using WCS. I read the white papers but as far as I can tell there are no new features..

Leo is a risky Australian.... beware
You might be able to get it to work, just Cisco will not support it. They need to keep the LifeCycle going $$$$$$$
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"

Problem to register upgraded AP 1242 to WLC 4402

Hi,
I am running a small Cisco WLAN with about 20 APs (all 1242) that are managed by two WLC 4402 (running v4.0.155.0).
WLCs are in Mobility group, serveral WLANs/VLANs are configured (including 802.1x, guest access with WebAuthentication etc.). All APs are configured for the same WLC as primary and the other as secondary. Everthing was working fine until I tried to upgrade another AP from IOS to LWAPP using the Cisco Upgrade tool.
After the AP was flashed and rebooted it started to discover a WLC but fails. The console messages look like this:
*Mar 1 00:00:05.962: %CDP_PD-4-POWER_OK: Full power - AC_ADAPTOR inline power source
*Mar 1 00:00:06.952: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:07.952: %LINEPROTO-5-UPDOWN:
ap> Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:25.960: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
Translating "CISCO-LWAPP-CONTROLLER.xxx.yyy"...domain server (10.x.y.z)
*Mar 1 00:00:35.348: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.x.y.z, mask 255.255.254.0, hostname AP0019.3076.fe30
*Mar 1 00:00:36.349: LWAPP_CLIENT_ERROR: lwapp_name_lookup - Could Not resolve CISCO-LWAPP-CONTROLLER.xxx.yyy
*Mar 1 00:00:46.398: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:54.397: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response
*Mar 1 00:00:54.397: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
*Mar 1 00:00:54.397: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
*Mar 1 00:00:54.398: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
The switchport of the AP is configured for the same VLAN as the management and ap-management interface of the controller (not native VLAN), the primary controller is set to master controller mode and I see no other error messages (e. g. on the WLC).
Does anyone know how to fix this problem?
(even adding a "CISCO-LWAPP-CONTROLLER" host in the DNS does not help!!!)

Hi Ankur,
here the output of "dir flash:"
dir flash:
Directory of flash:/
2 -rwx 1048 Aug 14 2007 14:29:38 +00:00 private-multiple-fs
3 -rwx 314 Mar 1 2002 00:00:57 +00:00 env_vars
156 drwx 128 Aug 14 2007 14:29:32 +00:00 c1240-rcvk9w8-mx
10 drwx 256 Aug 15 2007 07:15:47 +00:00 c1240-k9w8-mx.123-11.JX
15998976 bytes total (11196416 bytes free)
AP0019.3076.fe30#
Is there something wrong?
Kind regards,
Hagen

WLC 4402 7.0.220.0 compatability.

hello friends,
Could you please let me know if Windows 8 laptops machine are conpatible with the WLC IOS Version 7.0.220.0.
My client has WLC 4402 Version 7.0.220.0.
The message that appears is AAA authentication failed.
Your help will be highly appreciated.
Warm Regards
Nelson Mathias

You need 7.0.235.3 as a minimum. Here is a reference guide.
https://supportforums.cisco.com/docs/DOC-27213
Sent from Cisco Technical Support iPhone App

WLC 4402-50 with ACS 3.3

Hi,
We want to use ACS to authenticate an ssh or http connection to a WLC 4403-50 4.2.99 using TACACS+. On our ACS 4.2 test server it works fine. Configured identically on an ACS 3.3 appliance we are not able to log in although we do see a successful login in the Passed Authentications report withing ACS.
Is there an incompatability between the WLC 4402-50 with ACS 3.3?
thanks
Bob

The Cisco Secure Access Control Server (ACS) provides authentication, authorization, and accounting (AAA) services for users of the wireless network.
It is also possible to employ a WLC controller strategy that uses an N+1 approach. When using N+1 architecture, each WLC is configured with a WLC that is designated as a backup WLC in the event of a failure. This controller is not used until there is a failure event upon which all APs using the failed controller switch to the backup WLC. This cost-effective approach provides a high level of availability in the event of a single WLC failure scenario.

Wireless controller ha between wlc5508 and wlc 4402

We have 2 wlc: a wlc 5508 ( license 100 AP ) and wlc 4402 ( license 12AP).
We try to setup when 5508 down, 12 identify AP (important AP -Group A) will join 4402 and all other AP (not improtan AP -Group B)
wont joint wlc 4402.
First, all AP join wlc 5508, 2 WLC have same mobility group.
After that, we config 12 APs belongto group A have primary and secondary wlc, group B only has primary wlc.
When wlc 5508 down, some of APs of GroupA and some of APs of GroupB join wlc 4402. We test many times and we have differnet result each times.
is theare any way to resolve our problem?
Thanks.

Just to add, make sure that the WLC is running the same code, if not, then make sure the ap is supported on the code that is running on the 5508. The issue with mixed code is the ap will upgrade and downgrade very time they switch to a different WLC.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Sent from Cisco Technical Support iPhone App

Bonjour / iChat working across wlc 4402

I have a L3 switched LAN (Cat4510 at the core with 3560 to the edge), and a WLC 4402 [s/w 4.0.217.0] providing wireless access. There is a multitude a PC's and MACs that sit on the wired and wireless network.
I currently am having issues getting a Apple tool called Bonjour working across the wireless network.
I have done some reading and from what I can gather it uses mdns (which uses udp 5353 / 5354). I have enabled Multicast Routing on the Cat4510 and enabled on the WLC 4402 Ethernet Multicast Mode with a group address of 224.0.0.1, however still cannot get Bonjour clients talking.
Admittedly the blogs I have read and Tech pages on Apple do not give up anymore info than this. Has anyone had experience or come across this before?

Found something interesting on this.
Apparently, apples do not like multicast using IANA Administratively Scoped Block range of 239.0.0.0-239.255.255.255.
I was using 239.0.1.100 and nothing was connecting, I then changed it to 235.0.0.1 and all is well.
Go figure.
ref: http://www.cisco.com/en/US/tech/tk828/technologies_white_paper09186a00802d4643.shtml#wp1011111

WLC 4402 update softwar

hello everybody,
actually i'm confused so i want to upgrade my WLC 4402 from 6.0.199.4 to last version available and i have my AP 1242G with version 12.4(21a)JHB1 I just want to know what's the version compatibility beween my WLC and AP,thank you for your helps

Hi,
Go for 7.0.250.0(It is the last supoort version for this WLC). You can directly upgarde from 6.0.199.0 to 7.0.250.0.
http://software.cisco.com/download/release.html?mdfid=279911193&flowid=7586&softwareid=280926587&release=7.0.250.0&relind=AVAILABLE&rellifecycle=ED&reltype=latest
And 1242 AP supported this software.
Cisco Wireless Solutions Software Compatibility Matrix
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
Regards
Dont forget to rate helpful posts

WLC 4402 - APs last reboot reason power loss

st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Normale Tabelle";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
Hi,
we have a Wireless LAN Controller WLC 4402, Software Version 4.1.192.22M (Mesh).
At the moment there are 6 Access Points in one house, one of them is the root AP. The others are only connected via electrical socket.
AP’s are: AIR-LAP1131AG-E-K9 / Boot Version 12.3.8.0 / IOS Version 12.4(3g)JMC1
I think the configuration worked fine over a period of 2 years.
Now the problem is that the number of access points connected to the controller is changing nearly every minute. At times there is only one AP connected to the controller. So it is impossible for the clients to build up a steady connection. They have to log in via the guest user web interface at short intervals or they can’t see the wireless lan.
First we thought it would be a problem of one or two “defect” access points. But we replaced 4 of the 6 access points and the problem is still there.
An example, yesterday:
13:17 o’clock – 2 AP’s
13:19 o’clock – 4 AP’s
13:21 o’clock – 5 AP’s
13:23 o’clock – 4 AP’s
13:25 o’clock – 5 AP’s
13:25 o’clock – 4 AP’s
13:26 o’clock – 5 AP’s
13:26 o’clock – 6 AP’s
13:28 o’clock – 4 AP’s
13:28 o’clock – 2 AP’s
Eye-catching is the following message of the log, which appears often: “52       Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
Also eye-catching is the AP up time. The Root AP is up for over 80 days. But all the other access points show an up time of a few minutes until some hours…but not more.
Does anybody know what the problem could be?? I read some similar threads but no solution.
In the following an abstract of the log:
21        Mon May 16 13:25:43 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
22        Mon May 16 13:25:30 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
23        Mon May 16 13:25:30 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
24        Mon May 16 13:25:30 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
25        Mon May 16 13:25:05 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
26        Mon May 16 13:24:10 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
27        Mon May 16 13:24:10 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
28        Mon May 16 13:24:10 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
29        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
30        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
31        Mon May 16 13:23:59 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
32        Mon May 16 13:23:59 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Admin Configured
33        Mon May 16 13:23:58 2011        AP 'AP001d.45d8.4ea6', MAC: 00:1d:71:e1:b2:20 disassociated previously due to AP Reset. Last reboot reason: power loss
34        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
35        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
36        Mon May 16 13:23:31 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
37        Mon May 16 13:23:31 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Admin Configured
38        Mon May 16 13:23:30 2011        AP 'AP001d.e557.6f0c', MAC: 00:1d:70:01:b5:a0 disassociated previously due to AP Reset. Last reboot reason: power loss
39        Mon May 16 13:23:13 2011        Client Association: Client MAC:00:1d:71:e1:b2:2f Base Radio MAC :00:1d:70:01:bc:20 Slot: 1 User Name:c1130-001D45D84EA6
40        Mon May 16 13:23:13 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
41        Mon May 16 13:23:04 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:23:5e:49:9d:e0' from mesh node '00:1f:ca:cc:b7:40'.
42        Mon May 16 13:22:57 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
43        Mon May 16 13:22:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
44        Mon May 16 13:22:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
45        Mon May 16 13:22:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=New Discovery
46        Mon May 16 13:22:39 2011        AP 'AP0021.d847.ffca', MAC: 00:23:5e:49:9d:e0 disassociated previously due to AP Reset. Last reboot reason: power loss
47        Mon May 16 13:22:17 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1d:70:01:bc:20' from mesh node '00:1f:ca:cc:b7:40'.
48        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
49        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
50        Mon May 16 13:21:57 2011        AP's Interface:1(802.11a) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
51        Mon May 16 13:21:57 2011        AP's Interface:0(802.11b) Operation State Up: Base Radio MAC:00:1d:70:01:bc:20 Cause=Admin Configured
52        Mon May 16 13:21:56 2011        AP 'AP001d.e557.6fd8', MAC: 00:1d:70:01:bc:20 disassociated previously due to AP Reset. Last reboot reason: power loss
53        Mon May 16 13:21:39 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
54        Mon May 16 13:21:32 2011        Client Association: Client MAC:00:23:5e:49:9d:ef Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-0021D847FFCA
55        Mon May 16 13:21:12 2011        Mesh child node '00:1d:71:e1:b2:2f' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:b5:a0'.
56        Mon May 16 13:21:05 2011        Client Association: Client MAC:00:1d:70:01:bc:2f Base Radio MAC :00:1f:ca:cc:b7:40 Slot: 1 User Name:c1130-001DE5576FD8
57        Mon May 16 13:20:32 2011        Mesh child node '00:23:5e:49:9d:ef' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
58        Mon May 16 13:20:11 2011        Mesh child node '00:1d:70:01:bc:2f' is no longer associated with mesh node '00:1f:ca:cc:b7:40'.
59        Mon May 16 13:20:06 2011        Mesh child node '00:1d:70:01:b5:af' has changed its parent to mesh node '00:1f:ca:cc:b7:40' from mesh node '00:1d:70:01:bc:20'.
60        Mon May 16 13:19:57 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:b5:a0
61        Mon May 16 13:19:57 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
62        Mon May 16 13:19:57 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:b5:a0 Cause=Heartbeat Timeout
63        Mon May 16 13:19:49 2011        AP Disassociated. Base Radio MAC:00:1d:70:01:bc:20
64        Mon May 16 13:19:49 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
65        Mon May 16 13:19:49 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:70:01:bc:20 Cause=Heartbeat Timeout
66        Mon May 16 13:19:39 2011        AP Disassociated. Base Radio MAC:00:23:5e:49:9d:e0
67        Mon May 16 13:19:39 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
68        Mon May 16 13:19:39 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:23:5e:49:9d:e0 Cause=Heartbeat Timeout
69        Mon May 16 13:19:36 2011        AP Disassociated. Base Radio MAC:00:1d:71:e1:b2:20
70        Mon May 16 13:19:36 2011        AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
71        Mon May 16 13:19:36 2011        AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:1d:71:e1:b2:20 Cause=Heartbeat Timeout
Greetings Lydia

st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Normale Tabelle";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
Hey,
last week I tried to upgrade the controller step-by-step.
Under the software 4.1.192.35M the problem was still there… access points were often disassociated from the controller.
There were problems with Software 4.2.207.54M too. The access points couldn’t reach the download-status. The log of the access point said that it could not open the tar-file.
So I went back to 4.1.192.35M. Of course the controller lost some of its configuration. I configured it new with the same settings as before.
After it the wireless connection seemed to be a little bit more robust. I asked the users to test the connection at the weekend and this is the answer:
“so we tested the WLAN during the weekend. The situation definitely improved with respect to before. Authetication is much faster and the connection (when active) is sensibly faster.
However the connection is still very unstable and it is necessary every five-ten minutes to reconnect (especially for intense network traffic like when watching a streaming content or using VOIP applications. Actually switching off and on again the WLAN card (Airport) often a new authentication is not required. However, without doing so the connection would not resume alone to a working state.
So what to say? Better than before (thanks) but far from being fixed. From last September to January we did not experience any problem, so it must be something that chronologically happened at the beginning of the year, it is not a systemic problem.
But there were no changes or anything else at the beginning of the year.
Do you mean it makes sense to resume upgrading? I’m a little bit afraid of more problems like under 4.2.207.54M
Greetings Lydia

Wlc 4402 errors when trying to join ap

Hello,
I have a wlc 4402 controller with software version 6.0.199.4
now i have problems adding 1131 aps to my controller.
in the pas i added 15 access points (withouts problems) but
now doesn't seems to work anymore.
here's what i got from controller when trying to join
*Nov 11 12:24:37.739: %LWAPP-3-RADIUS_ERR: spam_radius.c:138 Could not send join reply, AP authorization failed; AP:00:13:c4:93:c1:58
here's what i got on the AP (console cable on my pc when booting)
%LWAPP-3-CLIENTERRORLOG: LWAPP Crypto Init (SSC): no certs in the SSC Private File
Got an idea on this ?
thanks for help

Was the AP in automatic mode before? Did you copy the LWAPP recovery image to the AP using tftp?
All APs manufactured before 2005 or 2006 do not have MIC (manfacture install MIC) installed. You need to use LWAPP conversion tool to convert the AP to LWAPP/CAPWAP; so that the conversion tool will install SSC (Self Signed Certificates) to build the encrypt the LWAPP/CAPWAP control traffic:
http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html
As LWAPP discovery image is already there, you need to convert the AP back to autonomous mode and use LWAPP conversion tool to conver the AP:
http://www.cisco.com/en/US/docs/wireless/access_point/12.3_8_JA/configuration/guide/s38trb.html#wp1058472
I hope that the mode button is not disable on the AP. if it does, I hope that the break key is not disable. If both the mode button and break key are disable, you need to RMA the AP.

Help required with WLC software upgrade

I have a customer with WLC 4402 in use, running software version 7.0.98.0, and supporting 11 APs at present. The customer wants to enlarge the WLAN, which involves increasing the number of APs. I have purchased a new WLC5508, and have installed it onto the network alongside the 4402. the 5508 is running software version 7.0.116.0. Because the wireless network is critical to the user, we want to move the APs over to the new controller while the network is up and running, then remove the 4402.
However, when we set the 5508 as the master controller, or tell one of the APs to use the 5508 as its primary controller, the AP connects to the new controller, downloads the new software version, attempts to load it but reports an error with the unzipped file size of the software and fails to boot. formatting the flash on the AP, then disconnecting the 5508 from the network and rebooting the AP allows it to connect to the 4402, it downloads the older software and boots as normal. A new AP, if connected to the 5508 in a test scenario (ie no 4402) connects, downloads and boots perfectly.
I have the upgrade software to allow the 4402 to be upgraded to 7.0.116.0, but I am concerned that, if this is installed, the existing APs will then fail to boot from the 4402 or the 5508.
all APs are 3502s, running IOS version 12.04(23c)JA when connected to the 4402 and 12.04(23c)JA2 on the 5508.
Any suggestions would be gratefully received
Thanks

Hi Pat,
thanks for the reply. I am off site until the morning, but will attach the colsole output tomorrow.
Your mentioning a corrupt image makes me wonder - we had a lot of trouble setting up the initial config on the new WLC, getting a lot of launch failures. Eventually things seemed to settle down (it certainly booted successfully first time this morning) and getting an AP to connect without a problem made me hope it was just a quirk of the configuration wizard, but I think I will try a reboot of the WLC before I do anything else, just to check it is stable.
If it is a corrupt image it may take a little while to sort, as we have not as yet got a support contract on the 5508 - the plan was to upgrade the existing contract on the 4402 once they were swapped out, but I'll let you know whats going on
Rob

WLC-4402 : Users complaint slow down load

Hello
My users complaint the down load speed is slow when using wireless. I checked and indeed is slow.
Before this happen, my WLC is running 802.11b/g. So my thought maybe the 802.11b can slow down
on the users so I changed WLAN to run on 802.11g only. Well, it is still slow. If anyone has any idea
on this is appreciated.
The WLC-4402 is running on version 4.1.185 and all 19 LAPs is 1242AG with IOS version 12.4(3g)JA2

OUCH...
"Channel Utilization is depending on what channel and is changing from time to time.
Channel 1 is between 17 and 62, Channel 6 is between 9 and 33, and Channel 11 is between 28 and 45"
Do your APs have 802.11a radios? If so, move your asscoation to the 802.11a side and run your test... Your channel utlization is high, very high. I assume you have 1 PHY rate set to mandatory and lower data rates are enabled 1,2,5.5 ?
Lets clean up the utilization first and see the results before you go further...
Test the 802.11a side ...

WLC 4402 upgrade to 7.0.235.3 -- high latency

Similar Messages

Maybe you are looking for