AP Fallback not working with Cisco 4402

[Chellis Dodge]

Hello everyone,

I have an issue with AP Fallback not working with two Cisco 4402-50 WLC's.  Here is the senerio:

Site 1 has a 4402 (WLC01) running software 7.0.220.0 with 48 associated access points. AP Fallback is enabled in Controller > General and all 48 AP's are set to Critical failover with WLC01 being the primary controller and WLC02 (at site 2) being the secondary.

Site 2 is the location of WLC02 which is also running software 7.0.220.0 but has 0 ap's associated and also had AP Fallback set to enabled.

Your typical active/passive setup

The problem is when WLC01 goes down all of the AP's fail over to WLC02, however when the connection is restored to WLC01 we have to manually reboot each access point in order for them to reassociate back to the primary controller. Isn't AP Fallback enabled suppose to allow the AP's to move back to the primary controller once connection is reestablished?

Thanks in advance.

-Chellis

[Scott Fella]

FYI.

• Make sure that the DMZ and local WLC in the wired network are reachable. Use mobility pings (eping and mping) to test.

• Mobility ping over UDP—This test runs over mobility UDP port 16666 and tests whether the mobility control packet can be reached over the management interface.

mping mobility_peer_IP_address

• Mobility ping over EoIP—This test runs over EoIP - IP port 97 and tests the mobility data traffic over the management interface.

eping mobility_peer_IP_address

Note: Only one mobility ping test per controller can be run at a given time.

• If there is a firewall present, make sure that the UDP port 16666 and IP port 97 are opened for communication between the WLCs.

Thanks,

Scott Fella

Sent from my iPhone