I've noticed a couple of problems with Client Match in firmware version 6.4.2.0-4.1.1.0_46028.
First, a problem where the mouse-over display fights with the cursor. I see similar behavior in both Chrome and Safari on Mac OS X. I can work around the problem by using Firefox, which doesn't have this issue.
The simplest explanation of the problem is probably a screen capture video:
(view in My Videos)
Second (and possibly more annoying): the MAC addresses shown in the client-view heatmap don't match any of the APs in my cluster. The first three octets (i.e. the manufacturer prefix) appear correct, but the last three octets are scrambled. Interestingly, these unknown MAC addresses also appear in the syslog output. For example, this is a line from my cluster's syslog:
Sep 30 16:40:17 2014 192.168.253.205 sapd[1535] <Notice>: <127004> <NOTI> <192.168.253.205 00:0B:86:CF:90:B2> |ids-ap| AP(00:0b:86:79:0b:28): Interfering AP: An AP detected an interfering access point (BSSID 6c:f3:7f:96:cb:78 and SSID on CHANNEL 44).
00:0b:86:79:0b:28 (the MAC shown in the screen capture video above) is NOT a member of the cluster, and AFAIK does not exist, but 00:0B:86:CF:90:B2 is in the cluster (and does have the .205 IP address).
This message doesn't appear in the latest version of the Syslog Messgages Reference Guide I have access to, so I'm not sure if I'm reading it correctly, but it looks to me like the "AP()" section is supposed to be the reporting AP.