A5c reboot with reason code 5006

Products A5
#1

Has anyone had A5c reboot on there own with clients and in the logs it gives reason code 5006?

We will have several A5c reboot on our network at the same time and come back. On majority of the A5c’s we have firmware 2.5.4. On our latest tower we put 2.5.4.1 firmware on those A5c’s. We have had the newest A5c’s reboot with the older A5c’s.

We are using WIFi interop with DHCP 82 and not SRS.

Any suggestion would be great appreciated.

Here is a log from one of the A5c.
2021-01-01 00:00:18 (UTC +0000) : Running Firmware Version: 2.5.4.1
2021-01-01 00:00:19 (UTC +0000) : Shutdown reason: Console reboot command - Reason code: 5006
2022-03-20 02:18:26 (UTC +0000) : First real time update from GPS at (UTC) Sun Mar 20 02:18:23 2022
2022-03-20 02:18:30 (UTC +0000) : [Boot_Reboot] Reboot reason: Console reboot command - Reason code: 5006
2022-03-20 02:18:31 (UTC +0000) : Management VLAN 52 creation is success
2022-03-20 02:18:56 (UTC +0000) : [Config] Configuring Wireless Protocol: WiFi Interop, Channel Num: 56, Center Freq: 5290, Tx Power: 18,Channel Width: 40
2022-03-20 02:19:02 (UTC +0000) : [EthernetUpDown] Ethernet link up (1000/Full)
2022-04-20 05:50:57 (UTC +0000) : [CriticalFault] No GPS signal was seen for 3 seconds
2022-04-20 05:51:26 (UTC +0000) : [CriticalFault] GPS signal recovered
2021-01-01 00:00:18 (UTC +0000) : Running Firmware Version: 2.5.4.1
2021-01-01 00:00:18 (UTC +0000) : Shutdown reason: Console reboot command - Reason code: 5006
2022-04-25 05:18:07 (UTC +0000) : First real time update from GPS at (UTC) Mon Apr 25 05:18:05 2022
2022-04-25 05:18:15 (UTC +0000) : [Boot_Reboot] Reboot reason: Console reboot command - Reason code: 5006
2022-04-25 05:18:17 (UTC +0000) : Management VLAN 52 creation is success
2022-04-25 05:18:41 (UTC +0000) : [Config] Configuring Wireless Protocol: WiFi Interop, Channel Num: 56, Center Freq: 5290, Tx Power: 18,Channel Width: 40
2022-04-25 05:18:47 (UTC +0000) : [EthernetUpDown] Ethernet link up (1000/Full)
2021-01-01 00:00:18 (UTC +0000) : Running Firmware Version: 2.5.4.1
2021-01-01 00:00:19 (UTC +0000) : Shutdown reason: Console reboot command - Reason code: 5006
2022-04-25 05:41:32 (UTC +0000) : First real time update from GPS at (UTC) Mon Apr 25 05:41:29 2022
2022-04-25 05:41:36 (UTC +0000) : [Boot_Reboot] Reboot reason: Console reboot command - Reason code: 5006
2022-04-25 05:41:38 (UTC +0000) : Management VLAN 52 creation is success
2022-04-25 05:42:03 (UTC +0000) : [Config] Configuring Wireless Protocol: WiFi Interop, Channel Num: 56, Center Freq: 5290, Tx Power: 18,Channel Width: 40
2022-04-25 05:42:08 (UTC +0000) : [EthernetUpDown] Ethernet link up (1000/Full)
2021-01-01 00:00:18 (UTC +0000) : Running Firmware Version: 2.5.4.1
2021-01-01 00:00:18 (UTC +0000) : Shutdown reason: Console reboot command - Reason code: 5006
2022-04-28 07:24:54 (UTC +0000) : First real time update from GPS at (UTC) Thu Apr 28 07:24:52 2022
2022-04-28 07:24:59 (UTC +0000) : [Boot_Reboot] Reboot reason: Console reboot command - Reason code: 5006
2022-04-28 07:25:01 (UTC +0000) : Management VLAN 52 creation is success
2022-04-28 07:25:26 (UTC +0000) : [Config] Configuring Wireless Protocol: WiFi Interop, Channel Num: 56, Center Freq: 5290, Tx Power: 18,Channel Width: 40
2022-04-28 07:25:31 (UTC +0000) : [EthernetUpDown] Ethernet link up (1000/Full)

#2

Yes this has happened to us several times ( may have to confirm the error code - but) - Basically if the radio becomes unresponsive - it will reboot itself - kinda cool actually - an internal watch dog if you will.

Odd that you are having this happen at the same time every day however - can you elaborate?

I will say that 2.5.4.2 is now the general release / firmware to use - I still have some on 2.5.4.1 and will be updating them soon. No major fix’s that I see - just some new MAC Address support and some general stability -

Having said that 2.5.4 had some security issues - so you want to update if you have any there.

#3

Thanks for your reply. We do plan to upgrade the firmware. The A5c do not reboot everyday. When they do reboot it will be several A5c at different locations that reboot at the same time. Three of the locations are fed by fiber to the tower. 2 Locations are PTP from 2 towers and a 3rd is a PTP from one of the tower that is fed by a PTP back to the tower that is fed by fiber.

So these are different locations where these A5c are at and are about 12 -15 miles apart.

We have mostly Netonix POE switches to power the A5c with one Cisco poe switch that is in our central office at the newest tower to provide power the those 4 A5c.

I did contact tech support and only suggestion they gave was to update the firmware and use the POE injectors that come with the A5c’s

#4

So, one thing that we found / heard was that the A5c’s like to run at 48V High - We also had Mimosa lightning arrestors and removed those on a recommendation from Mimosa.

After moving to 48V High we stopped having so many issues. The Netonix only does 48V H on port 1 if you have an 8 port and ports 1-4 if you have a 12 port. Check the switch before moving / testing your voltages - but that is what I recall.

Also - check your logs - we had ethernet flapping going on pretty bad and once we swapped to 48V H that seemed to have stopped - but we also removed the lightning arrestors at the same time.

I would also recommend that you work with Mimosa - if you have a bad unit and it is under warranty - they where really good with us on sending replacement units.