I’d like to meet the engineer that changed the way configs are stored and handled on the SXTsq antennas and make him drive to the sites that are the result of this UTTER STUPIDITY!!!
If the config is just dragged over to the antenna - the GODAMMED SXTsq saves it in volatile memory - or in a place that isn’t permanent between reboots - UNLIKE EVERY OTHER MIKROTIK DEVICE!!
When you operate a network with SXTsq antennas as the minority this has proven to be a MAJOR PROBLEM when a config is uploaded and the tech doesn’t notice that it is a SXTsq antenna and forgets to move it into the fucking flash folder so that the device doesn’t wipe itself during a configuration reload!!!
This is so far the ONLY Mikrotik device with this bizarre and inconsistent behavior. Even software updates behave correctly - only configuration files MUST be saved to the flash folder in order for the antenna to be able to reconfigure itself on a reboot!!!
You need to put a warning on the reconfiguration dialog box when the selected config file is in the root (volatile) folder or fix this goddammed stupidity so that these antennas behave like all other Mikrotik devices for the purpose of uploaded and reconfiguring devices remotely!! Better yet, the reconfiguration drop down menu should not show files that are in the root folder - only the flash folder or any folder that is in non-volatile memory!! That way it is impossible to choose a configuration file from a place where it won’t exist during a reboot!!
Yet another unnecessary outage has been caused - another PISSED OFF customer!! Another emergency 2-4 hour dispatch!!
Was this a change between RouterOS versions? Your post is not very clear.
If it wasn’t a change between RouterOS versions, the one guilty of “utter stupidity” is the one that installed them in those sites without testing at least one device first (and the maintainer of course).
It’s a bit of a dumb change but this is really on you. I’m assuming you’re a provider of some sort, you did no testing prior to deployment? you don’t have any systems in place to save running configs remotely like Oxidized?
I get it, I would be a little upset too but I think you’re taking your anger out in the wrong way. Sounds like you need to deploy systems ot be proactive with config management and not reactive on the forums that wont change anything but just create troll comments - kinda like this one.
RouterOS 6.47. This is not a change between RouterOS versions - these damn SXTsq antennas have always done this. Drove us nuts with our automated provisioning system which we made a specific exception for. But field changes don’t use the automated system which is only used for initial deployment.
Yes, DigiLink is a provider. Another PISSED OFF CUSTOMER in a highly competitive environment. An emergency 2-4 hour dispatch all because of a STUPID INCONSISTENCY!!
To expect perfection from humans is ridiculous. The problem is with INCONSISTENT BEHAVIOR!! This is an ENGINEERING FAULT!!
When you manage a few hundred devices - 99% of which behave consistently and the ONLY way to notice that you are dealing with an inconsistent one is to notice the little tiny model number at the top of the Winbox window.
The reconfiguration dialog should NOT PERMIT THE SELECTION OF A CONFIGURATION FILE FROM THE ROOT FOLDER!!!
All of you armchair quarterbacks are being unreasonable!!
I handle over a few hundred radwin radios as well as another couple hundred firewall’s at remote sites. I don’t have these issues so I apologize for my armchair having too much knowledge and common sense. Attention to detail isn’t much to ask for and isn’t much effort to accomplish. Maybe it’s just not a thing in California?