CIRCUITO
CARIOCA TI · DOCUMENTATION
♙
ROUTEROS V7 · NOC · FIELD · ROUTING · SWITCHING

Troubleshooting MikroTik

Operational center for CCR, CRS, RB and modern RouterOS v7 Wi-Fi: routing, switching, bridge/VLAN, hardware offload, optics, firewall, CPU and CAPsMAN.

mikrotik://diagnostics
$ scope: CCR · CRS · RB · Wi-Fi
$ os: RouterOS v7
$ rule: hardware != software
$ safety: read first_
Critical rule: A common RouterOS ecosystem does not mean a common dataplane. Validate model, switch chip, hardware offload and device-mode before changing configuration.
01 · COMMAND LIBRARY

RouterOS v7

Prefer read-only commands first. Torch and sniffer should be short-lived in production.

System

/system/resource/print

CPU, memory, uptime and platform

System

/system/device-mode/print

Device mode, restrictions and flagged state

Interfaces

/interface/print stats-detail

Counters, link-downs and detailed interface state

Ethernet / Optics

/interface/ethernet/monitor <porta> once

Link, rate, negotiation, FEC and transceiver diagnostics

Bridge

/interface/bridge/port/print detail

Bridge ports, PVID and hardware offload

VLAN

/interface/bridge/vlan/print detail

Tagged/untagged VLAN membership

Routing

/ip/route/print detail

Active routes, gateways and route origin

BGP

/routing/bgp/session/print detail

BGP session state in RouterOS v7

OSPF

/routing/ospf/neighbor/print detail

OSPF neighbors and adjacency state

Diagnostics

/tool/ping <destino> count=10

Reachability and RTT

Diagnostics

/tool/traceroute <destino>

Hop-by-hop path

Traffic

/tool/torch interface=<porta>

Short real-time traffic analysis; may affect FastPath

Capture

/tool/sniffer/quick interface=<porta>

Packet capture; device-mode may restrict it

Performance

/tool/profile

CPU consumption by process/task

Wi-Fi

/interface/wifi/registration-table/print

Associated clients and radio state

Change

/export file=pre-change

Text export before a change

Change

/system/backup/save name=pre-change

Binary backup; protect as sensitive data

02 · PLAYBOOKS

Troubleshooting by symptom

No Internet / no route

  1. Check interface and IP address.
  2. Inspect /ip/route/print detail.
  3. Ping the next hop, then the destination.
  4. Run traceroute.
  5. Check firewall, NAT and VRF.
  6. Check BGP/OSPF when routing is dynamic.

BGP down or flapping

  1. Validate reachability and TCP/179.
  2. Inspect BGP session and connection details.
  3. Confirm ASN, VRF, TTL and template.
  4. Correlate logs, CPU and interface state.
  5. Analyze filters only after session establishment.

VLAN without traffic

  1. Check bridge ports and PVID.
  2. Inspect bridge VLAN table.
  3. Inspect MAC learning.
  4. Validate CPU/bridge membership.
  5. Check ingress filtering and frame types.
  6. Confirm hardware offload.

CRS low throughput

  1. Confirm hardware offload.
  2. Check switch chip and block diagram.
  3. Inspect counters and CPU.
  4. Review firewall, queues and bridge filters.
  5. Stop unnecessary Torch/sniffer sessions.
  6. Validate L3HW when applicable.

Wi-Fi client issue

  1. Inspect /interface/wifi.
  2. Check security and authentication.
  3. Check registration table.
  4. Review Wi-Fi/RADIUS logs.
  5. Validate country and channel.
  6. Separate RF from authentication.
03 · OPERATIONAL NOTES

What changes diagnosis

Hardware Offload

CRS forwarding can move between switch chip and CPU depending on model and configuration.

Device-mode

RouterOS v7.17+ may restrict sniffer and other tools; flagged state requires security review.

Wi-Fi

Do not confuse modern /interface/wifi with legacy /interface/wireless. Frequency scan can disconnect clients.

OFFICIAL DOCUMENTATION

RouterOS Manual

Open manual ↗