Another problem, and more..... Port Flapping :(


#1

Please !!!, always a surprise !!!

Please !!!, always a surprise !!!

We had a PtP with RapidFire equipment from LigoWave, and once again we tried to trust MIMOSA and changed them to beautiful B5c, BUT! We changed the equipment, and within 20 min of being working! They started to fail on the ethernet port!

The same wire AS BEFORE we had the RapidFire connected !! Without any problem, for more than 8 months. !!!

All this we already realize:
0 http://backhaul.help.mimosa.co/backhaul-troubleshooting-guide-ethernet
1 Switch to new Cable (shielded CAT6)
2 We set new ground.
3 we change the POE
4 We connected the Mimosa to a Switch and from there to our Router (CCR2036 Mikrotik)

For the doubts, it is our tower, there are no FM equipment or anything similar.

Every time we install a Mimosa Radios we encounter problems. It’s a matter of stopping trying. It is a shame since you see success cases … will we stop trying?


2017-06-02 03:59:38 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 03:59:40 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x221622.
2017-06-02 03:59:40 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 03:59:41 (UTC +0000) root: MIMO_EVENT Startup reason: Power On Reset
2017-06-02 03:59:48 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 03:59:50 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 03:59:51 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 03:59:52 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 03:59:59 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 03:59:59 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:01 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:03 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:08 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:10 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:13 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:14 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:20 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:26 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:28 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:37 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2017-06-02 04:00:38 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:41 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:43 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:00:51 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:00:57 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:01:02 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:01:05 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:01:14 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:01:17 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:02:12 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:02:15 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:02:20 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:02:22 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:02:23 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:02:25 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:02:29 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2017-06-02 04:02:33 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:02:42 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:02:46 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:02:50 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:02:56 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:03:00 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2017-06-02 04:03:04 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:03:07 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:03:10 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:03:13 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:03:15 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:03:20 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:03:30 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:03:31 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:04:21 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:04:25 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:04:34 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:04:35 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2017-06-02 04:05:36 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:05:38 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:05:40 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:05:53 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:06:00 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:06:10 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:06:12 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:06:23 (UTC +0000) root: MIMO_EVENT ethernet link up (10/Half)
2017-06-02 04:06:41 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:06:46 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:06:50 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:06:54 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:06:57 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:06:58 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:07:03 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:07:06 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:07:07 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:07:19 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)
2017-06-02 04:08:33 (UTC +0000) root: MIMO_EVENT ethernet link down
2017-06-02 04:08:43 (UTC +0000) root: MIMO_EVENT ethernet link up (1000/Full)


#2

I forget to comment, when we make the fault we can generate with just send more than 100Mbps of traffic on the ethernet, if we do speed test from B5c to the other B5c there is no problem, it is more 500Mbps without TROUBLE!


#3

We also had trouble with B5Cs when we connected them to MikroTik routers and/or switches. We found that the Flow Control for the Ethernet port on the B5C is defaulted to ‘off’. This appears to create a problem between the B5C and the MikroTik equipment. Turning on the Flow Control on the B5C fixed the problem. We also found that leaving Flow Control off on the B5C and ‘locking’ the MikroTik ethernet port to a fixed speed (we tried 100 Mbps) would fix the problem. We did not try ‘locking’ the MikroTik to 1 Gbps, since we chose to leave the MikroTik in ‘auto’ mode and use Flow Control on the B5C.

John Rayfield, Jr.
Rayfield Communications


#4

Thanks! i am try now!


#5

Cesar, this issuse should have something to do with your cable or any thing else, we’ve had a b5c up and running for the last year and to be honest it goes really well as long as it doesnt’t receive any noise, even better and more rock solid than our epmp1000 backhauls.


#6

We’re actually having a similar issue also b5c same issue flapping port, whats funny is when it autonegotiated to 1000mbit clients traffic over the ethernet+rf was showing sub 100mbit like 20mbit, and the port was flapping… we forced the port to 100mbit and somehow that seems to mostly fix the issue the speeds getting 100mbit now but still i see port flapping, also we need more than 100mbit of traffic, we’re busy replacing the cable, but a fluke test reports no errors on the cable itself.

But will swap the cable and see what that does.


#7

Try with old firmware - 1.31 or 1.4.1