Error on ZD 1200 and r500 aps not joining.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2018 10:10 AM
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
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
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 01:39 AM
Hi Elec,
What was the command you used in the AP CLI? Was it 'set-factory'?
This should work the same (for the most part) as a hardware reset.
Thanks,
Darrel.
What was the command you used in the AP CLI? Was it 'set-factory'?
This should work the same (for the most part) as a hardware reset.
Thanks,
Darrel.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 06:00 AM
Hello Darrel,
I used the cli set factory is there any difference between the "-" and no "-" ?
I used the cli set factory is there any difference between the "-" and no "-" ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 06:19 AM
'set factory' is the correct CLI command. 'set-factory' is invalid.
- Anusha
- Anusha
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 06:34 AM
Hi Elec, apologies for the hyphon confusion. Only the correct command would be accepted by the AP. Differen platforms and firmware revisions can have slightly different commands. Thanks to Anusha for the correction.
Darrel.
Darrel.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2018 12:47 AM
Hi Elec,
You can try upgrading an AP to the ZD firmware and check if that helps.
AP firmware can be downloaded from the ZD using below procedure. However, please make sure that ftp is enabled on the ZD.
To enable FTP :
ruckus>en
ruckus#config
ruckus(config)#ftp-anon
URL :
ftp:// IP address>
- Anusha
You can try upgrading an AP to the ZD firmware and check if that helps.
AP firmware can be downloaded from the ZD using below procedure. However, please make sure that ftp is enabled on the ZD.
To enable FTP :
ruckus>en
ruckus#config
ruckus(config)#ftp-anon
URL :
ftp://
- Anusha

