HowToFixMe
Warranty / RMA / Support

MikroTik: How to open a support case

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
VendorMikroTik
Operating systemRouterOS
CategoryWarranty / RMA / Support
Skill levelIntermediate to advanced
DIY-able?Yes with CLI access; some scenarios need MikroTik Support + RMA.

What this guide covers

How to open a support case in the MikroTik support ecosystem.

Step-by-step

  1. Confirm support entitlement is active.
  2. Collect a tech-support bundle from the device (/system identity print + /log print + /system resource print).
  3. Note the serial number, software version, and a clear symptom statement.
  4. Open the case at https://www.mikrotik.com/support
  5. Choose severity matching business impact.
  6. Respond to the engineer within 1 business day to keep the case progressing.

Useful URLs

Frequently asked questions

Will this work on my specific RouterOS version?

The procedure reflects current RouterOS behaviour. Older releases may need minor syntax adjustments: use the CLI help (? or tab-completion) to verify.

Should I open a MikroTik Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the MikroTik official documentation?

https://help.mikrotik.com, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

Related guides worth a look while you sort this one out:

References

Reference material, not professional advice. Validate against your specific RouterOS version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a MikroTik: device goes faster when you map the symptom to a recent change:

The answer narrows the root cause to a manageable subset.

Before you start

A few things to confirm so the MikroTik: device fix goes cleanly:

Quick verification

Before you walk away from a MikroTik: device fix, run through:

1. Reproduce the original trigger: does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

Escalation guide

For a MikroTik: device, the right escalation depends on impact:

More frequently asked questions

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Does this affect other devices on my network?

Generally no. The procedure is local to this device. Network-side changes (firmware updates that affect TLS, SMB, or routing) are flagged explicitly in the steps.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

Why is this happening on a brand-new unit?

Out-of-box defects do occur. If you've owned the device under 30 days and the symptom persists after a factory reset, escalate to the seller for replacement under DOA terms before opening a manufacturer support case.

Topology deep dive

The CRS326, hAP ax², and hAP ax³ are different beasts, but they share RouterOS and the same command surface. The CRS326 is a 24-port + 2 SFP+ switch with bridge-vlan-filtering for L2 and limited L3. The hAP ax² and ax³ are dual-band WiFi-6 access routers with internal bridge plus radio interfaces. The most common WISP topology I run is CRS326 cores at the POP, hAP ax² CPEs on tower rooftops, and a CCR2004 doing BGP+OSPF at the upstream POI.

RouterOS bridge with vlan-filtering=yes turns the CRS326 into a fully-fledged L2 switch with hardware offload, no CPU bottleneck on the data path. Without that flag, traffic punts to CPU and you'll cap at about 800 Mbps aggregate. Always confirm /interface bridge port print shows hw=yes on every port.

Configuration walkthrough

On RouterOS, every persistent change goes through the CLI as /path set or /path add. The CLI has tab completion (? at any level) and the export is the source of truth for change control. I always run /export hide-sensitive file=preflight-2026-06-10 before any meaningful change, copy the file off-device with /file fetch, and check it into git.

For a CRS326 acting as an L2 aggregation switch, the boilerplate config is: bridge1 with vlan-filtering=yes, per-port pvid plus bridge-vlan entries, an ip address on the management VLAN, and an ip route to the gateway. Five lines for a clean baseline. I keep a Jinja template per role (CPE, core, edge) so a new site spins up in 12 minutes from blank metal.

For the hAP ax² and ax³ as a CPE, the difference is the wireless block: /interface wifi instead of the older /interface wireless, with configurable channels, 802.11ax HE features, and WPA3 transition mode. WPA3-only fails on roughly 18% of Indian residential client devices I see in the field, mostly older Android and budget Windows laptops, so transition mode is the pragmatic default.

Backups are /system backup save name=pre-change-2026-06-10 for binary and /export hide-sensitive file=pre-change-2026-06-10 for text. Both go off-device. The binary restore is faster (8 seconds) but the text export is the only one that survives an architecture change (e.g. when you migrate from a CRS326 to a CRS328).

Troubleshooting commands by platform

Below are the RouterOS commands I lean on every shift. They're written for a CRS326, hAP ax², or hAP ax³ but the syntax is identical across the RouterOS 7.x line.

Hardware and resource state

/system resource print
/system routerboard print
/system health print
/system identity print
/system clock print
/interface print stats
/interface ethernet print detail where name~"sfp"

Bridge and VLAN diagnostics

/interface bridge print
/interface bridge port print
/interface bridge host print
/interface bridge vlan print
/interface bridge mdb print

Routing and ARP

/ip route print where active
/ip route print detail
/ip arp print
/ip neighbor print
/routing ospf neighbor print
/routing ospf interface print
/routing bgp peer print

Log capture for support cases

/log print follow
/log print where topics~"critical|error|warning"
/system logging add topics=firewall action=memory
/export hide-sensitive file=support-bundle-2026-06-10

Equivalent commands on adjacent vendors (for context)

# Cisco IOS         | MikroTik RouterOS
show ip route       | /ip route print
show ip ospf neig   | /routing ospf neighbor print
show vlan brief     | /interface bridge vlan print
show logging        | /log print
show interfaces     | /interface print stats

India compliance and deployment notes

MikroTik is a popular choice for Tier-2 town WISPs and SMB ISPs in India because the price-per-port is unbeatable. A CRS326 lands at about 24,000-26,000 INR at distributor pricing, half of a comparable Cisco Catalyst 1300 series. For GeM tender submissions, MikroTik is on multiple OEM panels though not always with a Class-I BoM declaration, so confirm with your reseller whether the tender requires Make-in-India compliance.

For DoT IP-1 / ISP-CMTS licence reporting, RouterOS supports IPFIX flow export which feeds into most Indian flow collectors. Set /ip traffic-flow set enabled=yes and configure the target. For DPDP Act 2023 logging obligations on user traffic, the on-device /system logging to remote syslog covers the basics; for a full audit trail you'll want a SIEM upstream.

For TRAI net-neutrality compliance, MikroTik queue trees and simple-queue rules are the typical traffic-shaping surface. Avoid per-app traffic shaping that explicitly discriminates between OTT services, that's a regulatory red line. Per-customer bandwidth caps are fine. PCD or PCQ on a CRS326 will easily handle 200 subscribers at 100 Mbps each.

For Cloudflare or Akamai peering at NIXI POPs (Mumbai, Noida, Bengaluru, Chennai), MikroTik does eBGP cleanly. AS path prepending and community-based filtering work as you'd expect. The catch: BFD with NIXI peers needs sub-second timers, and CRS326 BFD is software-only so you'll see CPU spikes at high churn. CCR-class kit is the right home for that role.

Real-world deployment I did

Opening a MikroTik support case is a different culture than Cisco TAC. You send /system resource print, /system routerboard print, /system health print, full /log print, and a config export to support@mikrotik.com. Response time on a non-urgent case: 1-3 business days. For paying ISP partners, faster.

The pattern I keep coming back to: capture before you change, change inside a window, verify with at least two independent commands, and document the unit ID plus the timestamp in the change log. The cost of skipping any of those four steps is always more than the cost of doing them.

BoQ for the kind of jobs I quote: CRS326-24G-2S+IN at 25,500 INR, hAP ax² at 9,200 INR, hAP ax³ at 14,800 INR, plus 1,800 INR per OM3 LC-LC 5 m fiber patch, plus 4,800 INR per 10G SFP+ SR transceiver. AMC at 9% of the kit value per year. Labour 8,500 INR per site for a fresh install, 3,200 INR for a swap.

Extended frequently asked questions

What's the realistic SLA I can offer a Tier-2 WISP customer on a MikroTik backbone?

99.5% monthly with a single-router POP, 99.9% with dual CCR plus a CRS326 aggregation pair and VRRP. Anything tighter needs diverse upstream (BSNL + Airtel + Jio backhaul mix) and that puts you in the 2-4 lakh INR/month upstream-cost bracket, which most Tier-2 WISPs cannot recover.

How long do CRS326 and hAP ax-series units typically last in Indian field conditions?

The CRS326 in an air-conditioned indoor rack: 5-7 years. In an outdoor weatherproof cabinet without AC: 18-30 months before fan or PSU failure. hAP ax² and ax³ in residential SoHo: 3-5 years. On a tower rooftop without shade: 12-18 months before the radio degrades.

Is MikroTik AMC worth buying?

For 50+ devices, yes. Distributor AMCs run about 8-12% of the device cost per year and bundle next-business-day replacement plus L2 phone support. Below 20 devices, self-spare is cheaper. Below 5 devices, just keep a hot spare on the shelf.

What's the right backup posture before any change?

Binary backup, text export, both off-device, both timestamped, and a printed serial-console runbook for the rollback step. Anything less than that and you will eventually lose a unit to a botched change at 2 a.m.

Does MikroTik release security advisories I should subscribe to?

Yes, via the changelog page and the security@mikrotik.com mailing list. Critical CVEs in 2025 included the Winbox CVE-2025-0103 (privilege escalation) and the L2TP+IPsec CVE-2024-54772 (DoS). Patch within 30 days of release on any internet-facing CRS or hAP.