Slow Data transfers but fast pings?

[aeccles]

Hi,

I've got a WLAN consisting of (2) 2106 controllers and (10) 1131AG APs. The controllers are in a Mobility group - same name, both can see each other, same virtual IP.

QoS is set to Silver (best effort).

I have a single SSID.

Currently only about 5 users.

APs are all associated and no errors any of the logs.

The issue is that I am getting very slow HTTP connections. Pings average 2ms across my entire network, but all other traffic is significantly slower.

I'm getting great signal strenght and very little RF interference.

If anyone has any suggestions please let me know - if any more specific info regarding my config is nesc. please let me know as well.

Thanks

[Scott Fella]

Port 4 shows as being connected. The vlan that you are using for management and for your wlan.... do you have NAT setup for subnet on your L3?

Port Summary

STP Admin Physical Physical Link Link

Pr Type Stat Mode Mode Status Status Trap POE

-- ------- ---- ------- ---------- ---------- ------ ------- ---------

1 Normal Forw Enable Auto 100 Full Up Enable N/A

2 Normal Disa Enable 100 Full 100 Full Down Enable N/A

3 Normal Disa Enable 100 Full 100 Full Down Enable N/A

4 Normal Disa Enable Auto Auto Down Enable N/A

5 Normal Disa Enable 100 Full 100 Full Down Enable N/A

6 Normal Disa Enable 100 Full 100 Full Down Enable N/A

7 Normal Disa Enable 100 Full 100 Full Down Enable Enable (Power Off)

8 Normal Disa Enable 100 Full 100 Full Down Enable Enable (Power Off)

[aeccles]

yep NAT is enabled - same subnet as the wired.

Port 4 says it's down - set to auto auto but it's down in what you posted there.

[Scott Fella · Accepted solution]

Yeah.. port 4 is down... dont know what I was looking at.

By the way, your wireless uers should be put on a different subnet than wired users. That might be your issue. Create a new dynamic interface on the WLC. You will also need to create a new vlan and L3 interface for that subnet and make sure that subnet is nat'd.

[aeccles]

Hi Scott,

I worked with a handful of Cisco TAC engineers and we finally tracked it down. It was the the Mobility Anchor setting. The functionality of this setting on the 2106 differs from other Cisco WLCs and there seems to be some "undocumented functionality" (Cisco's term) that occurs when you use it on the 2106.

Thanks for your help and time - greatly appreciated.

[Scott Fella]

Interesting... so you had mobility anchor configured? What was the fix?

[aeccles]

The fix was to disable it... Cisco had built a lab out to test it and basically said it wasn't acting as they expected on the 2106 - seems to be fine on the higher end controller modules however.