Ruckus AP stuck in provisioning mode

[silvestre]

Hi everyone I'm using a zone director 1000 and 7363 APs. 2 of the aps are stuck in provisioning mode and keep on rebooting. I have done a hard reset as well it goes back to provisioning.

Has anyone faced a similar issue

[snagrat]

You use VLANs?

[silvestre]

No vlans

[silvestre]

I have even reduced the MTU to 1100 to test but same result

[snagrat]

No funny subnets (ie DHCP super scope?)

[DMcCoy]

Have you tried with them plugged in elsewhere? I have seen provisioning fail repeastedly when the cable could not negotiate 1Gb correctly

[silvestre]

No funny subnets (ie DHCP super scope?)

 

Nope no super scopes

[silvestre]

Have you tried with them plugged in elsewhere? I have seen provisioning fail repeastedly when the cable could not negotiate 1Gb correctly

 

Did not try that will do tomorrow

[silvestre]

So i tried plugging it elsewhere and the same problem

 

It ends with this error message on the AP

 

 

 

Dec 3 00:01:05 RuckusAP kern.info kernel: kstat_init_tasklets: hash=0xd5, func=0x8332caac v54_flow_cur_ager

Dec 3 00:01:05 RuckusAP user.info syslog: First IGMP/MLD Query interval timeout in 300 sec

Dec 3 00:01:05 RuckusAP daemon.notice rsmd[18]: smartcast ....... [started] (0.183)

Dec 3 00:01:05 RuckusAP daemon.notice rsmd[18]: IP event ........ [started] (0.022)

Dec 3 00:01:05 RuckusAP daemon.notice rsmd[18]: supplicant ...... [started] (0.089)

Dec 3 00:01:05 RuckusAP daemon.notice rsmd[18]: hostap .......... [started] (0.030)

Dec 3 00:01:05 RuckusAP daemon.notice rsmd[18]: eth1x ........... [started] (0.030)

Dec 3 00:01:05 RuckusAP daemon.notice rsmd[18]: auto-prov ....... [started] (0.000)

Dec 3 00:01:05 RuckusAP kern.info kernel: br0: topology change detected, propagating

Dec 3 00:01:05 RuckusAP kern.info kernel: br0: port 3(eth2) entering forwarding state (webs,244)

Dec 3 00:01:06 RuckusAP daemon.notice rsmd[18]: webserver ....... [started] (0.898)

Dec 3 00:01:06 RuckusAP daemon.notice rsmd[18]: rsm_led ......... [started] (0.022)

Dec 3 00:01:06 RuckusAP daemon.notice rsmd[18]: rfwd ............ [started] (0.010)

Dec 3 00:01:06 RuckusAP kern.info kernel: v54_bsp: 0x0

Dec 3 00:01:06 RuckusAP daemon.notice rsmd[18]: telnetd ......... [started] (0.108)

Dec 3 00:01:06 RuckusAP daemon.notice rsmd[18]: sshd ............ [started] (0.044)

Dec 3 00:01:06 RuckusAP authpriv.warn dropbear[254]: Failed reading '/writable/data/dropbear/dropbear_dss_host_key', disabling DSS

Dec 3 00:01:06 RuckusAP authpriv.info dropbear[254]: Running in background

Dec 3 00:01:07 RuckusAP daemon.notice rsmd[18]: snmpd ........... [started] (1.089)

Dec 3 00:01:07 RuckusAP daemon.notice rsmd[18]: snmptrap ........ [started] (0.333)

Dec 3 00:01:07 RuckusAP local0.err snmpd[281]: /var/run/snmpd.conf: line 3: Error: Name or service not known

Dec 3 00:01:07 RuckusAP local0.err snmpd[281]: /var/run/snmpd.conf: line 4: Error: Name or service not known

Dec 3 00:01:07 RuckusAP local0.info snmpd[281]: NET-SNMP version 5.3.0.1

Dec 3 00:01:08 RuckusAP kern.info kernel: af_l (br0): version=1.0.0, build on Mon Aug 5 12:18:22 PDT 2013

Dec 3 00:01:08 RuckusAP kern.info kernel: NET: Registered protocol family 30

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: apmgr ........... [started] (0.331)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: meshd ........... [started] (0.028)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: sntp ............ [started] (0.022)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: hotspot ......... [started] (0.028)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: tr069 ........... [started] (0.028)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: aerosctd ........ [started] (0.028)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: sysinfo-archive . [started] (0.027)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: l2tp ............ [started] (0.027)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: zapd ............ [started] (0.001)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: channelfly ...... [started] (0.463)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: autoboot ........ [started] (0.027)

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: rsmd: started 31/32 modules -

Dec 3 00:01:08 RuckusAP daemon.notice rsmd[18]: (11.000)

Dec 3 00:01:08 RuckusAP daemon.info init: starting pid 322, tty '': '/bin/cttyhack /usr/bin/-rkscli'

Dec 3 00:01:09 RuckusAP daemon.info channel-wifi0: channefly mode set to DISABLED

Dec 3 00:01:09 RuckusAP daemon.info channel-wifi1: channefly mode set to DISABLED

Dec 3 00:01:11 RuckusAP cron.notice ntpclient[349]: Using server: ntp.ruckuswireless.com

Dec 9 09:43:04 RuckusAP cron.notice ntpclient[349]: Time set from remote server

Dec 9 09:43:04 RuckusAP cron.notice ntpclient[349]: Skew 553313401.6mS, freq adjust 0

Dec 9 09:43:11 RuckusAP local2.err syslog: Cannot find FIS directory info

Dec 9 09:43:27 RuckusAP daemon.warn Eved: Last Reboot Reason: unknown

Dec 9 09:43:36 RuckusAP kern.debug kernel: wlan50 (WE) : Driver using old /proc/net/wireless support, please fix driver !

[EricM_NetCtrl]

What version of code are you trying to provission to the AP's? Are you holding in the reset for more than 10sec to do a full factory reset.?, after you factory reset if you connect the AP's to your laptop do you get the Standalone WEB GUI.

 

Eric

[silvestre]

What version of code are you trying to provission to the AP's? Are you holding in the reset for more than 10sec to do a full factory reset.?, after you factory reset if you connect the AP's to your laptop do you get the Standalone WEB GUI.

 

Eric

 

The zone director version is 9.3.4.0.21 so it changes all the AP's to the same version. I had upgraded this Ap to version 10 and it downgraded it once approved on the controller.

Yes i did a hard reset and got the standalone web gui. I still can get to the AP web gui using the default password and not the zone director login. Although it says that this AP is being managed by the zone director.

[EricM_NetCtrl]

When you say you had to upgrade to version 10 do you mean 9.10? have you tried factory resetting the AP then when a standalone re-firmware the AP with the 100.1.0.0.500 image then once thats upgraded then re-connect it to your network. You say you have a flat network?

 

Eric

[silvestre]

When you say you had to upgrade to version 10 do you mean 9.10? have you tried factory resetting the AP then when a standalone re-firmware the AP with the 100.1.0.0.500 image then once thats upgraded then re-connect it to your network. You say you have a flat network?

 

Eric

Hi Eric yes i had imaged it with 100.1.0.0.500 and then approved it on the zone director, It then downgraded the firmware to 9.3.4.0.21 but still stuck on provisioning loop.

 

Yes its a flat network.

[silvestre]

Anything else i can try?