Help with Dude

A few more tips:

  • If you enable SNMP on the individual routers, by default it will show CPU/memory for the devices on the map & in general Dude likes to operate with SNMP not RouterOS commands.

  • If you want to monitor devices on each of those routers, it’s often helpful to create a NEW network map on a per-subnet & if desired you can enable discovery of new device on that map, for that particular subnet – this avoid a mega-map with too many item. You can further use a “submap” via the same “+” so you click through to another map, or have a “meta map” that has submap links to all the other maps to get overview of status.

  • Beyond the link, more advanced monitoring is possible the “probes” – that more complex, plenty of examples here: http://forum.mikrotik.com/t/probe-thread/10321/1 – since they haven’t changed much in 10+ years, likely most still work if you have other device types to monitor BUT complex…

  • If you want to customize the device labels to show your own things… See my post about LTE tracking here: http://forum.mikrotik.com/t/how-to-track-lte-signal-using-the-dude/163250/1

  • It is also a syslog server, so you can always use it as remote log destination – they don’t have a lot of tools to mange them, but possible – e.g. helpful for error/warn from things, but NOT for sending MBs/GBs of logs and excepting it to be useful to search/manage/etc.


    Two big gotcha however…

  • once you add a device to a map it’s stuck there forever – you have to recreate the device on a new map if you want to “move it”. This loses all the tracked data – so critical to design your maps right FIRST and get it right. Adapting later results in lost of historical data, and you can’t even cut-and-paste the devices, so you’re re-creating them.

  • Also no CLI to manage the devices means you either add them by hand, or relay on the “discovery” feature of a map to add devices – so limits the usefulness in some larger installs.