This issue occurs when Wireless Domain Services (WDS) AP and the infrastructure access point (AP) are on different subnets. When an AP runs as the WDS, it does not support infrastructure devices on different subnets. The WDS can only run on an AP when the WDS and the infrastructure devices are on the same broadcast domain.This is because WDS advertises itself with Wireless LAN Context Control Protocol (WLCCP) multicast mesages which is not routable.When an Access point is configured as WDS take care of the following
1.In order to stabilize the WDS environment, configure an AP as a WDS on each subnet.If there are more than 30 access points on a subnet make WDS doesnt have any client associated.
3.Remove the wlccp ap wds ip address if it is configured
The wlccp ap wds ip address command specifies a Wireless LAN Services Module (WLSM) as the WDS instead of another AP.The WLSM uses the Generic Routing Encapsulation (GRE) tunnels created between the switch and the AP in order to send the WLCCP messages. So this can support Access Points on different subnets.
If the APs are registered against the WDS and are already set and work properly, register the Wireless LAN Solution Engine (WLSE) against the WDS.
Set the WLCCP credentials, the username and password on the Remote Authentication Dial-In User Service (RADIUS) server, on the WLSE in order to register it with the WDS. In order to do this, complete these steps: