Error on ZD 1200 and r500 aps not joining.

[elec_travis]

I have a property I just had to reset the ZD 1200 on. 24 of the APS came in and worked fine. 24 others had the cloud based firmware on them and wont talk to the ZD. I upgraded the FW to the Correct 104 version. That got me 10 more aps into the ZD. I still have 10 more that give me this error and will not finish the provisioning step. I have tried change mtus made sure ftp was open but still nothing. The IP 252.1 that is referenced is the ZD IP so Im not sure if maybe the ZD config got corrupted and needs a reset?

Dec 13 17:25:09 RuckusAP local2.err syslog: (ap state) AP begin to join ac.  
Dec 13 17:25:09 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 172.17.252.1(0) event, 
-- No such file or directory(2) 
Dec 13 17:25:09 RuckusAP local2.err syslog: WTP join cfm response, lwapp_notify_kernel_ip_addr [nat  ipv4
].   nat_ipv4_addr: 172.17.252.1    port: 0    family: 2   
Dec 13 17:25:09 RuckusAP local2.err syslog: WTP join cfm response, lwapp_notify_kernel_ip_addr [ipv6].   
ipv6_addr: ::    port: 0    
Dec 13 17:25:09 RuckusAP daemon.notice rsmd[33]: wsgclient ....... [stopped] (0.191)
Dec 13 17:25:09 RuckusAP daemon.notice rsmd[33]: wsgclient ....... [stopped] (0.074)
Dec 13 17:26:13 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 
15 re-transmits 
Dec 13 17:26:13 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 172.17.252.1(0) event, -- 
No such file or directory(2) 
Dec 13 17:26:45 RuckusAP local2.err syslog: (ap state) AP begin to join ac.  
Dec 13 17:26:45 RuckusAP local2.err syslog: Cannot notify kernel for Upd AP Param 172.17.252.1(0) event, 
-- No such file or directory(2) 
Dec 13 17:26:45 RuckusAP local2.err syslog: WTP join cfm response, lwapp_notify_kernel_ip_addr [nat  ipv4
].   nat_ipv4_addr: 172.17.252.1    port: 0    family: 2   
Dec 13 17:26:45 RuckusAP local2.err syslog: WTP join cfm response, lwapp_notify_kernel_ip_addr [ipv6].   
ipv6_addr: ::    port: 0    
Dec 13 17:26:45 RuckusAP daemon.notice rsmd[33]: wsgclient ....... [stopped] (0.189)
Dec 13 17:26:45 RuckusAP daemon.notice rsmd[33]: wsgclient ....... [stopped] (0.073)
Dec 13 17:27:49 RuckusAP local2.err syslog: Proceed to IDLE state from CONFIGURAION state, no resp after 
15 re-transmits 
Dec 13 17:27:49 RuckusAP local2.err syslog: Cannot notify kernel for Delete AP 172.17.252.1(0) event, -- 
No such file or directory(2) 
Dec 13 17:27:58 RuckusAP user.warn kernel: rks_ioctl_NODEDATA:4909 Node not found:00:01:ff:ff:ff:ff
Dec 13 17:27:58 RuckusAP user.warn kernel: rks_ioctl_NODEDATA: buffer error
OK

[elec_travis]

Thanks for the reply Anusha. The ap does get the FW for the ZD installed on it I can even see that the ap thinks its associated to the ZD. It just wont finish getting the config pushed to it. This is happening on 10 aps. Could there be something corrupted on the ZD and can that be fixed without have to reset the ZD.

[Anusha_Vemula]

Hi Elec,

In this case, I would suggest you to open a ticket with Ruckus TAC support to check the logs and assist you further.

- Anusha