cancel
Showing results for 
Search instead for 
Did you mean: 

R710 unleashed group. Do not connect new AP.

mikhail_starozh
New Contributor III
I have a working group of four R710.
Image_ images_messages_5f91c3f1135b77e2478f3f39_cf98c56b2d3da341973caf0481631984_RackMultipart20181018681301r0k-70b1ccb6-addd-48af-b03d-63ce7d56a101-270817841.png1539872891
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.
Image_ images_messages_5f91c3f1135b77e2478f3f39_a948c7a12ca7f378cef28e61dbcefb37_RackMultipart201810181276801gh-09d955ef-6592-4411-bbbc-b1a99c506c54-1376000081.png1539873403
I can connect to new AP only via SSH, since via HTTP (S) I only see one page.
Image_ images_messages_5f91c3f1135b77e2478f3f39_81d10ca9c6e5915942c413ca84e58cff_RackMultipart20181018116937nh9-0461dd6a-b47d-484a-a3bc-a12577059475-1749252419.png1539873874

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

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?
 

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


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.

mikhail_starozh
New Contributor III
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.