nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ruckus ZoneFlex 7982 continuous reboot

unknown

I have a Ruckus ZoneFlex 7982 and after a couple of days disconnected due to a vacations' trip the AP is performing continuous reboots.
No changes in the configuration. The AP is configured as bridge and get the internet from a DSL router (PPPoE).
The support log shows the following:

Jan 2 14:52:21 RuckusAP daemon.warn Eved: Last Reboot Reason: application reboot

Jan  2 14:52:27 RuckusAP local2.err syslog: Parameter value L2 is invalid for parameter Tunnel-Mode 

Jan  2 14:52:33 RuckusAP user.info kernel: br0: port 3(wlan0) entering disabled state (hostapd,423)

Jan  2 14:52:33 RuckusAP user.info kernel: br0: port 3(wlan0) entering learning state (hostapd,423)

Jan  2 14:52:34 RuckusAP user.info kernel: br0: port 3(wlan0) entering forwarding state (swapper,0)

Jan  2 14:52:42 RuckusAP cron.notice ntpclient[690]: Using server: ntp.ruckuswireless.com

Jan  2 14:52:43 RuckusAP cron.notice ntpclient[690]: Time set from remote server

Jan  2 14:52:43 RuckusAP cron.notice ntpclient[690]: Skew 31.6mS, freq adjust 0

Jan  2 14:52:43 RuckusAP cron.notice ntpclient[692]: Using server: ntp.ruckuswireless.com

Jan  2 14:52:43 RuckusAP cron.notice ntpclient[692]: Time set from remote server

Jan  2 14:52:43 RuckusAP cron.notice ntpclient[692]: Skew 265.2mS, freq adjust 0

Jan  2 14:52:57 RuckusAP daemon.notice rsmd_func[713]: Monitor: APMgr process not alive

Jan  2 14:52:57 RuckusAP daemon.err rsmd[66]: Receive reboot msg [a,1] 

Any ideas?

Find more posts tagged with

Accepted answers

All comments

unknown

what version are you on?

unknown

Firmware? I have updated it to the latest one.

unknown

Base 100 image?

unknown

Not sure I got your question....is it still about the firmware?

unknown

Leo,

Reboots happen for many reason starting power faults to bugs in the software. In the AP support, you should be able to see reboot reasons and if that does not make sense then better to upgrade to latest and if that still persists, better open a support ticket..

btw is your AP working as standalone or with a controller?

unknown

Stand Alone! The reboot reason (I think) is listed below
Jan 2 14:52:27 RuckusAP local2.err syslog: Parameter value L2 is invalid for parameter Tunnel-Mode
I have already upgraded it to latest version.

unknown

ok. got it. reason reboot info is in AP support file and when you search in it. it should look like below:

### Reboot Reason ###

user reboot

### Reboot Reason In Detail Recently ###

              Reboot Time            UP Time Total Boot Reason

Tue Sep 22 03:33:36 2015     7 day 00:29:33         13 WebUI, user requests a reboot

Tue Sep 29 12:04:53 2015     7 day 08:30:51         14 WebUI, user requests a reboot

Mon Oct 5 03:26:06 2015     5 day 15:20:48         15 WebUI, user requests a reboot

Mon Dec 7 05:15:37 2015    63 day 01:48:53         16 WebUI, user requests a reboot

Fri Dec 11 04:28:30 2015     3 day 23:12:05         17 WebUI, user requests a reboot

Wed Dec 16 04:52:22 2015     5 day 04:12:29         18 WebUI, user requests a reboot

### Reboot Reason End ###

unknown

Here you have it

### Reboot Reason ###

application reboot



### Reboot Reason In Detail Recently ###

              Reboot Time            UP Time Total Boot Reason

 Sat Jan  2 14:54:27 2016     0 day 00:01:00         19 Crash Dump,/usr/sbin/apmgr receive Signal# Segmentation fault # 

 Sat Jan  2 14:54:42 2016     0 day 00:01:15         19 Monitor: APMgr process not alive

 Fri Jan  1 16:03:53 2016     0 day 00:00:58          1 Crash Dump,/usr/sbin/apmgr receive Signal# Segmentation fault # 

 Tue Jan  5 19:08:40 2016     0 day 00:01:15          1 Monitor: APMgr process not alive

 Tue Jan  5 19:10:13 2016     0 day 00:01:02          2 Crash Dump,/usr/sbin/apmgr receive Signal# Segmentation fault # 

 Tue Jan  5 19:10:26 2016     0 day 00:01:15          2 Monitor: APMgr process not alive



### Reboot Reason End ###

unknown

Anyone?

unknown

Yeah, what version have you updated the AP too.

As the current stand alone images are Base 100.X

So are you running base 100 image? and what version

unknown

Segmentation fault is about memory access violation - I would open a ticket and put the support file from the AP in the ticket

unknown

Looks like there is a fix in the latest 9.12.2 MR just released for the ZD