I have 2 different routerboards running same setup apart from the Ips and ssid. They are both rb600 with 5.14.
Both run a netwatch which runs a script to change the ssid in case of link falure. Anyway this script works fine on one of the routers but on the other one it simply doesn’t do anything when the ping fails. The netwatch shows down but the script doesn’t run! Ive checked and double checked both configs and they are the same so I know the config works. I just cant understand why it only works on one router. I’m not new to mikrotik either ive been using it for 10 years so this has stumped me? Also it used to work in the past. Its like it just stopped working? No settings have changed or anything. Anyone ever had anything like that happen?
I am not sure what your situation is but it strikes me as odd.
I am not sure why you would want to change the SSID of a link when it fails… what about resetting the interface or changing the channel? If your having link failures then there is something wrong that should be fixed rather then circumvented. You should be able to set the SSID to something unique and leave it.
I understand, however, that you may have a reason for doing this that I don’t understand so as to answer the particular question I would have to review your router’s config. I doubt that it is an issue with the operating system or hardware because all of my scripts run quite reliably.
You could try adding an email notice to the script to see when it runns so you can determine if the script is truly not running or if it is just not functioning as expected.
Hi, Thanks for replying. The reason the ssid changes is that its a station and there is two different ap’s it can connect to. Rather than using the connect list I find this a better way to control which AP it uses. It just changes back and forth in event of failure until it gets a connection. I can specify how long it will wait between changes and also not make it too sensitive to change 
Its not like they do fail often but as you know in the space of some years it can happen at some point! And for backhauls from a cell site it makes sense to always double up AP side even when you only have one dish at the station end.
But anyway I can tell the script is not running because in netwatch I use the name of the script to run and in the system scripts it dosent show any runs even though the netwatch host has gone down. Its really weird as the other one I have running like that is same config and same type hardware. I guess it must be some really obscure problem/bug with the OS? I run scripts like this on maybe 50 different MT routers and only this has happened once! If I didn’t have same config running on another unit I would have probably already reset it and assumed it was my bad.
After you explain it, that sounds like a great idea…
The only thing I can think of is to do a netinstall on it and re-apply the config.