I’ve sent in a supout but have heard nothing back yet. Its a pre-v5 RB532 with daughterboard. It never did this running up to ROS 2.9.50 but since v3 upgrade it has. No other equipment I have does this, just this one. Its been running a year no problems until upgrade so it wasn’t coincidence. Oh yeah I updated the firmware it made no difference.
Its on a tower so if I downgrade it back to 2.9.50 will I have to go there physically or should it be happy with remote downgrade with the daughterboard and two R52 radios installed?
I haven’t done this except once about a year ago – I copy the file to the RB 532 then choose what from winbox to downgrade - or do you have to do it through console.
Thanks for the info…
Scott
This board is starting to reboot a lot more. What is the best way to modify the logging options so I can see when the unit rebooted (log to disk). Right now every time it reboot I see how long it was up and the log gets cleared out - I’d like the reboots to be written to disk so I can see in the log every time it happened.
Any ideas which items to log to disk to best show a problem reboot?
Thanks,
Scott
use a syslog server. a simple linux box can do that for you. i use for example syslog-ng for that on debian. on ros use as “action” remote for the logs you want to send to the syslog server. in the configuration for the action remote you just need to type in the ip address and the port for the syslog server.
regards
Jan