cancel
Showing results for 
Search instead for 
Did you mean: 

R710 cannot migrate from ZD3050 to sVZ 6.1.1

gsfakian
New Contributor III

Hi to all, the title describes my problem... i have managed to migrate 21 r710 but one insists not to migrate... It starts to accept the firmware from the sVZ but fails... I manually flash the stand alone firmware and after that the ZD starts auto adoption and readopts it by flashing back the ZoneDirector firmware 10.1.1.0.42. Access point seems to work fine... any proposals?

 

thanks in advance!

1 ACCEPTED SOLUTION

I had already opened a case.. and finally problem solved. Ruckus support rocks!.. The problem was that the certificate file was completely missing from the AP and it was not possible to upload it from GUI. It was showing that the procedure was done but nothing happened in the end. So the solution was to "feed" manualy firmware 6.1.1.0.1274 which probably contains certificate and after that controller adopted it!.. 

View solution in original post

14 REPLIES 14

Sorry for that probably trying to send latest long post is too long and cut by the system(?)

I was trying to write that Licenses are 21/76, ZD was isolated after flashing the R710, version is confirmed 114.0.0.0.65565. sVZ and AP are on the same VLAN , L2 network can ping each other. Set scg ip was given many times and confirmed by get scg, cert check was disabled from sVZ... nothing has changed!... Also tried to request new certificate from Ruckus but seems i cannot upload it... I received the res file trying to upload from GUI shows success and that it will reboot automatically but nothing happens...

Hi @gsfakian 

Most of the basic steps are already checked. I believe it is best to open the Support case so that we can check the logs and see what is going on.

I had already opened a case.. and finally problem solved. Ruckus support rocks!.. The problem was that the certificate file was completely missing from the AP and it was not possible to upload it from GUI. It was showing that the procedure was done but nothing happened in the end. So the solution was to "feed" manualy firmware 6.1.1.0.1274 which probably contains certificate and after that controller adopted it!.. 

Hi @gsfakian 
We are glad to hear that the issue is resolved and than you for your feedback.
Please feel free to contact us for any assistance or queries.

gsfakian
New Contributor III

Also last log entries if help... i see some ssl errors?

P daemon.info cubic[669]: cub_state_action:2319 [CONN_GET_ADDR_STATE] -> [DISC_REQ_STATE]; reason: [CUB_RESULT_CONN_GET_ADDR_SUCCESS].
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: json_cmd_proc:558 Data type : [1][GENERATE_DISCOVER].
Mar 13 18:32:27 RuckusAP daemon.debug cubic[669]: apcfg_general_get_radio_info:153 background scan wifi0: en:0, timer:20, channel num:11.
Mar 13 18:32:27 RuckusAP daemon.debug cubic[669]: apcfg_general_get_radio_info:153 background scan wifi1: en:0, timer:20, channel num:24.
Mar 13 18:32:27 RuckusAP daemon.warn cubic[669]: apcfg_general_get_base_info:513 ret:[6]/[bad key: device-gps-coordinates] No GPS data
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: apcfg_general_get_sz_list:319 Server list[10.50.49.3] from SZ..
Mar 13 18:32:27 RuckusAP daemon.warn cubic[669]: apcfg_general_get_base_info:565 ret:[34]/[file missing for RSM services] No server cert validation setting.
Mar 13 18:32:27 RuckusAP daemon.err cubic[669]: apcfg_general_get_wan_ipv6:1119 Get IP error. stop rsm config get/set, please check the config key and value
Mar 13 18:32:27 RuckusAP daemon.debug cubic[669]: curl_https_request:1323 curl_https_request, msg_type:[0][MSG_TYPE_DISC], via ssh:[no], send_data:[{   "protocolVersion":      "0.50",     "mac":   "58:B6:33:3D:67:D0",    "serial":       "341503410070",         "deviceName":   "RuckusAP",     "model":        "R710",         "timeStamp":    1678732347,     "fwVersion":    "114.0.0.0.6565",    "gpsInfo":      "",     "deviceIpMode": 3,      "ip":   "10.50.49.229",         "ipv6": "fc00::1",      "countryCode":  "US",   "provisionTag": "",     "location":     "", "devSupportUsb": "1",    "meshRole":     0,      "radio":        [[{                             "channel":      "1,2,3,4,5,6,7,8,9,10,11"                       }], [{                      "channel":       "36,40,44,48,52,56,60,64,100,104,108,112,116,120,124,128,132,136,140,149,153,157,161,165"                       }]] }].
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: util_cmd_proc:1574 Execute CMD type: [5][GET_DOMAIN_SUFFIX_INFO].
Mar 13 18:32:27 RuckusAP daemon.debug cubic[669]: wrap_getaddrinfo:1181 getaddrinfo with address [10.50.49.3] returns success.
Mar 13 18:32:27 RuckusAP daemon.debug cubic[669]: resolve_addrinfo:1222 wrap_getaddrinfo with addr [10.50.49.3] returns success.
Mar 13 18:32:27 RuckusAP daemon.debug cubic[669]: do_curl:968 No SZ public key from APR, skip verification..
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: do_curl:1069 Send HTTP request to URL:[https://10.50.49.3:443/wsg/ap/discovery/58:B6:33:3D:67:D0].
Mar 13 18:32:27 RuckusAP daemon.err cubic[669]: ssl_ctx_func_cb:790 SSL cert/key file init error.(file doesn't exist).
Mar 13 18:32:27 RuckusAP daemon.err cubic[669]: do_curl:1131 curl_easy_perform failed:[66][Failed to initialise SSL crypto engine].
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: cub_disc_req_state_action:714 DISC request http return code:[0]..
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: cub_state_action:2315 Start [CONN_GET_ADDR_STATE].
Mar 13 18:32:27 RuckusAP daemon.info cubic[669]: cub_state_action:2319 [DISC_REQ_STATE] -> [CONN_GET_ADDR_STATE]; reason: [CUB_RESULT_DISC_REQ_FAIL].