R710 unleashed group. Do not connect new AP.

  • 1
  • Question
  • Updated 3 weeks ago
  • Answered
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.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes

Posted 4 weeks ago

  • 1
Photo of Michael Brado

Michael Brado, Official Rep

  • 2570 Posts
  • 351 Reply Likes
I have not seen those logs, I suggest to contact our tech support for further troubleshooting.
https://support.ruckuswireless.com/contact-us
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
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.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2570 Posts
  • 351 Reply Likes
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.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
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.


(Edited)
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
Can you send the result via the below CLI commands in the new AP?
1. get election
2. get version
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
rkscli: get election

The local AP's ip address is 192.168.3.56, Election role is member, Fix role is NO, Debug level is DEBUG, Prefer master is 00:00:00:00:00:00

mac_address ipaddress role configID station_rate free_memory mesh_enabled mesh_node mesh_node_type model version bak_version systime board_type uptime last_seen
------------------------------------------------------------------------------------------------------------------------------------------------
44:1e:98:39:80:00 192.168.3.56 member 1 67 313064 1 0 1 R710 200.6.10.1.312 104.0.0.0.1347 0 r710-5-30-4bss 17 hrs 11 mins 16 secs Fri Oct 19 05:58:48 2018
44:1e:98:3b:5e:40 192.168.3.55 member 482 63 292232 1 0 1 R710 200.6.10.1.312 200.5.10.0.235 0 r710-5-30-4bss 17 hrs 21 mins 21 secs Fri Oct 19 05:58:47 2018
24:79:2a:33:e0:10 192.168.3.51 member 482 66 293324 1 0 1 R710 200.6.10.1.312 110.0.0.0.663 0 r710-5-30-4bss 17 hrs 13 mins 11 secs Fri Oct 19 05:58:47 2018
44:1e:98:39:8a:50 192.168.3.62 member 1 67 316756 1 0 1 R710 200.6.10.1.312 104.0.0.0.1347 0 r710-5-30-4bss 1 day 21 hrs 20 mins 22 secs Fri Oct 19 05:58:47 2018
44:1e:98:3b:59:c0 192.168.3.66 member 482 64 291516 1 0 1 R710 200.6.10.1.312 200.5.10.0.235 0 r710-5-30-4bss 17 hrs 21 mins 18 secs Fri Oct 19 05:58:48 2018
44:1e:98:3b:43:c0 192.168.3.60 master 482 63 272396 1 0 1 R710 200.6.10.1.312 200.5.10.0.291 62375 r710-5-30-4bss 17 hrs 21 mins 18 secs Fri Oct 19 05:58:49 2018
34:fa:9f:1c:1e:70 192.168.3.61 member 1 67 309088 1 0 1 R710 200.6.10.1.312 104.0.0.0.1347 0 r710-5-30-4bss 14 hrs 8 mins 32 secs Fri Oct 19 05:58:47 2018
OK
rkscli: get version
Ruckus R710 Multimedia Hotzone Wireless AP
Version: 200.6.10.1.312
OK

Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
It looks this AP is working fine and can see all of neighbor APs.
And please double check Unleashed webUI- Access Points Tab if the new AP is in the next page.
.



Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Alas, but other pages does not exist.

(Edited)
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
And I see AP list has 7 APs here,and the other of 3 APs as below can not join Unleashed and the previous build is 104.0.0.1347 which is not unleashed version. Can you try "set factory" in CLI and try again.
 
44:1e:98:39:80:00 192.168.3.56 member 1 67 313064 1 0 1 R710 200.6.10.1.312 104.0.0.0.1347
34:fa:9f:1c:1e:70 192.168.3.61 member 1 67 309088 1 0 1 R710 200.6.10.1.312 104.0.0.0.1347
44:1e:98:39:8a:50 192.168.3.62 member 1 67 316756 1 0 1 R710 200.6.10.1.312 104.0.0.0.1347

Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Can you try "set factory" in CLI and try again.
------------------------
Only the administrator's name and password has changed.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
You've definitely selected three unattached devices. But there is one more device attached:

24:79:2a:33:e0:10 192.168.3.51 member 482 66 293324 1 0 1 R710 200.6.10.1.312 110.0.0.0.663

It differs in the previous version of the firmware. Is it possible for non-aligned devices to return to version 104.x, update it to 110.x, and only then update to 200.x?
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
You've definitely selected three unattached devices. But there is one more device attached:

24:79:2a:33:e0:10 192.168.3.51 member 482 66 293324 1 0 1 R710 200.6.10.1.312 110.0.0.0.663

It differs in the previous version of the firmware. Is it possible for non-aligned devices to return to version 104.x, update it to 110.x, and only then update to 200.x?

----------------------------
Better not. Now:

44:1e:98:39:80:00 192.168.3.56 member 1 67 313520 1 0 1 R710 200.6.10.1.312 110.0.0.0.663

There is no connection with the master. Errors are repeated.
Need help specialist in firmware.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Please tell me which command switches the boot image from Image1 to Image2?
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
You don't need to switch the image. I see you pasted the current version(200.6.10.1.312) is correct. so you just do a factory reset and reboot it to try.


Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
These are error messages that are sent to the external syslog server. Access points that are connected to the group, such messages are not issued.
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
1. If you factory reset AP and AP can not join Unleashed network, how it can know the external syslog server setting and send these messages out?
2. "fw show all" command shows one backup image is 110.x which is not same as the previous 104.x, why? Did you check the same AP?
 
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
BTW: AP with either build 104.x or 110.x can not join Unleashed network. So please ensure AP is working on 200.x Unleashed firmware.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
1. "how it can know the external syslog server setting and send these messages out?"
- Connect via SSH and enter parameters in the command

set syslog : set syslog {options}
                 -> {enable|disable}
                 -> ip <ipv4/ipv6 address>
                 -> port <service-port>
                 -> protocol  {tcp|udp}
                 -> level {local|network} level {0|1|..|6|7}
                 -----------------------------------------------
                 ** 0(emergency), 1(alert), 2(critical) 3(error)
                 ** 4(warning), 5(notice), 6(info), 7(debug)
                 -- Modify Syslog Settings

2. "Did you check the same AP?"
-  I managed to load the 110.x version, and go back to 200.x. Please note that the MAC and IP points have not changed.

44:1e:98:39:80:00 192.168.3.56 member 1 67 313520 1 0 1 R710 200.6.10.1.312 110.0.0.0.663


Photo of Michael Brado

Michael Brado, Official Rep

  • 2570 Posts
  • 351 Reply Likes
Hi Everybody,

   Lots of community activity overnight, great.  What you NEED is UNLEASHED firmware, if you want
your R710 to be recognized and join the Unleashed network.  That's the 200.6 code, not 104.x or 110.x
which are Solo AP/Standalone AP code, which will join a ZoneDirector or SmartZone controller, or run
in Standalone mode, IGNORING the Unleashed network on the same VLAN...

   Here is the code you need: 

https://support.ruckuswireless.com/software/1809-ruckus-unleashed-ap-200-6-10-1-312-ga-refresh2-soft...

   I hope you are soon running all your APs in Unleashed!  With best regards.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Dear Mr. Brado.

Apparently there was too much activity and you didn’t read the text.
Therefore, a brief summary: There are seven devices Ruckus R710 purchased at different times. ONE VERSION OF FIRMWARE - R710_200.6.10.1.312 is installed on all devices (exactly the version that you recommended). Four devices united in a group, and three others cannot join due to an error. An example of error messages is in the first message.

Photo of Michael Brado

Michael Brado, Official Rep

  • 2570 Posts
  • 351 Reply Likes
Yes, round and round... sorry.  Next suggestion, try replacing a working AP with a problem one on the same switch port?The power cycle alone is enough, don't need to FD again, thanks.  
(Edited)
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
This idea has already been tested. I swapped a non-accepting device and a device that works stably in a group. The behavior of the devices has not changed.

I want to still ask to focus on the only factual error. All unconnected devices repeat connection attempts every 5 seconds with the same error.

(Here is a sequence of messages from bottom to top)
 Oct 20 07:29:35 wsgclient[509]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap  
Oct 20 07:29:35 wsgclient[509]: communicatorInit:331 Init connection failed, ret:125, connectRetry:8162 
Oct 20 07:29:35 wsgclient[509]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed 
Oct 20 07:29:35 wsgclient[509]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known

I am very interested in the highlighted message here. Connection failure on port 443. Could there be a problem with SSL certificates or encryption methods?

Although other lines are no less interesting. In the first line: "getaddrinfo failed, ret: -2 / Name or service not known". That is, some service in the device simply did not start?

(Edited)
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Information for detailed analysis - below the whole process of restarting the device at the debug level.

Daemon    Error     Oct 20 08:50:34 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:34 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:13
Daemon    Error     Oct 20 08:50:34 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:34 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Error     Oct 20 08:50:28 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:28 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:12
Daemon    Error     Oct 20 08:50:28 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:28 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Error     Oct 20 08:50:23 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:23 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:11
Daemon    Error     Oct 20 08:50:23 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:23 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
User    Notice     Oct 20 08:50:22 hub_registrar: query result - ''
Daemon    Info     Oct 20 08:50:21 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar @ ap-registrar.ruckuswireless.com
Daemon    Notice     Oct 20 08:50:20 meshd[449]: Scan returned 0 entries.
Daemon    Error     Oct 20 08:50:18 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:18 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:10
Daemon    Error     Oct 20 08:50:18 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:18 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Error     Oct 20 08:50:13 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:13 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:9
Daemon    Error     Oct 20 08:50:13 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:13 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Notice     Oct 20 08:50:12 meshd[449]: core_sm_common_post: restoring to fixed channel ...
Daemon    Notice     Oct 20 08:50:12 meshd[449]: Advertise IF_code=- depth=1 downlinks=0 reason=
Kernel    Info     Oct 20 08:50:12 kernel: [  123.071767] br0: port 20(wlan63) entered disabled state (meshd,449)
Kernel    Warning     Oct 20 08:50:12 kernel: [  123.071467] [2018/10/20 8:50:12]  wmi_unified_vdev_down_send for vap 15
Kernel    Warning     Oct 20 08:50:12 kernel: [  123.054430] [2018/10/20 8:50:12]  wmi_unified_vdev_stop_send for vap 15
Daemon    Notice     Oct 20 08:50:12 meshd[449]: lspd: 0>955
Daemon    Notice     Oct 20 08:50:12 meshd[449]: stat: I -> R [0: GW_DETECTED] (elapsed: 44s)
Daemon    Notice     Oct 20 08:50:12 meshd[449]: stat: I>R
Daemon    Notice     Oct 20 08:50:12 meshd[449]: dump: I:136:l w:(0 0) uplk (nil -1 -1) pulk (nil -1 -1) wulk nil) ...
Daemon    Notice     Oct 20 08:50:12 meshd[449]: drct: unkwn>direct
Local2    Error     Oct 20 08:50:12 syslog:  AP get the broadcast ip in its subnet, the broadcast ip is 192.168.3.255
Daemon    Error     Oct 20 08:50:08 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:08 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:8
Daemon    Error     Oct 20 08:50:08 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:08 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Notice     Oct 20 08:50:07 meshd[449]: uplink(wired=0)=null(0.0) best_wired=null(0.0) proposed=null( ,0.0,0.0)
Daemon    Notice     Oct 20 08:50:07 meshd[449]: Scan returned 0 entries.
User    Notice     Oct 20 08:50:05 hub_registrar: query result - ''
Daemon    Info     Oct 20 08:50:05 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar @ ap-registrar.ruckuswireless.com
Daemon    Error     Oct 20 08:50:03 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:50:03 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:7
Daemon    Error     Oct 20 08:50:03 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:50:03 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Info     Oct 20 08:50:00 hub_registrar: OCSP: APR lookup timer expired
Daemon    Error     Oct 20 08:49:57 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:49:57 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:6
Daemon    Error     Oct 20 08:49:57 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:49:57 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Error     Oct 20 08:49:52 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:49:52 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:5
Daemon    Error     Oct 20 08:49:52 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:49:52 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Notice     Oct 20 08:49:49 meshd[449]: uplink(wired=0)=null(0.0) best_wired=null(0.0) proposed=null( ,0.0,0.0)
Daemon    Notice     Oct 20 08:49:49 meshd[449]: Scan returned 0 entries.
User    Notice     Oct 20 08:49:49 hub_registrar: query result - ''
Daemon    Info     Oct 20 08:49:47 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar @ ap-registrar.ruckuswireless.com
Daemon    Error     Oct 20 08:49:47 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:49:47 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:4
Daemon    Error     Oct 20 08:49:47 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:49:47 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Local2    Error     Oct 20 08:49:47 syslog: /home/jenkins/workspace/Unleashed-200.6.10.1_R710/buildroot/../controller/common/lwapp/lwapp_wtp_cfg.c:5522  uplink_enabled=0 downlink_enabled=0 second_downlink_enabled=0 exclusive_radio=0
Local2    Error     Oct 20 08:49:47 syslog: /home/jenkins/workspace/Unleashed-200.6.10.1_R710/buildroot/../controller/common/lwapp/lwapp_wtp_cfg.c:5522  uplink_enabled=0 downlink_enabled=0 second_downlink_enabled=0 exclusive_radio=0
Local2    Error     Oct 20 08:49:47 syslog: Parameter value L2 is invalid for parameter Tunnel-Mode
Daemon    Notice     Oct 20 08:49:45 meshd[449]: uplink(wired=0)=null(0.0) best_wired=null(0.0) proposed=null( ,0.0,0.0)
Daemon    Notice     Oct 20 08:49:45 meshd[449]: Scan returned 0 entries.
Daemon    Error     Oct 20 08:49:42 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Oct 20 08:49:42 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:3
Daemon    Error     Oct 20 08:49:42 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Oct 20 08:49:42 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Cron    Notice     Oct 20 08:49:42 ntpclient[1148]: Skew 7436894845.3mS, freq adjust 0
Cron    Notice     Oct 20 08:49:42 ntpclient[1148]: Time set from remote server
Cron    Notice     Jul 26 07:01:27 ntpclient[1148]: Using server: ntp.ruckuswireless.com
Daemon    Notice     Jul 26 07:01:22 meshd[449]: uplink(wired=0)=null(0.0) best_wired=null(0.0) proposed=null( ,0.0,0.0)
Daemon    Notice     Jul 26 07:01:22 meshd[449]: Scan returned 0 entries.
Daemon    Error     Jul 26 07:01:22 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Jul 26 07:01:22 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:2
Daemon    Error     Jul 26 07:01:22 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Jul 26 07:01:22 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Warning     Jul 26 07:01:21 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:21 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Warning     Jul 26 07:01:20 Eved: Last Reboot Reason: user reboot
Daemon    Warning     Jul 26 07:01:20 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:20 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Warning     Jul 26 07:01:19 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:19 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Warning     Jul 26 07:01:18 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:18 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Info     Jul 26 07:01:17 hub_registrar: OCSP: 'unknown' on ap-registrar.ruckuswireless.com - withhold query
Daemon    Notice     Jul 26 07:01:17 meshd[449]: gwdt: 0>1
Daemon    Notice     Jul 26 07:01:17 meshd[449]: drct: none>unkwn
Daemon    Warning     Jul 26 07:01:17 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:17 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Error     Jul 26 07:01:17 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Jul 26 07:01:17 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:1
Daemon    Error     Jul 26 07:01:17 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Jul 26 07:01:17 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Notice     Jul 26 07:01:14 meshd[449]: neighbor_updateAll: Mesh lost all proposed uplinks at uptime=80.
Daemon    Notice     Jul 26 07:01:14 meshd[449]: uplink(wired=0)=null(0.0) best_wired=null(0.0) proposed=null( ,0.0,0.0)
Daemon    Warning     Jul 26 07:01:14 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:14 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Warning     Jul 26 07:01:14 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:14 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Warning     Jul 26 07:01:14 wpa_supplicant: wlan63: Failed to initiate AP scan
Daemon    Error     Jul 26 07:01:14 wpa_supplicant: wlan63: Reject scan trigger since one is already pending
Daemon    Notice     Jul 26 07:01:14 meshd[449]: Advertise IF_code=s depth=1 downlinks=0 reason=
Daemon    Notice     Jul 26 07:01:12 meshd[449]: lspd: 955>0
Daemon    Notice     Jul 26 07:01:12 meshd[449]: stat: R -> I [1: GW_LOST] (elapsed: 15s)
Daemon    Notice     Jul 26 07:01:12 meshd[449]: stat: R>I
Daemon    Notice     Jul 26 07:01:12 meshd[449]: drct: init>none
Daemon    Info     Jul 26 07:01:12 channel-wifi1: No controller or backup mechanism
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Pausing 1 minute (target VAP wait related) for 44:1e:98:39:80:0c
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Pausing 10 minutes (DFS related)
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found 24 valid channels
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 165 : 5825 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 161 : 5805 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 157 : 5785 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 153 : 5765 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 149 : 5745 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 140 : 5700 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 136 : 5680 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 132 : 5660 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 128 : 5640 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 124 : 5620 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 120 : 5600 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 116 : 5580 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 112 : 5560 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 108 : 5540 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 104 : 5520 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel 100 : 5500 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi0: unable to find active wlan device for wifi0
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  64 : 5320 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi0: init: (44:1e:98:39:80:08) interval=15
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  60 : 5300 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  56 : 5280 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  52 : 5260 DFS
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  48 : 5240 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  44 : 5220 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  40 : 5200 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: Found channel  36 : 5180 
Daemon    Info     Jul 26 07:01:12 channel-wifi1: init: (44:1e:98:39:80:0c) interval=15
Daemon    Error     Jul 26 07:01:12 wsgclient[464]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
Daemon    Error     Jul 26 07:01:12 wsgclient[464]: communicatorInit:331 Init connection failed, ret:125, connectRetry:0
Daemon    Error     Jul 26 07:01:12 wsgclient[464]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
Daemon    Error     Jul 26 07:01:12 wsgclient[464]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known
Daemon    Notice     Jul 26 07:01:11 meshd[449]: drct: wait>init
Daemon    Info     Jul 26 07:01:08 init: starting pid 982, tty '': '/bin/tsyslogd.sh'
Daemon    Info     Jul 26 07:01:08 init: starting pid 980, tty '/dev/ttyMSM0': '/tmp/var/run/-login'
Daemon    Error     Oct 20 08:47:55 watchdog[64]: watchdog_task(309): watchdog-0 exiting ...
Daemon    Info     Oct 20 08:47:55 init: The system is going down NOW!
Daemon    Info     Oct 20 08:47:55 init: starting pid 13478, tty '': '/etc/init.d/rcStop'
User    Notice     Oct 20 08:47:54 hub_registrar: query result - ''
Daemon    Info     Oct 20 08:47:53 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar @ ap-registrar.ruckuswireless.com
Daemon    Notice     Oct 20 08:47:49 meshd[494]: Scan returned 0 entries.
User    Notice     Oct 20 08:47:36 syslog: CLI, user requests reboot via CLI command
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
A repeated group of error messages was removed by disabling the SCG service.
Questions:
1. Does the device need SCG service for correct operation in a decoupled group? Service is disabled on running devices.
2. If not needed, how could this installation be saved after updating the firmware and numerous resets to factory settings?
3. What services are necessary and sufficient to run to work properly in the untied group?
4. How to guarantee full reset of all parameters to factory settings for firmware version 200.x?
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Another observation: for all joined devices, the serial number starts at 1, and for non-joined devices, the serial numbers start at 9 or 4. Can this have an impact?
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
You needn't care about wsgclient messages. As I said, they are no useful in Unleashed product line.


Why is there GW lost message? Did you check the SW port or cable connection is stable?

Daemon    Notice     Jul 26 07:01:12 meshd[449]: stat: R -> I [1: GW_LOST] (elapsed: 15s)
Daemon    Notice     Jul 26 07:01:12 meshd[449]: stat: R>I

Can you put the non-joined APs into another subnet and set up a new Unleashed WIFI network successfully? This can ensure these APs are working fine in the new Unleashed. 

Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
How about "get wlanlist" and "get ipaddr wan" in AP cli at the new place?
Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
And if possible, you may send the debug info to me. We need to debug further for your case. Leave your email here, I will contact you later.
Instructions:
webUI-Admin & Services - Administer - Diagnostics- Debug Info
1. Select all of Debug Components, and "Apply"
2. Reconnect these non-joined APs in the network. Keep monitor about 30 minutes.
3. Click "Save Debug info" to download the file.
(Edited)
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
This is a non-group point with which I am doing experiments.

rkscli: get wlanlist
name          status   type   wlanID   radioID  bssid             ssid                           
--------------------------------------------------------------------------------------------------
wlan0         down     AP     wlan0    0        00:00:00:00:00:00 Wireless1                      
wlan1         down     AP     wlan1    0        00:00:00:00:00:00 Wireless2                      
wlan2         down     AP     wlan2    0        00:00:00:00:00:00 Wireless3                      
wlan3         down     AP     wlan3    0        00:00:00:00:00:00 Wireless4                      
wlan4         down     AP     wlan4    0        00:00:00:00:00:00 Wireless5                      
wlan5         down     AP     wlan5    0        00:00:00:00:00:00 Wireless6                      
wlan6         down     AP     wlan6    0        00:00:00:00:00:00 Wireless7                      
wlan7         down     AP     wlan7    0        00:00:00:00:00:00 Wireless8                      
recovery-ssid down     AP     wlan102  0        00:00:00:00:00:00 Configure.Me-398000            
wlan8         down     AP     wlan8    1        00:00:00:00:00:00 Wireless9                      
wlan9         down     AP     wlan9    1        00:00:00:00:00:00 Wireless10                     
wlan10        down     AP     wlan10   1        00:00:00:00:00:00 Wireless11                     
wlan11        down     AP     wlan11   1        00:00:00:00:00:00 Wireless12                     
wlan12        down     AP     wlan12   1        00:00:00:00:00:00 Wireless13                     
wlan13        down     AP     wlan13   1        00:00:00:00:00:00 Wireless14                     
wlan14        down     AP     wlan14   1        00:00:00:00:00:00 Wireless15                     
wlan15        down     AP     wlan15   1        00:00:00:00:00:00 Wireless16                     
meshd         up       AP     wlan62   1        00:00:00:00:00:00 Wireless63                     
meshu         down     STA    wlan63   1        00:00:00:00:00:00 RANDOM-                        
recovery-ssid down     AP     wlan103  1        00:00:00:00:00:00 Configure.Me-398000            
OK
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

Debug information collection started.
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Where to send a file with debug data?
How to translate it into text format?
-----------------
My temporary e-mail address: [email protected]
(Edited)
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Error found.
The following messages were found in the logs of the main access point:

Oct 22 16:33:59 stamgr: stamgr_handle_get_ap_sta():ERROR: no cfg AP 
Oct 22 16:33:59 stamgr: stamgr_match_countrycode():AP country code US`, ZD country code FR 
Oct 22 16:33:59 stamgr: stamgr_handle_get_ap_sta():in_req->env=60, contrycode=SU 
Oct 22 16:33:59 stamgr: stamgr_is_supported_ap_model():The AP r710 is supported
Oct 22 16:33:59 stamgr: stamgr_handle_get_ap_sta():main_cb->num_cfg_aps=4 max_cfg_ap=150 main_cb->sys_para.max_aps=25
Oct 22 16:33:59 stamgr: stamgr_ctrl_iface_receive():received msg from module 1, len = 204, id = 0x0200000a 


An attempt to change the country code at the access point through the command line interface was unsuccessful. The firmware does not know the code "FR". I had to change the code of the whole group to "US". After that, the remaining four access points successfully joined the group.

Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
Hi Mikhail,
Can you send the result of "get boarddata" in the previous non-joined AP CLI? I will check if these APs country code is fixed.  
Photo of Mikhail Starozhilov

Mikhail Starozhilov

  • 28 Posts
  • 3 Reply Likes
Hi Ken.

Yes, please:

kscli: get boarddata
name:     R710
magic:    35333131
cksum:    9aa
rev:      5.4
Serial#:  9918........
Customer ID: 4bss
Model:    R710
V54 Board Type: GD50
V54 Board Class: QCA_ARM
Random#:  3737 3436 3430 3462 3461 6630 3235 6561
symimgs:  yes
ethport:  2
V54 MAC Address Pool:  yes, size 16, base 44:1E:98:39:80:00
major:    2564
minor:    1
pciId:    0000
wlan0:    yes 44:1E:98:39:80:08
wlan1:    yes 44:1E:98:39:80:0C
eth0:     yes 44:1E:98:39:80:03
eth1:     yes 44:1E:98:39:80:04
eth2:      -  44:1E:98:39:80:05
eth3:      -  44:1E:98:39:80:06
eth4:      -  44:1E:98:39:80:07
eth5:      -  00:00:00:00:00:00
uart0:    yes
sysled:   no, gpio 0
sysled2:  no, gpio 0
sysled3:  no, gpio 0
sysled4:  no, gpio 0
Fixed Ctry Code:  yes
Antenna Info:  yes, value 0x00006D6C
usb installed:  yes
Local Bus:  disabled
factory:  yes, gpio 8
serclk:   internal
cpufreq:  calculated 0 Hz
sysfreq:  calculated 0 Hz
memcap:   disabled
watchdg:  enabled
OK


Photo of Ken Liu

Ken Liu, Employee

  • 18 Posts
  • 2 Reply Likes
Thanks! Get it. The root cause as you have found from the logs is the country code mismatched between Master AP with the new joining AP.
If these AP's country code is not fixed, AP can be setting to other Country code and join successfully.
But these non-join APs' boardata is "Fixed Ctry Code:  yes" and the default country code is US. AP can not be configured to other country code and rejected by Master AP due to countrycode mismatch. So you may need to check it with your reseller.