====== Mikrotik Troubleshooting Tips ======

===== Network Architecture =====

Tips to facilitate optimal troubleshooting:

  * Plug other 'links' directly into the Mikrotik CPE device
    * Wireless access points (WAPs)
    * Switches
    * Bridges to other buildings or networks
  * Keep a diagram showing which port goes where
  * Name the ports appropriately

===== Find Bandwidth Hogs =====

  - Use the ''Interfaces'' list to see the big picture
    - Is their upstream Internet or Metro Ethernet connection saturated?
    - Is a bridge to another building hogging the bandwidth?
    - Is their wireless access point (WAP) hogging the bandwidth?
      - Many problems are due to multimedia streaming with wireless devices
  - Use the Mikrotik ''IP Accounting'' feature to see which IP addresses are involved
    - RouterOS v6 only
  - Use the Kid Control feature to see which IP addresses are involved
    - RouterOS v7  only
  - Check the DHCP server ''Leases'' to look for host name clues

<note>The IPv4-only Accounting feature was removed in RouterOS v7.</note>

<note important>In a bridged environment, such as Metro Ethernet, the CPE device (bridge) may not see the traffic in ''IP Accounting''.

Try using the upstream router ''IP Accounting'' feature and filter by the client IP address range.

Or, enable ''use-ip-firewall=yes'' in the bridge settings.</note>

{{ :networking:router:ip_accounting_filtered.png?direct&750 |IP Accounting Snapshot Filtered by IP Range}}

{{ :networking:router:dhcp_server_leases.png?direct&750 |DHCP Server Leases with Host Name Clues}}