Are you sure you don't see primary and secondary controller's IP addresses on the command "show capwap client config"?

If configured, primary, secondary or tertiary WLCs appear on the output of this command like this:

mwarName               WLC1

mwarIPAddress        x.x.x.x

mwarName               WLC2

mwarIPAddress        y.y.y.y

mwarName               WLC3

mwarIPAddress        z.z.z.z

Where, WLC1 is the primary, WLC2 is the secondary and WLC3 is the tertiary.

Note that the listing order determines which one is primary and which is secondary...etc. (first listed is primary, second is secondary..etc).

You double check the output of your command.

You can take Leo's advice about testing HA without reloading the WLC, but you can also check HA per AP basis. Try adding one ACL that prevents specific AP from communicating with the primary WLC and wait to see if it will join the secondary or not.

HTH

Amjad

You want to say "Thank you"?
Don't. Just rate the useful answers,
that is more useful than "Thank you".

Just to add, makes sure you follow and understand this guide regarding ap failover. When you have this configured, you can either test with a single ap by switching the primary and secondary. Or you can console/telnet/ssh to the ap and issue:

test capwap controller ip

Use the ip address of the other wlc.

http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008064a294.shtml

Sent from Cisco Technical Support iPhone App