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.
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.
Posted 2 years ago
Michael Brado, Official Rep
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, Official Rep
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.
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.
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.
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)
Ken Liu, Employee
Can you send the result via the below CLI commands in the new AP?
1. get election
2. get version
1. get election
2. get version
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
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
Ken Liu, Employee
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.
.
And please double check Unleashed webUI- Access Points Tab if the new AP is in the next page.
.Alas, but other pages does not exist.
(Edited)
Ken Liu, Employee
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
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
Can you try "set factory" in CLI and try again.
------------------------
Only the administrator's name and password has changed.
------------------------
Only the administrator's name and password has changed.
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?
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?
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.
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.
Ken Liu, Employee
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.
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
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
Ken Liu, Employee
One more checking in CLI:
1. get director
2. fw show all
1. get director
2. fw show all
Ken Liu, Employee
You may ignore these wsgclient messages which are useless for Unleashed AP.
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 Info>
control file /writable/fw/main.cntl not in flash
-------------------------------------
current primary boot image is Image2
---------------<Image1 FW header>
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
---------------<Image2 FW header>
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
------ 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 Info>
control file /writable/fw/main.cntl not in flash
-------------------------------------
current primary boot image is Image2
---------------<Image1 FW header>
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
---------------<Image2 FW header>
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
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.
Ken Liu, Employee
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?
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?
Ken Liu, Employee
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.
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
- 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
Michael Brado, Official Rep
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.
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.
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.
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.
Michael Brado, Official Rep
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)
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?
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)
Ken Liu, Employee
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.
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.
Hello Ken.
Thank you for continuing to help me.
I wrote earlier that I swapped working and not working devices. Those devices that have worked before, continue to work successfully, devices that have not previously worked, do not start working at a new place.
GW error no longer repeats after disabling SCG service. Now the device log does not join the group as follows:
Thank you for continuing to help me.
I wrote earlier that I swapped working and not working devices. Those devices that have worked before, continue to work successfully, devices that have not previously worked, do not start working at a new place.
GW error no longer repeats after disabling SCG service. Now the device log does not join the group as follows:
Oct 22 08:09:09 kernel: [ 253.236207] ieee80211_ioctl_siwscan
Oct 22 08:09:09 meshd[435]: Err 14 Failed to start scan
Oct 22 08:09:06 hub_registrar: query result - ''
Oct 22 08:09:06 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:08:50 hub_registrar: query result - ''
Oct 22 08:08:49 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:08:38 kernel: [ 222.135344]
ieee80211_ioctl_siwscan
Oct 22 08:08:38 meshd[435]: Err 14 Failed to start scan
Oct 22 08:08:33 hub_registrar: query result - ''
Oct 22 08:08:32 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:08:17 hub_registrar: query result - ''
Oct 22 08:08:16 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:08:06 kernel: [ 191.037270]
ieee80211_ioctl_siwscan
Oct 22 08:08:06 meshd[435]: Err 14 Failed to start scan
Oct 22 08:08:00 hub_registrar: query result - ''
Oct 22 08:07:59 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:07:43 hub_registrar: query result - ''
Oct 22 08:07:42 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:07:35 kernel: [ 159.940205]
ieee80211_ioctl_siwscan
Oct 22 08:07:35 meshd[435]: Err 14 Failed to start scan
Oct 22 08:07:27 hub_registrar: query result - ''
Oct 22 08:07:26 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:07:10 hub_registrar: query result - ''
Oct 22 08:07:09 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:07:04 kernel: [ 128.844268]
ieee80211_ioctl_siwscan
Oct 22 08:07:04 meshd[435]: Err 14 Failed to start scan
Oct 22 08:06:53 hub_registrar: query result - ''
Oct 22 08:06:52 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:06:52 meshd[435]: drct: unkwn>direct
Oct 22 08:06:46 hub_registrar: OCSP: APR lookup timer expired
Oct 22 08:06:37 hub_registrar: query result - ''
Oct 22 08:06:36 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Oct 22 08:06:33 kernel: [ 97.748290]
ieee80211_ioctl_siwscan
Oct 22 08:06:33 meshd[435]: Err 14 Failed to start scan
Oct 22 08:06:28 ntpclient[1479]: Skew 7607099915.1mS, freq adjust 0
Oct 22 08:06:28 ntpclient[1479]: Time set from remote server
Jul 26 07:01:28 ntpclient[1479]: Using server: ntp.ruckuswireless.com
Jul 26 07:01:26 dropbear[1444]: chmod(/dev/ttyp0, 0620) failed: Read-only file
system
Jul 26 07:01:26 dropbear[1444]: chown(/dev/ttyp0, 0, 5) failed: Read-only file
system
Jul 26 07:01:26 dropbear[1444]: Deferring to RKS shell to authenticate
password.
Jul 26 07:01:25 dropbear[1444]: Child connection from 192.168.252.2:53429
Jul 26 07:01:22 Eved: Last Reboot Reason: user reboot
Jul 26 07:01:20 hub_registrar: query result - ''
Jul 26 07:01:19 hub_registrar: OCSP: 'Good' via ocsp-check - querying registrar
@ ap-registrar.ruckuswireless.com
Jul 26 07:01:17 hub_registrar: OCSP: started APR lookup timer
Jul 26 07:01:14 ntpclient[1347]: Using server: ntp.ruckuswireless.com
Jul 26 07:01:13 channel-wifi0: unable to find active wlan device for wifi0
Jul 26 07:01:13 channel-wifi0: init: (44:1e:98:39:80:08) interval=15
Jul 26 07:01:13 channel-wifi1: unable to find active wlan device for wifi1
Jul 26 07:01:13 channel-wifi1: init: (44:1e:98:39:80:0c) interval=15
Jul 26 07:01:12 meshd[435]: gwdt: 0>1
Jul 26 07:01:12 meshd[435]: drct: init>unkwn
Jul 26 07:01:12 meshd[435]: drct: wait>init
Oct 22 08:04:41 init: The system is going down NOW!
Oct 22 08:04:41 init: starting pid 23905, tty '': '/etc/init.d/rcStop'
Oct 22 08:04:22 rsmd[62]: Receive reboot msg [u,1]
Oct 22 08:04:22 syslog: CLI, user requests reboot via CLI command
Oct 22 08:04:18 meshd[435]: Scan returned 0 entries.
Oct 22 08:04:16 dropbear[23536]: chmod(/dev/ttyp0, 0620) failed: Read-only file
system
Oct 22 08:04:16 dropbear[23536]: chown(/dev/ttyp0, 0, 5) failed: Read-only file
system
Oct 22 08:04:16 dropbear[23536]: Deferring to RKS shell to authenticate
password.
Oct 22 08:04:15 dropbear[23536]: Child connection from 192.168.252.2:53160
Ken Liu, Employee
How can you disable SCG service? I can not understand here.
set scg disable
Ken,
Please re-read my posts.
https://forums.ruckuswireless.com/ruckuswireless/topics/r710-unleashed-group-do-not-connect-new-ap?t...
Please re-read my posts.
https://forums.ruckuswireless.com/ruckuswireless/topics/r710-unleashed-group-do-not-connect-new-ap?t...
Ken Liu, Employee
How about "get wlanlist" and "get ipaddr wan" in AP cli at the new place?
Ken Liu, Employee
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.
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)
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.
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.
Where to send a file with debug data?
How to translate it into text format?
-----------------
My temporary e-mail address: [email protected]
How to translate it into text format?
-----------------
My temporary e-mail address: [email protected]
(Edited)
Ken Liu, Employee
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.
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.
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
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
Ken Liu, Employee
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.
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.
