Andy, while this document works, there's absolutely no need to follow this approach with 5.2 (except some special cases, probably). The new join-cluster way is soooooooo much quicker and easier :) I saved about a hour of lecture/lab time with 5.2: I don't have to explain to students why they have to configure both devices on master controller, copy configs over, etc (and they make less mistakes configuring cluster). I know it takes 15 minutes to an experienced engineer to do this, but for someone who sees WiNG5 for the first time it is a pain... Instead, you configure cluster name on the 1st RFS, and you issue one command on the second - and you're done!

Thank you Arsen, for your candid feedback. We will update the release notes and repost. While on the subject, another edit that will be made is around multi-device termination wih Air Defense - that was also resolved in the last few days of release, so is no longer a known issue - that will also be updated in the next version. On the positive side, glad to know someone does read the release notes!

Arsen, Thanks. I have just been through this. I have attached a document which may help. I have followed section 4.1 and it seems to work although I have not robustly tested the setup. I tested using RFS4000 V5.2 and RFS6000 V5.2 (Not sure is this is supported as the WiNG 5.x clustering guide states):
"Also, only identical models of controllers can be clustered together, e.g. RFS4000 with another RFS 4000. This restriction rules out the possibility of a Wireless Controller being clustered with an AP acting as a Virtual Controller."
Regards, Andy