R710 unleashed group. Do not connect new AP.

[mikhail_starozh]

I have a working group of four R710.

But attempts to add new access points to the group are unsuccessful. New devices are updated to the latest firmware version, but are only visible in the section Admin & Service -> Administer -> Upgrade.

I can connect to new AP only via SSH, since via HTTP (S) I only see one page.


After outputting the debug information to the syslog server, I get a recurring group of messages for the new point:
 Oct 18 14:46:10 wsgclient[540]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap  
Oct 18 14:46:10 wsgclient[540]: communicatorInit:331 Init connection failed, ret:125, connectRetry:1395  
Oct 18 14:46:10 wsgclient[540]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed  
Oct 18 14:46:10 wsgclient[540]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known

I ask the club for help solving this riddle.

[michael_brado]

I have not seen those logs, I suggest to contact our tech support for further troubleshooting.
https://support.ruckuswireless.com/contact-us

[mikhail_starozh]

Today I have already applied to technical support. Now I need to contact the company that sold us the access points to register with Ruckus tech support as the owner of the AP. Once we have already asked to do this, but so far to no avail. So Ruckus tech support is a myth for us, despite 15 registered devices.

[michael_brado]

Ah, I understand more clearly, thanks. 

Your Reseller (who needs to register your products for support) is also typically your first resource for tech support too, so I hope you asked them to help troubleshoot.
But, that said, they likely won't have seen these logs with this AP not joining problem, and will need to get in touch with Ruckus TAC.
---
Meanwhile, let me suggest a couple things.  If you plug a PC/laptop into the Eth port you're connecting one of your new APs, does the PC get IP/DHCP/Def-GW information ok?Unleashed APs need to receive an IP address and Def-GW info to connect to the network.
If that works for your PC, try powering up one of the new APs (wait 2 min to be sure fully up), and press the indented Factory Default button for 8 seconds, to reset it again please.Plug it into the Eth port, and watch your Master AP's Access Points page, to see if the new AP shows up, or not...?
It's worth trying again, in the meantime, thanks.

[mikhail_starozh]

Open one of the non-aligned AP.

rkscli: get ipaddr wan
IP Address: (dynamic, vlan 1), IP: 192.168.3.56  Netmask 255.255.255.0  Gateway 192.168.3.1
OK

All parameters are as expected. Reset to factory settings was made repeatedly and to no avail.

rkscli: ping 192.168.3.60
PING 192.168.3.60 (192.168.3.60): 56 data bytes
64 bytes from 192.168.3.60: seq=0 ttl=64 time=0.697 ms
64 bytes from 192.168.3.60: seq=1 ttl=64 time=0.423 ms
64 bytes from 192.168.3.60: seq=2 ttl=64 time=0.562 ms
64 bytes from 192.168.3.60: seq=3 ttl=64 time=0.494 ms
64 bytes from 192.168.3.60: seq=4 ttl=64 time=0.750 ms

--- 192.168.3.60 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 0.423/0.585/0.750 ms
OK

The address 192.168.3.60 corresponds to the master device of a working group of AP Ruckus R710.