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-13-2018 10:57 AM
Hi Elec,
This could be related to the firmware you're running on your ZD1200, rather than the AP.
Please can you advise what version your ZD is on?
Thanks,
Darrel.
This could be related to the firmware you're running on your ZD1200, rather than the AP.
Please can you advise what version your ZD is on?
Thanks,
Darrel.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2018 11:41 AM
Hello Darrel,
The FW on the ZD is 10.1.1.0 build 42. I started the APS off on Zoneflex 104.0.0.1347 software. After they connect to the ZD they download the 10.1.1.0 software and installs correctly. This process worked correctly for 10 out of 20 of the aps so not sure if i was just lucky? Or if something in the ZD cfg corrupted along the way?
Thanks again.
The FW on the ZD is 10.1.1.0 build 42. I started the APS off on Zoneflex 104.0.0.1347 software. After they connect to the ZD they download the 10.1.1.0 software and installs correctly. This process worked correctly for 10 out of 20 of the aps so not sure if i was just lucky? Or if something in the ZD cfg corrupted along the way?
Thanks again.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2018 11:46 AM
Hi Elec,
Many thanks for confirming the ZD firmware version. I asked as there is a very small chance of connection issues on firmware prior to 9.10 with some revisions of the R500 hardware but it sounds like this isn't the case here.
Have you tried perorming a 'hard' factory-default (hold down the Reset button for 20+ seconds) on one of the APs that's failing to join and trying again?
Many thanks,
Darrel.
Many thanks for confirming the ZD firmware version. I asked as there is a very small chance of connection issues on firmware prior to 9.10 with some revisions of the R500 hardware but it sounds like this isn't the case here.
Have you tried perorming a 'hard' factory-default (hold down the Reset button for 20+ seconds) on one of the APs that's failing to join and trying again?
Many thanks,
Darrel.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2018 12:20 PM
Thanks again.
I wont be back onsite to try a full hadware reset till next week. I have tried the reset from the cli along with re-uploading the FW to the AP. if that still does not work what would be another step?
Elec
I wont be back onsite to try a full hadware reset till next week. I have tried the reset from the cli along with re-uploading the FW to the AP. if that still does not work what would be another step?
Elec