Guys, could you plz elaborate more on that or send me to the appropriate docs? I don't quite get what's the problem is in roaming between CCX-enabled and non-CCX-enabled network. Does "CCX-enabled" imply using some sorts of algorythms that prevent roaming?

Arsen, If you are using CCKM for "fast roaming" under CCX, then you would select to perform this CCKM/fast roaming in the Photon or Jedi radio which involves a Cisco proprietary authentication method (no matter what EAP method you are using for authentication).  We would then be hard coded to roam within APs advertising that they perform CCKM.  Although I still wouldn't promise anything will work, you may be able to get things working if you setup your Cisco APs to perform both CCKM and standard WPA enterprise, and setup the mobile computers to NOT use CCKM.  This would take away the benefit of CCKM for the mobile computer, but would possibly allow the roaming to work... however even this configuration has not been tested. -Dave

Not with the same ESSID.  When CCX first came out in fusion, the same ESSID would associate to either CCKM or WPA if both were enabled on the Cisco AP.  The problem was that if both are enabled, Fusion would always select the most secure protocol, which is WPA, and never use CCKM.  In your case, if you had fusion associate to either, you may never use CCKM keys and have the fast roams you want. Because of this, if you pick CCKM-WPA in the fusion profile, the device will only associate to CCKM EDSSID and not a WPA ESSID. SPR 12636 is where this behavior was found and adjusted.

Sorry, SPR12636 wasn't for the CCKM/WPA.  The Fusion Dev team fixed this as part of the beta testing process we were in.