topic Re: R710 unleashed group. Do not connect new AP. in Access Points - Indoor and Outdoor

R710 unleashed group. Do not connect new AP.

mikhail_starozh — Thu, 18 Oct 2018 14:59:14 GMT

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.

Re: R710 unleashed group. Do not connect new AP.

michael_brado — Thu, 18 Oct 2018 18:06:17 GMT

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

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Thu, 18 Oct 2018 20:15:12 GMT

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.

Re: R710 unleashed group. Do not connect new AP.

michael_brado — Thu, 18 Oct 2018 20:25:32 GMT

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.

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Thu, 18 Oct 2018 20:56:03 GMT

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.

Re: R710 unleashed group. Do not connect new AP.

ken_liu_hkzv8ty — Fri, 19 Oct 2018 02:41:16 GMT

Can you send the result via the below CLI commands in the new AP?
1. get election
2. get version

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 06:01:47 GMT

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

Re: R710 unleashed group. Do not connect new AP.

ken_liu_hkzv8ty — Fri, 19 Oct 2018 06:26:41 GMT

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.
.

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 06:43:28 GMT

Alas, but other pages does not exist.

Re: R710 unleashed group. Do not connect new AP.

ken_liu_hkzv8ty — Fri, 19 Oct 2018 06:46:58 GMT

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

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 06:49:32 GMT

Please tell me which command switches the boot image from Image1 to Image2?

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 06:58:08 GMT

Can you try "set factory" in CLI and try again.
------------------------
Only the administrator's name and password has changed.

Re: R710 unleashed group. Do not connect new AP.

ken_liu_hkzv8ty — Fri, 19 Oct 2018 06:58:21 GMT

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.

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 07:25:50 GMT

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 07:40:19 GMT

After executing "set factory" and "reboot", the device cycles through the error messages:

192.168.3.56 Oct 19 07:26:18 wsgclient[540]: registration:692 Failed to init socket! ret:125 url:https://RuckusController/wsg/ap
192.168.3.56 Oct 19 07:26:18 wsgclient[540]: communicatorInit:331 Init connection failed, ret:125, connectRetry:383
192.168.3.56 Oct 19 07:26:18 wsgclient[540]: cmrInit:141 Call 'crDefSocketInit()' failed, ip: port:443, ret:125/CR initial socket failed
192.168.3.56 Oct 19 07:26:18 wsgclient[540]: crResloveAddrInfo:152 getaddrinfo failed, ret:-2/Name or service not known

Re: R710 unleashed group. Do not connect new AP.

ken_liu_hkzv8ty — Fri, 19 Oct 2018 08:12:35 GMT

One more checking in CLI:
1. get director
2. fw show all

Re: R710 unleashed group. Do not connect new AP.

ken_liu_hkzv8ty — Fri, 19 Oct 2018 08:30:57 GMT

You may ignore these wsgclient messages which are useless for Unleashed AP.

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 08:41:34 GMT

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.

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 08:48:22 GMT

rkscli: get director
------ Unleashed Info ------
Device role          : ap
Primary Controller   : n/a
Secondary Controller : n/a
DHCP Opt43 Code      : 3
AP is in Stand-alone mode.
OK
rkscli: fw show all

control file /writable/fw/main.cntl not in flash
-------------------------------------
current primary boot image is Image2
---------------
Magic:        RCKS
next_image:   0x280000
invalid:      0
hdr_len:      160
compression: l7
load_address: 0x42000000
entry_point: 0x42008000
timestamp:    Wed May 2 11:28:02 2018
binl7_len:    12687196
hdr_version: 4
hdr_cksum:    0x057C
version:      110.0.0.0.663     ( 110.0.0.0.663 )
MD5:          D906240EC4282ACEF948186EC184AF0C
product:      r710      (0)
architecture: 0
chipset:      0
board_type:   0
board_class: 0
customer:
Image Sign Type: Intermediate Signed Image(ISI).
Tail start:   0xc18f60
---------------
Magic:        RCKS
next_image:   0x260000
invalid:      0
hdr_len:      160
compression: l7
load_address: 0x42000000
entry_point: 0x42008000
timestamp:    Thu Jul 26 07:18:39 2018
binl7_len:    25022300
hdr_version: 4
hdr_cksum:    0x5359
version:      200.6.10.1.312    ( 200.6.10.1.312 )
MD5:          AFE478CED659998FDECC583D6D47A42F
product:      r710      (0)
architecture: 0
chipset:      0
board_type:   0
board_class: 0
customer:
Image Sign Type: Intermediate Signed Image(ISI).
Tail start:   0x17dc760
OK

Re: R710 unleashed group. Do not connect new AP.

mikhail_starozh — Fri, 19 Oct 2018 08:51:47 GMT

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.