I know I need to supply more detail - still gathering all that. Just hoping someone else has seen something similar and may be be able to shortcut the problem siolving. Customer has MC3090s (CE5) running fine on the Cisco network. Now, using the same wireless configuration the MC3190 (Wm6.5) is behaving very different in the same Cisco network. The MC3190 seems to want want to roam more frequently than the Mc3090, and when it does it has trouble - it flitters between two APs and won't stay stable. The MC3090 in the same position stays stable and connected to the same AP. The wireless security being used is LEAP - TKIP.
MC3190 roaming issue on Cisco backbone// Expert user has replied. |
11 Replies
Have a look on this SPR : 19757 The patch solved my issue on MC9500 and CISCO infrastructure.
I have a similar roaming issue with MC3190 WM6.1 under Cisco EWLAN. Customer deployed 9 Cisco Aironet 3500 AP's and CT5508 controller using PEAP EAP-GTC/Token authentication. They have installed Fusion v3.00.2.0.007R. MC3190 does not even roam and cannot associate to "a" radio. Also had a similar case with Zyxel AP's. Can I use the patch from SPR19757 here? If yes pls upload it. Is it worth to upgrade terminals to WM6.5? Thanks Roland
I also had a case where the MC9590 in WM 6.1 was much slower than the WM6.5 upgrade with the base fusion of 3.0.0.0.0.058R . They did see much better response times after applying the upgrade. The cisco network has the dtim and other settings like we suggest for mobile computers. We tried updating the newer version of Fusion 3.0.0.2.0.008R and response was worse so we reverted back to the above configuration. They were seeing drops in connectivity.
Look into SPR# 20363. I'm told that this SPR is vigorously being worked. This may not be specific to the MC3190 because other MPA2.0 platform devices have been reported to have similarly described issues.
Thanks for the responses. My issue is now part of SPR#20363, and I have been dealing directly with engineering on this. I suggest you monitor the progress of this SPR if you believe your issue is related.
Just curious what OEM version and Fusion version your customers are using? I have a support case with a customer that is reporting connection issues on a Cisco network with the MC3190 and they said it works fine with OEM 27 but fails with OEM 37. They have tested with the latest version Fusion 8R on each OS and it does not make any difference. It seems the issue is related to the OS and not the Fusion version. Thanks, Tony
We have tested and replicated with the following fusion versions. 3.00.2.0.006R, 3.00.2.0.008R
We have also tested with OS/BSP version. WM6.5 OEM: 2.27.0006, WM6.5 OEM 2.27.0006, CE6.0 OEM: 93.26.0000 (beta).
We had this issue woith one of the customers. They had a warehouse full of MC3090 and started deploying MC3190. MC3090s were working fine, but MC3190 were flipping all the time (and it was MOTO WLAN!). But when took the unit to another warehouse - everything was working fine. So I forced them into re-building their WLAN config from scratch (They had WS5100 upgraded from 2.x with those config upgrade scripts and never tried to clean up the mess) and doing a site survey, after which the problem disappeared. We haven't nailed down the root cause, though.
I just want to add, that I am just fighting a similar case, trying to convince the customer to optimize his WLAN. My customer is using MC9590 with the latest OEM and all new Fusion on a Cisco WLAN. The old Intemec just do fine with this not well managed WLAN, but our devices roam like crazy even without any movement and a good carrier on hand.
Did you manage to get a resolution on this? I've just had the same thing reported to me from a customer. WT4090s and VC5090s working fine on site, MC3190s bouncing on and off the wireless. IJ
Is there any chance to change AP's config? I guess the problem is with CCX compatibility implementation on both terminals. So maybe...