RB333 stops recording the graph after reboot

RouterOS General
1

Hello,

After a reboot our two RB333 (that both work as a backhaul link only about 2 miles apart from each other) will stop recording their graphing once they reboot. They will stop recording with a reboot even if they have store-on-disk checked mark for their resources and the like.

We are running ROS3.7 with firm on version 2.13 on both sides. Does the “store-on-disk” just not work for RB333s? Just curious we are tying to figure out an odd problem with a drop in connection and when we go to review our graphs on the resources and what have you they are all gone except for the new information recorded since uptime.

If any one has a clue that would help us in the right direction we would appreciate it.

It almost feels liek there is a bug in ROS3.7 with this firm of 2.13 not sure just putting this out there. It is pecuilar becasue it happens to both boards that are on the same firm and ROS.

-Sincerely,
DesertAdmin

2

Do you have NTP client configured on these routers ?

3

Yes we do have ntp configured on them but I guess we do not need them if NTP is a problem. It also seems that we have stream lined this router configs down because once a day our BH drops for no reason. connection looks fine all day until it decides to just stop talking to the other side and then the watchdog goes off and reboots. When the reboot occurs all of the graphing is gone and it has to start to re-record.

My main goal is to figure out why it stops working which then makes the watchdog reboot the BH.

I do not understand why the graphing also makes it spike up to 100% every other second when it is enabled.

Any ideas would be appreciated.

-Sincerely,
DesertAdmin

4

I’ve had the same graphing issues from 2.9.x versions also.
Check out these threads:

http://forum.mikrotik.com/t/graphing/19584/1

and

http://forum.mikrotik.com/t/graphs-not-saving-on-reboot/16102/1