Tony1234,
Again, I have never been in an environment that required that to be changed. You first need to know:
- Is the user repeatedly connecting to G, because the power on the G band is too high? If so, lower the power on the G band so that the client can select the A band way ahead of client-match kicking the user off onto the other band.
- If you modify the clientmatch settings, you could have users that constantly get kicked to A, but return to G, because your power is too high on G. Your clients will notice this and it will be disruptive. You need to reduce the power on G, first.
To see what your clients are doing on clientmatch do this:
config t
logging level debugging user subcat client-match
Then type:
show log user all | include client-match
That will allow you to understand why client-match is making decisions. 90% of RF issues can be helped or prevented by setting the correct power. The remaining can be helped by Client Match on default settings after the client has already made a poor decision...