B5c Reboot by a SW User Process - Reason code: 2000

i have an issue with b5c link rebooting either the station or the AP
firmware 2.8.1

2021-03-21 13:12:36 (UTC +0000) root: MIMO_EVENT ethernet link down
2021-03-21 13:12:42 (UTC +0000) root: MIMO_EVENT ethernet link up(1000/Full)
2021-03-21 13:12:44 (UTC +0000) root: MIMO_EVENT ethernet link duplex Full
2021-03-21 13:12:56 (UTC +0000) PHP_DBG: MIMO_EVENT System time will be synchronized via GPS
2021-03-21 13:13:23 (UTC +0000) root: MIMO_EVENT build_time=2021-01-20 19:03:51 (UTC +0000) bamboo_build_time_stamp=2021-01-20T18:49:55.674Z bamboo_build_number=64 project=FWREL-RB5P24 branch=release/2.8.1
2021-03-21 13:13:30 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-21 13:13:36 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - Reason code: 2000
0000-01-01 00:00:34 (UTC +0000) root: MIMO_EVENT Running Firmware Version: 2.8.1
0000-01-01 00:00:53 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2021-03-21 13:31:37 (UTC +0000) nmea[411]: MIMO_EVENT First real time update from GPS at (UTC) Sun Mar 21 13:31:37 2021
2021-03-21 13:31:40 (UTC +0000) root: MIMO_EVENT ethernet link up(1000/Full)
2021-03-21 13:31:40 (UTC +0000) root: MIMO_EVENT ethernet link duplex Full
2021-03-21 13:31:52 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2021-03-21 13:32:02 (UTC +0000) root: MIMO_EVENT ethernet link down
2021-03-21 13:32:09 (UTC +0000) root: MIMO_EVENT ethernet link up(1000/Full)
2021-03-21 13:32:12 (UTC +0000) root: MIMO_EVENT ethernet link duplex Full
2021-03-21 13:32:22 (UTC +0000) PHP_DBG: MIMO_EVENT System time will be synchronized via GPS
2021-03-21 13:32:50 (UTC +0000) root: MIMO_EVENT build_time=2021-01-20 19:03:51 (UTC +0000) bamboo_build_time_stamp=2021-01-20T18:49:55.674Z bamboo_build_number=64 project=FWREL-RB5P24 branch=release/2.8.1
2021-03-21 13:32:57 (UTC +0000) root: MIMO_EVENT Shutdown reason: Power On Reset
2021-03-21 13:32:58 (UTC +0000) root: MIMO_EVENT Reboot reason: Power On Reset
2021-03-21 13:34:11 (UTC +0000) root: MIMO_EVENT: Successful Country Verification
2021-03-21 13:36:26 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-21 23:18:14 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-21 23:19:42 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-21 23:27:19 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-21 23:28:48 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-21 23:45:26 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-21 23:45:57 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 01:10:37 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 01:12:03 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 02:32:26 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 02:33:56 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 06:15:48 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 06:17:16 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 09:23:16 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 09:24:41 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 12:42:10 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 12:44:16 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 13:03:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
0000-01-01 00:00:34 (UTC +0000) root: MIMO_EVENT Running Firmware Version: 2.8.1
2021-03-22 13:04:17 (UTC +0000) root: MIMO_EVENT ethernet link duplex Full
2021-03-22 13:04:17 (UTC +0000) nmea[415]: MIMO_EVENT First real time update from GPS at (UTC) Mon Mar 22 13:04:14 2021
2021-03-22 13:04:17 (UTC +0000) root: MIMO_EVENT ethernet link up(1000/Full)
2021-03-22 13:04:18 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2021-03-22 13:04:29 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2021-03-22 13:04:39 (UTC +0000) root: MIMO_EVENT ethernet link down
2021-03-22 13:04:46 (UTC +0000) root: MIMO_EVENT ethernet link up(1000/Full)
2021-03-22 13:04:49 (UTC +0000) root: MIMO_EVENT ethernet link duplex Full
2021-03-22 13:04:56 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 13:05:06 (UTC +0000) PHP_DBG: MIMO_EVENT System time will be synchronized via GPS
2021-03-22 13:05:06 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 13:05:24 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 13:05:32 (UTC +0000) root: MIMO_EVENT build_time=2021-01-20 19:03:51 (UTC +0000) bamboo_build_time_stamp=2021-01-20T18:49:55.674Z bamboo_build_number=64 project=FWREL-RB5P24 branch=release/2.8.1
2021-03-22 13:05:40 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - Reason code: 2000
2021-03-22 13:05:41 (UTC +0000) root: MIMO_EVENT Reboot reason: Reboot by a SW User Process - Reason code: 2000
2021-03-22 13:06:53 (UTC +0000) root: MIMO_EVENT: Successful Country Verification
2021-03-22 14:22:21 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2021-03-22 14:23:43 (UTC +0000) root: MIMO_EVENT Wireless associated
2021-03-22 20:18:11 (UTC +0000) root: MIMO_EVENT Wireless disassociated

I’ve not seen a reason code 2000, or at least made note of it on my B5c radios or B11s.

I can run through some of my old Syslogs and see if it comes up. But I would expect some sort of Watchdog or power issue. Possibly low power on the PoE port?

Have you talked to Mimosa Support about this error?

haven`t talk to the support team yet.

I would recommend chatting with them, please please please report back with any solutions so I can reference to other people a solution.

Hi folks,

Lets get this device RMA’d. Please open up a support chat and they’ll take care of it.

I am having this same issue on one of our b5 links, sw user process reason code 2000. Is the only solution to this an RMA? It has never had an issues until I recently upgraded to 2.8.1, the link performs much better with thos firmware but I get these reboots. If I need to replace it we have spares, but if there is another reason for this I would like to know.

2021-09-07 15:51:44 (UTC +0000) root: MIMO_EVENT Reboot reason: Reboot by a SW User Process - Reason code: 2000

From the looks of it @net1, @DustinS has been having guys get in touch with Mimosa support for RMA of the effected device.