After some time, usually after 14 day, on CCR the ROS started to colabse, first crashed dude it self, after came services starting to be not accessible (telnet, ssh, web), then finally was accessible only MAC telnet thru which it was possible to reboot device (once device passes traffic of several hundreds client it is big problem to wait until late night to restart it and get Dude working). Then there was gaps in graphs during regular operation.Could you describe what is poor behavior in your case? We are also unhappy customers using a RB11004AHx4 Dude edition.
This is, what was making on CCR, no longer such problem on that RB1100AH4, only sometime, but it gets sorted out by averagingAfter migration to The Dude 6.41.2 on RB11004AHx4 Dude edition most of our graphs has gaps
Thank you for some hints, which I hadn't think of. The RAM will be probably crucial as system says 890MBytes used of 1GB total. This can be answer..RB1100ahx4 is great for networking, very efficient and powerful machine
is not about stability, you must be aware of computational power of rb1100ahx4 router CPU, its a little A15 ARM quad core like a high end smartphone or tablet cpu, you must size the dude accordingly:
For rb750gr3
maximum of 40 services monitoring and maximum 4 days of raw value data storage and maximum 75 mega-byte database size
For rb1100ahx4
maximum of 80 services and maximum 4 days of raw value data storage and maximum 150 mega-byte database size
For ccr1036
maximum of 160 services and maximum 4 days of raw value data storage and maximum 300 mega-byte database size
Anything beyond that you will have not good results
beyond that you need a separate x86 device to host the dude
for big networks multiple virtualized instances of the dude will be needed, decent ssd storage etc etc
always keep the dude database size under 500mega-byte to keep good performance
Network monitoring IS NOT a light task
is a very intensive one not only in terms of CPU usage but in terms of storage i/o too
NEVER use onboard storage to sotrage the dude database for long term usage, in the case of rb1100ahx4 dude edition always use the 60gb ssd to host it
because monitoring is very write intensive it leads to a premature exhaustion of finite and scarce write cycles of the flash memory
that numbers come exclusively from my personal experience deploying the dudeVery nicely written. But where did you take the sizing numbers from?
good point that i have not take in countThank you for some hints, which I hadn't think of. The RAM will be probably crucial as system says 890MBytes used of 1GB total. This can be answer..RB1100ahx4 is great for networking, very efficient and powerful machine
is not about stability, you must be aware of computational power of rb1100ahx4 router CPU, its a little A15 ARM quad core like a high end smartphone or tablet cpu, you must size the dude accordingly:
For rb750gr3
maximum of 40 services monitoring and maximum 4 days of raw value data storage and maximum 75 mega-byte database size
For rb1100ahx4
maximum of 80 services and maximum 4 days of raw value data storage and maximum 150 mega-byte database size
For ccr1036
maximum of 160 services and maximum 4 days of raw value data storage and maximum 300 mega-byte database size
Anything beyond that you will have not good results
beyond that you need a separate x86 device to host the dude
for big networks multiple virtualized instances of the dude will be needed, decent ssd storage etc etc
always keep the dude database size under 500mega-byte to keep good performance
Network monitoring IS NOT a light task
is a very intensive one not only in terms of CPU usage but in terms of storage i/o too
NEVER use onboard storage to sotrage the dude database for long term usage, in the case of rb1100ahx4 dude edition always use the 60gb ssd to host it
because monitoring is very write intensive it leads to a premature exhaustion of finite and scarce write cycles of the flash memory
That is really funny, Dude just crashed completely..
ohh yeahThis happened to me three times already too. For the first time I tried to make mikrotik to find a reason and correct it. Unfortunately they were unable to do that. I solved that by importing a dude backup back.
So why we have issues only with monitoring SNMP supporting devices and no issues using RouterOS API? Sure it is a same amount of data.Network monitoring IS NOT a light task