Chapter 9 of 9 · MikroTik MTCNA

Misc

Troubleshooting tools, monitoring with Torch, graphs, SNMP and The Dude, and how to prepare a support request.

  • 3topics
  • 15 minfast track

Topics in this chapter

Take them in order, or jump to the one you need.

  1. 1RouterOS Tools, E-mail, Netwatch, Ping, Traceroute and ProfilerUse the RouterOS tools menu for troubleshooting and alerts: e-mail, Netwatch host monitoring, ping, traceroute and the profiler…5 min
  2. 2Monitoring with Traffic Monitor, Torch, Graphs, SNMP and The DudeWatch a RouterOS network with the interface traffic monitor, Torch, graphs, SNMP and The Dude, and learn what each tool shows and…5 min
  3. 3Contacting MikroTik Support with supout.rif and LogsPrepare a good support request to MikroTik support, with a supout.rif file, an autosupout.rif, debug logs, a readable…5 min

About this chapter

What this chapter covers

Misc gathers the tools that you use when a network is running, and something needs to be tested, watched or reported.

It covers the tools menu, with ping, traceroute, Netwatch, e-mail and the profiler. It then covers monitoring, from live views to history and network wide tools. The last page explains how to contact MikroTik support with the evidence that makes a request easy to handle.

How the topics fit together

The three pages follow the path of a real problem.

Toolsping, traceroute, NetwatchthenMonitoringTorch, graphs, SNMPthenSupportsupout.rif, logs, diagram

First you test. Ping and traceroute tell you whether something is reachable and where the path stops. Netwatch and e-mail turn those checks into alerts, and the profiler shows what loads the CPU.

Next you watch. The traffic monitor and Torch show the present, and graphs, SNMP and The Dude keep the history and cover many devices.

If you cannot solve the problem yourself, you ask for help. A support output file, debug logs, a readable export and a network diagram give support what it needs.

The ideas to carry between the pages are these:

  • Choose the tool by the question you are asking.
  • Live tools keep no history, and graphs and SNMP do.
  • Enable debug logs only while testing.
  • Send a text export, never only a binary backup, to support.
Note

The tools in this chapter observe and report, and they do not change how traffic is forwarded unless you attach a script to them, for example to Netwatch.

How to use these pages

Each topic page has the same shape, so you can skim for what you need.

  • What it is: the idea in plain words.
  • How it works: the mechanism, with diagrams and console examples.
  • What to remember for the exam: the facts to memorise.
  • Common mistakes: the classic traps.
  • Check yourself: three questions to test your understanding.

Run each command on a lab router and read the output. Create a supout.rif file and look through its contents, so that you know what support will see.

Ready for more practice?

The full MikroTik MTCNA question bank has 558 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by MikroTik. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.