Link crash - Non responsive system


#1

Getting link drops on a regular basis on 2 of 4 B5C links

Every time we see ‘non responsive system’ in the log

Have upgraded/downgraded firmware, replaced POE, replaced network cable

Seeing it on the units either end of link

Now happening on a daily basis

Contacted support, sent support files

Tried to email support today and Mimosa anti spam seems to now block our email addresses!

2017-05-28 10:11:39 (UTC +0000) mimo_upgrade[1917]: log_message: Executing logger MIMO_EVENT Firmware upgraded
2017-05-28 10:11:39 (UTC +0000) root: MIMO_EVENT Firmware upgraded
2015-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2017-05-28 10:12:38 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2017-05-28 10:12:55 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2017-05-28 10:13:05 (UTC +0000) root: MIMO_EVENT System was upgraded
2017-05-28 10:13:13 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2017-05-28 10:13:18 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-05-28 10:13:18 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-05-28 10:13:19 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2017-05-28 10:13:20 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-05-28 10:13:21 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-05-28 10:13:24 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-04-27 14:00:22 (UTC +0000) bamboo_build_time_stamp=2017-04-27T13:58:28.508Z bamboo_build_number=44 project=FW-B5194 branch=release/1.4.5
2017-05-28 10:13:30 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243d91.
2017-05-28 10:13:30 (UTC +0000) root: MIMO_EVENT Shutdown reason: UI-initiated reboot - Upgrade
2017-05-28 10:13:31 (UTC +0000) root: MIMO_EVENT Startup reason: User Reboot - Firmware Upgraded
2017-05-28 10:15:57 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-05-28 10:17:54 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-05-29 08:38:12 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-05-29 08:43:15 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-05-29 08:44:08 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-05-29 08:49:45 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-05-29 08:51:12 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-05-29 08:52:22 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-05-29 11:37:09 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-05-29 11:39:06 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-05-29 11:39:38 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-05-29 11:41:34 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-05-29 11:41:53 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-05-29 11:43:50 (UTC +0000) root: MIMO_EVENT Wireless associated
2015-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2017-05-30 05:52:29 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2017-05-30 05:52:46 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2017-05-30 05:52:56 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System
2017-05-30 05:53:02 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2017-05-30 05:53:05 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-05-30 05:53:05 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2017-05-30 05:53:07 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-05-30 05:53:07 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-05-30 05:53:09 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-05-30 05:53:13 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-04-27 14:00:22 (UTC +0000) bamboo_build_time_stamp=2017-04-27T13:58:28.508Z bamboo_build_number=44 project=FW-B5194 branch=release/1.4.5
2017-05-30 05:53:19 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243d91.
2017-05-30 05:53:20 (UTC +0000) root: MIMO_EVENT Startup reason: Non-Responsive System


#2

Really need to get an answer on this, have sent numerous emails and tried calling support but just get a voicemail. Message left but still no call back.

This is starting to bring back very bad memories of Ubiquiti kit!

Please can someone respond. As details in a previous email to support it seems the links we have running firmware 1.3.1 are not having this issue so can someone please just send us that firmware so we can roll all affected links back

Thanks!.


#3

Hi Andy,

We did receive your 8 tickets submitted in the last 24 hours, and we are not intentionally blocking your email. I added your email domain to our domain whitelist just in case. We will respond to each of the tickets today. It was a holiday in the United States yesterday, so we apologize for the delay in response.

From reading the tickets, it seems like you might have either a firmware mismatch or a hardware problem. A small minority of our installed base is still running firmware version 1.3.1, while the others have moved on to 1.4.x which is far more stable.


#4

Any update on this? Received a call last week and was promised a follow up the next day but nothing. Have moved one link back to 1.3 firmware and not a single reboot however the second link is using newer hardware and when i try the older firmware two of the chains totally disconnect.

Now today another reboot with this error. Support file sent by email.

Please can we get an answer on this. We moved away from Ubiquiti for main links do to reliability issues and bugs in firmware and now seem to be back where we started!

2017-06-01 09:14:04 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-01 09:14:04 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2017-06-07 09:40:33 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2017-06-07 09:40:39 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2015-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2017-06-07 09:41:42 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2017-06-07 09:41:59 (UTC +0000) root: MIMO_EVENT System time changed… phystats re-sync
2017-06-07 09:42:15 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2017-06-07 09:42:16 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2017-06-07 09:42:18 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-07 09:42:20 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-06-07 09:42:22 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-07 09:42:25 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2017-04-27 14:00:22 (UTC +0000) bamboo_build_time_stamp=2017-04-27T13:58:28.508Z bamboo_build_number=44 project=FW-B5194 branch=release/1.4.5
2017-06-07 09:42:31 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243d91.
2017-06-07 09:42:31 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - MuC has halted
2017-06-07 09:42:33 (UTC +0000) root: MIMO_EVENT Startup reason: User Reboot


#5

Hello Andy,

Our apologizes for the delayed responses, and thanks for the log data. Our development team has been looking at the log data provided. They do show information related to the radio rebooting, but it is not conclusive as to the root cause. As per our private comments provided on 6/7, we suspect a hardware problem, and suggest you pursue replacements. We will honor the RMA request through your Mimosa supplier.


#6

All,

We experienced this same problem and found that if the antennas are set to DHCP with Static Failover and the DHCP server does not respond, it will eventually lock up the antenna and it will reboot.

The solution is to set the network dropdown to Static and enter a Static IP address. We have confirmed this works with 1.4.6 on two separate links.

Thanks,
Tom


#7

Tom, a non-responsive system condition is a nondescript log message which can be triggered by a number of conditions. We appreicate you contacting our Support team and letting us look at the logs from your device.