CloudLabBox
Try the free demo

MikroTik MTCNA lab 16 of 19

Monitoring and troubleshooting tools

Use RouterOS's own toolbox on a router that is misbehaving: ping and traceroute with options, interface statistics, Torch to find a mystery traffic source, the profiler, the packet sniffer, netwatch, remote syslog, SNMP and a support file.

Run this lab

It needs Lite: its 4 nodes are set to 4 vCPU and 2,048 MB in total. That fits the free demo too.

In your workspace: Shared, then MikroTik MTCNA RouterOS v7 guided labs, then 16 - Monitoring and troubleshooting tools

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
4 vCPU, 2,048 MB
Smallest plan
Lite

The scenario

A veterinary surgery says its Internet "goes slow every few seconds". Fernvale manages the router (GW) and has a small monitoring server (NMS, Linux) on the office LAN. Your job: find out what is eating the line with RouterOS's own tools, stop it, and leave the router properly monitored: netwatch on the important hosts, logs on the NMS, SNMP for the graphs, and a support file ready if MikroTik needs one.

DeviceInterfaceAddress
GWether1 (WAN) · ether2 (LAN)203.0.113.2/30 · 192.168.88.1/24
ISPether1 · internet loopback203.0.113.1/30 · 198.51.100.10 (web), 198.51.100.66
NMSeth0192.168.88.5/24 (syslog receiver)
PC1eth0192.168.88.20/24

What you’ll practise

  • Use ping with size, do-not-fragment and source address, and traceroute
  • Read interface statistics and monitor live traffic
  • Find who is using bandwidth with Torch, and trace it to its cause
  • Capture packets to a file with the sniffer
  • Watch hosts with netwatch and run scripts on state changes
  • Send logs to a syslog server and enable SNMP with a safe community
  • Produce a supout.rif file for MikroTik support

The tasks

  1. Prepare the NMS
  2. Ping and traceroute with options
  3. Look at the interfaces
  4. Find the mystery traffic with Torch
  5. Profile the CPU and capture packets
  6. Watch important hosts with netwatch
  7. Send logs to the NMS
  8. SNMP and graphs
  9. Prepare a support file

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Monitoring and troubleshooting tools4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.ISPGWNMSPC1Office-LANeth0eth0ether2ether1ether1
4 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • ISP ether1 to GW ether1
  • GW ether2 to Office-LAN (network)
  • NMS eth0 to Office-LAN (network)
  • PC1 eth0 to Office-LAN (network)
Nodes in Monitoring and troubleshooting tools, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
ISPMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
GWMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
NMSAlpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder MikroTik MTCNA RouterOS v7 guided labs.

  3. Open 16 - Monitoring and troubleshooting tools and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More MikroTik MTCNA labs

All MikroTik MTCNA labs

Related labs in other courses

CloudLabBox is independent of MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.