B5C Reboot All days


#1

Hi … I have a 54.5km blackhaul link that works fine but the B5C station restarts every day up to twice, I do not understand why, its voltage is normal and the PoE changes and everything is the same
this is LOG from B5C station.

2018-05-12 16:57:43 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-07-04 05:52:41 (UTC +0000) bamboo_build_time_stamp=2017-07-04T05:51:22.004Z bamboo_build_number=9 project=FW-B5207 branch=release/1.4.6
2018-05-12 16:57:51 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243dXX.
2018-05-12 16:57:53 (UTC +0000) root: MIMO_EVENT Startup reason: Power On Reset
2018-05-12 17:03:22 (UTC +0000) root: MIMO_EVENT ethernet link down
2018-05-12 17:03:24 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2018-05-12 17:09:37 (UTC +0000) root: MIMO_EVENT: lat: 11.24, long XX.XXXX local_country: Colombia , remote_country: Colombia
2018-05-12 17:09:37 (UTC +0000) root: MIMO_EVENT: Successful Country Authentication
2015-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2018-05-14 06:26:52 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2018-05-14 06:27:09 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2018-05-14 06:27:19 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System
2018-05-14 06:27:25 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2018-05-14 06:27:28 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2018-05-14 06:27:28 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2018-05-14 06:27:36 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-07-04 05:52:41 (UTC +0000) bamboo_build_time_stamp=2017-07-04T05:51:22.004Z bamboo_build_number=9 project=FW-B5207 branch=release/1.4.6
2018-05-14 06:27:45 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243dXX.
2018-05-14 06:27:48 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System
2018-05-14 06:29:04 (UTC +0000) root: MIMO_EVENT: lat: 11.24, long: -XX.XXXX, local_country: Colombia , remote_country: Colombia
2018-05-14 06:29:04 (UTC +0000) root: MIMO_EVENT: Successful Country Authentication
2018-05-14 07:08:28 (UTC +0000) root: MIMO_EVENT ethernet link down
2018-05-14 07:08:29 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2015-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2018-05-14 21:58:15 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2018-05-14 21:58:32 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2018-05-14 21:58:42 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System
2018-05-14 21:58:48 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2018-05-14 21:58:51 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2018-05-14 21:58:52 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2018-05-14 21:58:55 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-07-04 05:52:41 (UTC +0000) bamboo_build_time_stamp=2017-07-04T05:51:22.004Z bamboo_build_number=9 project=FW-B5207 branch=release/1.4.6
2018-05-14 21:59:03 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243dXX.
2018-05-14 21:59:04 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System
2018-05-14 22:00:25 (UTC +0000) root: MIMO_EVENT: lat: 11.24, long: -XX.XXXX, local_country: Colombia , remote_country: Colombia
2018-05-14 22:00:25 (UTC +0000) root: MIMO_EVENT: Successful Country Authentication
2018-05-14 22:20:39 (UTC +0000) root: MIMO_EVENT ethernet link down
2018-05-14 22:20:40 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)


#2

This is probably something for the Mimosa Support guys, either the B5c is locking up for some reason or it is loosing power and the “Startup reason: Non-Responsive System” is a hold-over from it.

I have not seen this in ours, but we are not shooting that far either. Do you have the watchdog timer turned on?