After reboot AP List on Smartzones Empty

[AdminHWE]

Dear Community,

we did shut down both controller because of moving them to another rack.

First we did shut down the "follower" and everything was fine, after moving the follower and start it again, everything was managed again no errors.

After we did shut down the leader in the cluster there came error "search failed" and it worked normally again after the leader was back. So the redundancy didnt work like expected. As Addon we got this wonderful feature, that the AP list is complete empty.

Anybody knows how to get the AP list back? in the logs you can see that ruckus smartzone is logging about all the APs, but they are not listed unter Access Points, the Zones and categories are still there, but no AP device is listed.

Thanks in advance!

[Vineet_nejwala · Accepted solution]

Hi @AdminHWE 

Kindly login to couple of APs and execute below command and share the output.

get scg

The idea here is to confirm if APs have lost the IP of controller/disconnected state or is it an DB corruption that need ES reindex.

Best Regards

Vineet

[AdminHWE]

Hi @Vineet_nejwala ,

thanks for the fast reply, yea I found this "get scg" in some documentation here, the problem is, we managed a lot through controller like get new factory -> rollout with profile.

we are searching for the ap password, default isnt working.

ssh is asking "login as" and then additional "please login" is this both super?

br

[Vineet_nejwala]

Hi @AdminHWE 

Yes, the AP ssh login requires twice username prompt (you can skip first), the username and password is set inside the zone to which AP belong, you can click on the zone >> edit and override the password (if APs still connected to this controller this password would get updated).

Best Regards

Vineet

[AdminHWE]

Hi @Vineet_nejwala ,

we weren't able to change the password through zone edit the APs didnt update the password, but to reindex the elastic search worked like charm.

many thanks for the fast support!

as addition: 

do you have an idea, why the shutdown of the "master" completly broken the cluster? the follower only said "search failed"?