A5-18 Reboot Cycles


#1

Our A5 is continuously rebooting without warning. I tried upgrading the firmware to see if perhaps it was panicing and there was a fix; I’ve also tried grounding it better (it’s now grounded twice) and that hasn’t helped either.

Last resort is going to be swapping out the Ethernet cable and power supply. I just bought a new A5-14 so I’m going to try to swap that power supply in to see if that helps at all. Aside from that, I’m stumped.

The reboots causing the issue are “Power on reset or Watchdog”. We have multiple other devices utilizing the same power source (a APC UPS) that aren’t rebooting, so I don’t think that’s the issue, but anything is possible. I’ll try bypassing that to see what happens.

"2017-03-06 01:23:16 (UTC +0000) : Shutdown reason: Reboot by a SW User Process - Firmware Upgraded"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:09 (UTC +0000) : System was upgraded"
"2015-01-01 12:00:22 (UTC +0000) : Shutdown reason: Reboot by a SW User Process - Firmware Upgraded"
"2015-01-01 12:00:23 (UTC +0000) : Radio Startup Status : Reboot by a SW User Process - Firmware Upgraded"
"2017-03-06 01:24:30 (UTC +0000) : Configuring Wireless Protocol: CSMA
Channel Num: 116
Center Freq: 5610
Tx Power: 22
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:22 (UTC +0000) : Shutdown reason: Console reboot command - Mode Changed to tdma"
"2015-01-01 12:00:22 (UTC +0000) : Radio Startup Status : Console reboot command - Mode Changed to tdma"
"2017-03-06 01:27:44 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 149
Center Freq: 5715
Tx Power: 22
Channel Width: 80
Change Reason: Default"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:31 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-06 01:32:54 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 59
Center Freq: 5265
Tx Power: 22
Channel Width: 80
Change Reason: Default"
"2017-03-06 01:34:06 (UTC +0000) : Channel Changed: Channel Num: 104
Center Freq: 5550
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2017-03-06 01:34:32 (UTC +0000) : Channel Changed: Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:32 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-06 05:23:38 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:32 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-06 05:45:40 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:31 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-06 16:46:49 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:32 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-07 00:25:44 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:32 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-07 00:29:39 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"
"2015-01-01 12:00:06 (UTC +0000) : Bootup configuration is verified successfully"
"2015-01-01 12:00:08 (UTC +0000) : Running Firmware Version: 2.2.1"
"2015-01-01 12:00:31 (UTC +0000) : Radio Startup Status : Power on reset or Watchdog"
"2017-03-07 03:50:10 (UTC +0000) : Configuring Wireless Protocol: TDMA
Channel Num: 131
Center Freq: 5625
Tx Power: 17
Channel Width: 80
Change Reason: user"

#2

Hi Chris,

We’ll pull the logs and review them if your radio is cloud monitored. It would be useful if you would contact Mimosa Support (chat or email) and provide serial numbers and/or logs so that they can help review the details rather than posting partial event logs here. The .tar files provide more information about how to solve problems, and the community members here don’t have access to review them.


#3

Hi Chris,

I was able to locate the radio on the cloud and pulled the logs. We’ll let you know what we find.


#4

Thanks Chris,

I’m not sure why, but it only seems to happen during the day? That may be because there’s only load on the device during the day., so it’s drawing more power. I’m trying to get access to our UPS in that building so that I can plug in directly to the power source instead of going through our UPS. But like I said, there are 3 other devices on that same power source (B5-lite, 2 ubnt) and none of them are rebooting.


#5

Good idea. All indications are that this is a power problem according to log messages. It could be a power budget problem, cabling problem, PoE, or radio. It requires a bit of troubleshooting to root cause. Moving to direct power would rule out a power budget problem on the UPS. In the meantime, I have logged a ticket and engaged our engineering team to advise on any other possible root causes.


#6

Engineering reviewed the logs, and we can’t find any root cause other than the power on reset message which is related to power loss.

Yes, throughput influences power draw, so the PoE supply could be near its power budget. We’ve had a few cases of radios rebooting when running speed tests, so published an FAQ about it here: http://ap.help.mimosa.co/ap-troubleshooting-guide-reboot-during-speed-tests

Please let us know the results of your testing.


#7

In order to get power on the roof we’re on I had to daisy-chain a few extension cords together. I moved our outdoor enclosure to shorten the distance of the extension cords by about 100-150ft and that seems to have fixed it.


#8

Excellent. Thanks for the update, @Christopher.


#9