1252's client bandwidth fluctuation + crash

Unanswered Question
Sep 23rd, 2008

I recently installed 10 1252's with TerraWave combined 2.4/5 Gigaherz antennas. While the coverage is great, the clients available bandwidth fluctuates greatly. Sometimes the client goes all the way to 1Mbps then bombs out. Reconnecting usually resolves the issue. We are very early in our project so usually there is not more then 1-2 users per AP. There are no link errors on the AP. My boss cant understand why he gets solid 45mbps from his linksys at home and at work speeds are all over the place. Please Help !

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Scott Fella Tue, 09/23/2008 - 17:21

Kind of hard to say... seems like it is a configuration issue. Post your show run-config... not the show running-config.

Scott Fella Tue, 09/23/2008 - 18:34

1. upgrade the boot image to 5.0.148.2 BOOT

2. configure your service port to an ip that is not part of your network. this has to be non routable... ex 192.168.250.10 255.255.255.0. Don't connect this to the network.

3. enable 802.11n (5 GHz) High Throughput, do not do this on the 2.4GHz.

4. configure the channel and power manually on the 5GHz band. This is required to enable 40mhz channel width.

5. enable 40mhz channel width on the 5ghz side.. either 40mhz above or below.

To configure 40mhz channel width above, ap must be set to one of these channels:

36,44,52,60,100,108,116,132,149,157

To configure 40mhz channel width below, ap must be set to one of these channels:

40,48,56,64,104,112,136,153,161

Also, you have peer to peer blocking an all your wlan's except for wlan 1. Is this what you want to do?

Try this and let me know.

jickfoo Wed, 09/24/2008 - 17:25

Thanks for your reply. I'm working toward implementing your changes.

I'm running image 5.1.151.0, I'm confused about how to upgrade just to boot image, or is it the bootloader version to 5.0.148.2 ?

Please help and thanks..

Scott Fella Wed, 09/24/2008 - 17:28

Just upgrade it the same as the code. You will need to reboot the wlc.

jickfoo Wed, 09/24/2008 - 17:32

I did, I dont think it took. How can I check just the boot version ? I dont see 5.0.148.2 anywhere in my show commands. The system runs 5.1.151.0, but that is different then the boot version right ?

Scott Fella Wed, 09/24/2008 - 17:54

Yes it is different. Run the show run-config. It is toward the top.

Scott Fella Wed, 09/24/2008 - 18:00

Sometimes it doesn't show. Bug of course, but if it didn't fail during the tftp then it's there.

jickfoo Wed, 09/24/2008 - 18:28

Anythoughts if this is upgraded ? Was I suppose to disable WLANS or something ?

System Information

Manufacturer's Name.............................. Cisco Systems Inc.

Product Name..................................... Cisco Controller

Product Version.................................. 5.1.151.0

RTOS Version..................................... Linux-2.6.10_mvl401

Bootloader Version............................... 4.0.206.0

Build Type....................................... DATA + WPS

This shows boot image 4.0.206.0 with image 5.1.151.0. The upgrade path is from 4.0 xxx to 4.2 then to 5.1

So something has gone wrong and I would sort this out and see what happens before going forward.

Product Version.................................. 5.1.151.0

RTOS Version..................................... Linux-2.6.10_mvl401

Bootloader Version............................... 4.0.206.0

Scott Fella Thu, 09/25/2008 - 17:04

If the upgrade of the boot image did not fail them the upgrade took. This is an issue that TAC knows of.

jickfoo Thu, 09/25/2008 - 17:19

Thanks.. I got up to 4.2.112.0, then from there I ran the 5-0-148-2-ER upgrade, but the bootloader still reads, 4.2.112.0.

This is in the readme, its confusing. Could it truely be that after running the BOOT code for 5.0.148.2, there is no way to see that its been installed ?

Unlike previous ER images, a new bootloader file is not loaded when you install the 5.0.148.2 ER.aes file. This is true for all controllers. The 4.2.112.0 ER.aes file is the last ER file to contain a bootloader. If you want the latest bootloader, install the 4.2.112.0 ER.aes file. If you want to obtain the fix for CSCsd52483, also install the 5.0.148.2 ER.aes file.

jickfoo Fri, 09/26/2008 - 03:55

So after I run that update, there is no way to actually verify that it successfully took the update? That's weird..

Scott Fella Fri, 09/26/2008 - 04:27

You are correct. Look at the other thread posted, I think it was wlc bootloader or something like that. Has info on which code actually changed to boot code.

pbuch Mon, 09/29/2008 - 10:56

A little strange, but according to the 5.1 documentation the 4.2.112.0 ER was released after 5.0.148.2 ER.

The newest bootloader is 4.2.112.0

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode