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

Can you try "set factory" in CLI and try again.
------------------------
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?

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.

mikhail_starozh
New Contributor III
Please tell me which command switches the boot image from Image1 to Image2?

ken_liu_hkzv8ty
New Contributor II
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.