Clients Freeze when MSE is deployed ?

Question

Hi All
I just wanted to ask the community if anyone has ever experienced this problem.
Problem description:
At a customer we where making a small test with MSE, and a couple of tags.
When we enabled / setup the MSE in NCS, and enable synchronization with the controller that was running the APs in our location, all of the clients (a Bar code scanner) the customer uses in his production started to freeze.
There was simply no reponse from the operating system, just plain frozen.
Rebooting the devices didn't solve the problem either. The minute they had started up, they froze.
The APs in the affected productionarea, was also under the control of the WLC we where using for our small test.
All other production areas, with APs not associated to this controller, where not affected.
Other types of clients in the area where also not affected (PCs, smartphones, tablets and so on) only the bar code scanners.
The scanners are using a 802.11g NIC from Summit http://www.summitdata.com
The client are being reported as supporting CCX v4 in NCS.
The minute we shut down the MSE everything returned to normal (maybe after another reboot of the clients, I cant remember).
The customer has also made another test with the client, where he has turned off CCX in the NIC properties.
When doing this the client does not freeze.
/End Problem description.
So what could be the problem ? and has anyone else experienced something like this ?
I speculate that the client NIC hears some addition to CCX relating to location, and fails (catastrophically) because it does not understand this addition.
I know that tags send out CCX tag information, that the wireless system then hears, processes and sends to the MSE.
But does the wireless system start to send out, or request new information from normal CCX clients when enabling MSE ?
Just looking for some logical explanation :-)
/Thomas

Answer 1

I've also just encountered a failure to associate using LXE MX9 scanners with a Summit card. Moving the setting from CCX FULL to CCX OPTIMIZED in the SCU resolves but is not a recommendation from Honeywell/LXE. have you had any response from TAC or Teklogix?