Did some updates to 6.37.4 today. Some CPEs did not come back. Seems randomly distributed over different models/source firmware/places. 1 out of twenty.
Angry customer calls … Some seem to need a power cycle.
Configuring a SXT AC for a business customer as replacement. Ethernet LED does not work with 6.37.4.
It is just a matter of quality …
Yup, lets switch to other vendor, pay 20x more and have exactly the same problems only 10x bigger time intervals, and software updates/patches once a year, etc,etc. By the money you saved you should have 2 devices on all locations in case one goes bust…
Sorry , nothing personal, simply working with people everyday that would like to get everything or 1/10th of the price…
For exact reasons mentioned by ste, I always do a test at home in the lab (yes, I have several MKtik’s in the lab, with client configs etc…) before putting the new software in “production” at the client. I know, several RB751’s are still on 6.37.3, because it fails to put up the Wireless card after installing the new version. So I rolled back and leave it like that. Customer is happy and does not complain.
The hardware is not so expensive, and you can have a lab at home, with configs of all customers.
ste,
I’m sorry to hear about your problems.
What RouterBOARD was it? What RouterOS version was installed before?
How many board were affected actually?
Thank you very much for the report about SXT LED. For our faster reaction, it is advised to contact support@mikrotik.com about all possible software issues you have.
We do testing, too. But the problem we are getting seems to be site dependend. Some CPEs do not connect to some sectors they where connected before.
Adding them to the access list of a neighboring sector allows them to login again.
MT have done changes to the connect algorithm.
This happens with different CPEs mostly SXT nd and ac. Most of them are upgraded from 6.34 but not all. It seems if there are more APs with the same SSID but the cpe is only allowed to connect to one of them it does not connect (we use access lists to steer the cpes). May be it gets one of the other APs with stronger signal and insists on connecting to this.
So something in the connect algorithm in the new wireless package has changed.
Just had a bad day … so please excuse 
).
Actually I’ve had the same problem with ubiquiti devices connecting to ubiquiti ap’s too. Think it’s more of a general 802.11 issue than a specific Mt one?
We use nv2 so I guess different vendor different problem.
I’m sorry you have had such problems. Though I don’t think quality is in question here. I have just under 200 Mikrotik devices deployed, and I have only had two issues with updated. Both were CCR1009’s that had an flash error that was fixed very quickly.
The quality is much better than before. Some years ago even OSPF was unstable between versions so it was a hassle to keep things living. Our main concern is wireless now. CPEs not connecting randomly is no fun. It makes things unpredictable. nv2 needs a writup to match .ac speeds and scale better beyond 10 CPEs.