nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't associate R750 to SZ5.2 when R750 has static IP address.

unknown

HI.

I recently heard that from partner we can't joining R750 with SZ5.2 when R750 has static IP address.

Thus I tested that, and I got same result.

Below is syslog on R750.

<---------when R750 is configured static ip address -------------->
Mar 12 01:46:36 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:46:41 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:46:46 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:46:51 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255
Mar 12 01:46:51 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:46:56 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7]
Mar 12 01:47:16 RuckusAP daemon.err cubic[770]: apcfg_general_get_wan_ipv6:1119 Get IP error. stop rsm config get/set, please check the config key and value
Mar 12 01:47:17 RuckusAP daemon.err cubic[770]: update_ssh_public_key:781 Address [] is invalid address.[-258].
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hub_registrar ... [stopped] (0.016)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hub_registrar: ref count 0 mon_level 2
Mar 12 01:47:17 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: sshclient ....... [failed ] (0.014)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: sshclient ....... [failed ] (0.006)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hotspot ......... [stopped] (0.006)
Mar 12 01:47:17 RuckusAP daemon.notice rsmd[189]: hotspot ......... [started] (0.006)
Mar 12 01:47:22 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:47:47 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:47:52 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255
Mar 12 01:47:52 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:47:57 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:48:52 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:48:53 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255
Mar 12 01:48:58 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:49:48 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:49:52 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255
Mar 12 01:49:53 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:50:08 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:51:01 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255
Mar 12 01:51:03 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:51:08 RuckusAP daemon.err cubic[770]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 12 01:51:08 RuckusAP daemon.notice rsmd[189]: sshclient ....... [stopped] (0.027)

<---------when R750 is configured dynamic ip address -------------->

Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSHtunnel Public Key verify Successfully ServerIP=172.16.100.225
Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSH tunnel pararms: 172.16.100.225 128
Mar 12 01:51:12 RuckusAP daemon.notice rsmd[189]: sshclient ....... [started] (3.324)
Mar 12 01:51:12 RuckusAP daemon.notice rsmd[189]: lldpd ........... [stopped] (0.005)
Mar 12 01:51:12 RuckusAP daemon.notice rsmd[189]: lldpd ........... [started] (0.054)
Mar 12 01:51:13 RuckusAP daemon.notice Firmware Daemon[689]: working|looking up control server IP
Mar 12 01:51:13 RuckusAP daemon.notice Firmware Daemon[689]: working|reading control file
Mar 12 01:51:14 RuckusAP daemon.notice Firmware Daemon[689]: working|reading firmware file header
Mar 12 01:51:22 RuckusAP authpriv.info dropbear[6623]: Child connection from 192.168.100.51:53206
Mar 12 01:51:24 RuckusAP authpriv.notice dropbear[6623]: Deferring to RKS shell to authenticate password.
Mar 12 01:51:24 RuckusAP authpriv.err dropbear[6623]: chown(/dev/ttyp0, 0, 5) failed: Read-only file system

When R750 is configured static ip address, he don't update ssh public key by any reason.

Mar 12 01:47:16 RuckusAP daemon.err cubic[770]: apcfg_general_get_wan_ipv6:1119 Get IP error. stop rsm config get/set, please check the config key and value
Mar 12 01:47:17 RuckusAP daemon.err cubic[770]: update_ssh_public_key:781 Address [] is invalid address.[-258].

But When R750 is configured dynamic ip address, he did update ssh public key well.

Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSHtunnel Public Key verify Successfully ServerIP=172.16.100.225
Mar 12 01:51:11 RuckusAP daemon.info rsmd_func[6432]: SSH tunnel pararms: 172.16.100.225 128

Is there a bug report about this symptom?

Find more posts tagged with

Accepted answers

All comments

michael_brado

Hi Jeronimo, your text got flagged as possible spam, and I've released it and removed the other two duplicate posts.
I don't know your answer, but if you open a ticket with TAC, they can search for a match in our JIRA (bug) database.

unknown

Very stupid question.... when setting up the AP with a static IP, did you setup its default gateway? from the AP CLI, when configured with a static IP, can you do a ping to the SZ's IP?

unknown

That's too bad.
Do you think I don't check those?

unknown

Yes system blocked my article.

And I opened a case.

The case's id is 01040508.

unknown

Diego! You did very stupid comment. You really think Mr jeronimo did not check default gateway and etc. don't you?
I faced same issue also.

unknown

Sorry for the comment. Didn't mean it as a something obvious. . I had issues where the default gateway was configured but the route wasn't active in the ap. Is the IP range the same when using static or dhcp ? Smartzone uses an internal pool of ips to setup ssh tunneling between the ap and the controller. That range didn't use to be configurable and that range also couldn't be used on the APs themselves or on any other IP destination that smartzone would have to reach. On the latest versions the range is configurable. Any chance it might be using ips in the range 10.254.0.0/16 or 10.255.0.0/16?

More details here. https://forums.ruckuswireless.com/ruc...

Also, looking at the log, was the IP manually assigned ip 10.10.99.255? .. I imagine that there could be a code path on the ap checking that the IP doesn't end in 255 which would be valid as long as you're using masks in the /1-23 range. (meaning the check would be wrong).

Mar 12 01:46:51 RuckusAP local2.err syslog: AP get the broadcast ip in its subnet, the broadcast ip is 10.10.99.255

Or is it happening with any static IP?

I didn't notice your long post history jerónimo. Once again sorry of the first comment sounded wrong.

unknown

I have the same issue, R750 and vSZ 5.2.0, and already upgraded to the latest ap patch 5.2.0.0.5010

Enabling debug on R750 I got this and I notice that GET_DOMAIN_SUFIX_INFO resolves to 127.0.0.1, and the ap uses this adress as the "controller" address.

Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: util_cmd_proc:1574 Execute CMD type: [1][GET_BASE_INFO].
Mar 16 17:48:52 APR75003 daemon.warn cubic[1487]: apcfg_general_get_base_info:513 ret:[6]/[bad key: device-gps-coordinates] No GPS data
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: apcfg_general_get_sz_list:319 Server list[172.17.128.253,172.30.11.248,] from SZ..
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: apcfg_general_get_sz_list:398 Server list[172.17.128.253,172.30.11.248,,172.30.11.248] appended from lastJoin..
Mar 16 17:48:52 APR75003 daemon.warn cubic[1487]: apcfg_general_get_base_info:565 ret:[34]/[file missing for RSM services] No server cert validation setting.
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: apcfg_general_get_radio_info:153 background scan wifi0: en:0, timer:20, channel num:13.
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: apcfg_general_get_radio_info:153 background scan wifi1: en:0, timer:20, channel num:20.
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: cub_conn_get_addr_state_action:611 It's Registered.[1].
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: cub_conn_get_addr_state_action:615 Current server list:[172.17.128.253,172.30.11.248,,172.30.11.248]..
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: cub_state_action:2315 Start [IMG_REQ_STATE].
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: cub_state_action:2319 [CONN_GET_ADDR_STATE] -> [IMG_REQ_STATE]; reason: [CUB_RESULT_CONN_GET_ADDR_SUCCESS_REGISTERED].
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: json_cmd_proc:558 Data type : [3][GENERATE_IMGREQ].
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: curl_https_request:1332 curl_https_request, msg_type:[5][MSG_TYPE_IMGREQ], via ssh:[yes], send_data:[{ "protocolVersion": "0.50", "timeStamp": "20200316T174852", "seqNumber": 109, "zoneUUID": "499b2956-8d7a-4d73-8346-8c886b12dda5", "deviceIpMode": 3, "bkupFwVer": "112.1.0.0.2146", "configUUID": "b427e253-67ac-11ea-ab86-f627fe1aafae", "purpose": "FW_CONF" }].
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: util_cmd_proc:1574 Execute CMD type: [5][GET_DOMAIN_SUFFIX_INFO].
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: wrap_getaddrinfo:1187 getaddrinfo with address [127.0.0.1] returns success.
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: resolve_addrinfo:1236 wrap_getaddrinfo with addr [127.0.0.1] returns success.
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: do_curl:1069 Send HTTP request to URL:[http://127.0.0.1:8082/wsg/ap/config/4C:B1:CD:27:84:20/5.2.0.0.5010].
Mar 16 17:48:52 APR75003 daemon.err cubic[1487]: do_curl:1131 curl_easy_perform failed:[7][Couldn't connect to server].
Mar 16 17:48:52 APR75003 daemon.debug cubic[1487]: cub_sm_check_retry_timeout:183 Lost seconds:[236], connection timeout:[300], server num:[2].
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: cub_state_action:2315 Start [CONN_GET_ADDR_STATE].
Mar 16 17:48:52 APR75003 daemon.info cubic[1487]: cub_state_action:2319 [IMG_REQ_STATE] -> [CONN_GET_ADDR_STATE]; reason: [CUB_RESULT_IMG_REQ_CONNECTION_FAIL].
Mar 16 17:48:52 APR75003 daemon.err gapd: Fail to get pool stats
Mar 16 17:48:52 APR75003 daemon.info gapd: selecting.....
Mar 16 17:48:53 APR75003 daemon.err collectd[1495]: Unable to access rsm for retrieving server address

tim_lillis

having same problem but with dhcp address same ap model

syamantakomer

Hi Tim,

There is no issue reported in past for R750 with DHCP address facing same issue as discussed in this thread.

I request you to log a case with support.

In the meantime, please check below:

1- To avoid hitting static IP issue mentioned in this thread, please upload AP patch 5.2.0.0.5030 and update AP zones to it (If controller is running on 5.2.0 version).
2- Is the AP discovered on the controller? If yes, what events you see for this AP in the controller's event and alarm section?
3- Make sure port 22 and 443 are open in any firewall between AP to controller.
4- SSH into the AP and check AP syslog for any major error which may be preventing AP to get upgrade/configuration_update/SSH session. Command to see syslog is "get syslog log". You can also provide this information when opening the case with support.

Regards,
Syamantak Omer

unknown

We have vSZ and have the exact same issue trying to get one R510 AP to connect... We have plenty of APs on several different zones under the same vSZ controllers and all connect seamlessly... not this single one.

Patch has been applied last year.

unknown

Latency to the smartzone controller, from said location is high (>600ms). Would that be a problem?