Technical Tip: Clients shown offline in Ruckus Wireless controller x6.0

This article describes the behavior where clients are shown offline in the Ruckus Wireless controller running v6.0 after the L2 poll.

This can occur if the appliance has previously detected Access Points (APs) under a different Ruckus controller.

Diagnose

1) Enable debug attributes on the controller. Login to appliance CLI as root and type:

device -ip <Ruckus controller IP> -setAttr -name DEBUG -value 'TelnetServer ForwardingInterface'.

2) L2 poll controller.

3) Review output.master for the following content:

**************** <Ruckus Controller> *******************
<...>
IP = 10.236.5.100
<...>
DBID = 818 <--- Controller's Database ID
<...>

yams INFO :: 2022-04-26 16:31:04:085 :: 94 :: PollThread-trap5 :: RuckusSZ.readStaWireless : 10.236.5.100 : Reading clients for AP[2], apMac : 8C:FE:74:26:DE:60
yams INFO :: 2022-04-26 16:31:04:085 :: 94 :: PollThread-trap5 :: RuckusSZ.readStaWireless : 10.236.5.100 : authDevId = 764
yams INFO :: 2022-04-26 16:31:04:085 :: 94 :: PollThread-trap5 :: RuckusSZ.readStaWireless : 10.236.5.100 : not reading AP 797 since it is managed by different controller 764 <----

AP with apMac: 8C:FE:74:26:DE:60 was originally discovered/managed by a different controller with dbid 764. 

The appliance was expecting the authDevId (aka AuthenticatorDevId) to be the controller's dbid (818). The debug message "not reading AP 797" is generated and the clients connected to this AP are marked offline for this controller.