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

[hyosang_choi]

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?

[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

[cristiano_rodri]

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.

[cristiano_rodri]

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

[syamantakomer]

Hi Cristiano,

600ms is very high and could be cause of this issue.