MikroTik SXT 5 ac & DynaDish 5 Discontinued Replacement Guide
MikroTik SXT 5 ac / DynaDish 5 Replacement Guide: Item-by-Item Spec Comparisons, Six Decision Dimensions and a Migration Plan You Can Actually Run
At a Glance
Who this is for: ISP and private-network engineers running MikroTik 5 GHz outdoor links who are now looking for replacements for the SXT 5 ac or DynaDish 5 — or who are simply budgeting spares for next year.
Where things stand in one sentence: MikroTik has moved the SXT 5 ac and DynaDish 5 into its Discontinued category, the SXT Lite5 is end of life, and the Disc Lite5 product page is gone (404) — and the vendor names no replacement model and gives no reason for any of it.
What this guide gives you: item-by-item spec comparisons between the four discontinued devices and the LigoDLB 5ac line (gain, beamwidth, transmit power, receive sensitivity, power, ingress rating, dimensions and weight, list price — all laid out), six decision dimensions that sit outside the spec sheet, an FSPL link-budget method you can copy straight into a spreadsheet, and a six-phase migration process from inventory to closeout. The hand-off path to MikroTik’s current models (SXTsq, LHG, NetMetal) is set out just as plainly — staying inside the MikroTik ecosystem is a legitimate choice, and this article is here to help you price the costs and constraints of both routes.
Where Things Stand: Four Mainstays Withdrawn, No Replacement Guidance
The SXT and DynaDish families are the two highest-volume categories in MikroTik 5 GHz outdoor deployments: the SXT line handles short- to medium-range CPE and point-to-point work, while the DynaDish 5’s integrated 25 dBi dish covers the long-haul end. Both product lines have changed status officially — the SXT 5 ac and DynaDish 5 pages now sit under Wireless systems / Discontinued, the SXT Lite5 is likewise marked as discontinued, and the Disc Lite5 has been removed from the site altogether, returning a 404.
For the operator, “Discontinued” does not mean the hardware stops tomorrow. It means three much more concrete things (the same pattern applies to the Ubiquiti and Cambium retirements covered in the 5 GHz end-of-life replacement guide):
- The new-purchase channel is closed. You can no longer restock the original model through authorised distribution. Expansion and failed-unit replacement now come down to burning off channel inventory or turning to the secondhand market.
- The hidden cost of secondhand spares. Batch, firmware revision and RF ageing on a used SXT are all unknown. We have seen plenty of cases where a link produces worse numbers after the swap than the original design predicted — the budget was run against a new device, and what went up the tower was a three-year-old unit that had been running hot.
- Software lifecycle carries no promise. RouterOS downloads are still available for discontinued hardware, but there is no long-term guarantee of software support at the tail end of a hardware lifecycle, and the continuity of security patches has to be treated as an open question.
One thing should be made clear: MikroTik still sells 5 GHz outdoor models (SXTsq, LHG, NetMetal, BaseBox and others). In other words, what has been retired is the value-favourite classics, not the entire 5 GHz line. That leaves a real problem — the models still on sale no longer map cleanly onto the discontinued ones in either price or form factor, so working out a model-by-model substitution becomes the operator’s own job. Everything from section 3 onward is exactly that exercise.
The Discontinued List and the Official Wording
Full specifications of the four discontinued devices
| Model / product code | Official status | Wireless | Antenna | Interface / power | Environment / platform | List price |
|---|---|---|---|---|---|---|
| SXT 5 ac RBSXTG-5HPacDr2 |
Discontinued | 5 GHz · 802.11a/n/ac · 2×2 MIMO 867 Mbps peak |
16 dBi / 28° beamwidth | Gigabit port 802.3af/at, 15–60 V (24 V included) 12 W |
-40 to +70 °C QCA9557 720 MHz 128 MB RAM |
$109 |
| DynaDish 5 RBDynaDishG-5HacDr3 |
Discontinued | 5 GHz · 802.11a/n/ac · 2×2 867 Mbps peak |
25 dBi integrated dish Ø404 × 175 mm |
Gigabit port 802.3af/at, 11–60 V 9 W |
IP54 | $199 |
| SXT Lite5 RBSXT5nDr2 |
Discontinued | 5 GHz · 802.11a/n (no ac) | 16 dBi / 28° beamwidth | Fast Ethernet port passive PoE 8–30 V 6 W |
— | $49 |
| Disc Lite5 RBDisc5 |
Product page withdrawn (404) | 5 GHz · 802.11a/n | 21 dBi / 12° beamwidth | Fast Ethernet port passive PoE 11–30 V 6 W |
— | $48 |
What the vendor says — and what it does not
On the product pages, MikroTik’s only statement is the single word “Discontinued.” There is no reason given and no successor named (the RELATED PRODUCTS block is empty or has nothing of substance in it). Just two passages can be quoted verbatim from those pages, both on the SXT 5 AC page:
The first passage is a software-update commitment that applies during the sales window. The second matters a great deal for migration planning: MikroTik confirms officially that its 802.11ac products are backwards compatible with legacy 802.11an gear. Combined with the fact that both ends can fall back to standard 802.11 mode, this gives large networks an official basis for a staged replacement (how that works and what it requires is covered in Phase 4 of section 9).
Following this guide’s editorial rule: since the vendor states no reason for discontinuation, no reason is speculated here. Since the vendor names no replacement, the mapping table below is an engineering judgement made by LigoWave from publicly available specifications, and every basis for that judgement can be checked.
Master Replacement Mapping
| Discontinued MikroTik model | Recommended LigoWave model | Substitution class | Basis for the call |
|---|---|---|---|
| SXT 5 ac (16 dBi / 28° / 867 Mbps / gigabit) | LigoDLB 5-15ac | ✅ Direct replacement | 1 dB gain difference, 28° → 35° beamwidth (more alignment tolerance), both 802.11ac 2×2 with gigabit ports; link budget essentially unchanged |
| SXT Lite5 (16 dBi / 802.11a/n / Fast Ethernet) | LigoDLB 5-15ac | ✅ Direct replacement (upgrade) | 1 dB gain difference; 802.11a/n with Fast Ethernet becomes 802.11ac with gigabit and 500+ Mbps throughput |
| Disc Lite5 (21 dBi / 12° / Fast Ethernet) | LigoDLB 5-20ac | ✅ Direct replacement (upgrade) | 1 dB gain difference, 12° → 16° beamwidth; Fast Ethernet upgraded to gigabit |
| DynaDish 5 (25 dBi dish / 867 Mbps / gigabit) | LigoDLB 5-20ac (links ≤8 km) | ⚠️ Partial replacement | 5 dB gain difference; a direct swap at short and medium range. The 16° narrow beam plus iPoll 3 holds up better under interference |
| LigoDLB 5ac + 25 dBi or larger dish (links >8 km) | ✅ Direct replacement | Connectorised model with an external dish, preserving the original link margin; the existing dish can be reused | |
| Base-station side (originally SXT SA5 ac at 14 dBi / 90°, or NetMetal with a sector) | LigoDLB 5-90AC (18 dBi / 90° / 20° elevation) | ⚠️ Partial replacement | 4 dB more gain; an all-in-one 90° sector, with no separate antenna to source |
How the classes are defined. Direct replacement = same form factor, gain difference ≤2 dB, same interface tier, existing power can be reused, link budget and coverage essentially unchanged, no site survey needed. Partial replacement = one factor needs to be re-checked (a gain difference of 3–5 dB, or a change in beam shape), and the link budget in section 6 must be run before anything is ordered.
Spec Comparison, Item by Item
4.1 SXT 5 ac vs LigoDLB 5-15ac — the main CPE, head to head
| Specification | MikroTik SXT 5 ac (discontinued) | LigoWave LigoDLB 5-15ac |
|---|---|---|
| Band / standard | 5 GHz (international 5150–5875 MHz) / 802.11a/n/ac, 2×2 MIMO | 5 GHz / 802.11a/n/ac, 2×2 MIMO |
| Channel width | 20 / 40 / 80 MHz | 5 / 10 / 20 / 40 / 80 MHz |
| Peak data rate | 867 Mbps (MCS9 / 80 MHz) | 866 Mbps (80 MHz rate), 500+ Mbps throughput claimed |
| Antenna gain | 16 dBi | 15 dBi |
| Beamwidth (3 dB) | 28° | 35° / 35° / 35° |
| Transmit power | MCS0: 30 dBm; MCS7: 27 dBm; 802.11a 6 Mbps: 31 dBm | ≤30 dBm; 24–29 dBm at 80 MHz |
| Receive sensitivity | MCS0: -96 dBm; MCS7: -77 dBm; MCS9: -72 dBm | -90 to -64 dBm (full rate range at 80 MHz) |
| Ethernet | 1× 10/100/1000 | 1× 10/100/1000 |
| Power | 802.3af/at, 15–60 V (24 V passive included) | 24 V passive PoE |
| Max power draw | 12 W | 10 W |
| Hardware platform | QCA9557 720 MHz / 128 MB RAM | QCA9563 750 MHz / 64 MB RAM / 16 MB flash |
| Operating temperature | -40 to +70 °C | -40 to +65 °C |
| Ingress rating | Not stated by vendor | IP-65 (non-metallic enclosure) |
| Dimensions / weight | Not listed on the vendor page | 158×97×38 mm / 185 g |
| Wireless protocol | 802.11 / NV2 / Nstreme (proprietary TDMA) | iPoll 3 (proprietary TDMA) |
| Vendor coverage guidance | None given | PtMP 5 km / PtP 7 km |
| Device positioning | Full RouterOS routing platform | Wireless bridge (link transport is the core job) |
Five rows in this table deserve a closer look:
① Two extra channel widths, 5 and 10 MHz. These are not decoration. In interference-dense urban areas, or at sites that need to squeeze more use out of one frequency, narrow 5/10 MHz channels are a genuinely usable anti-interference tool — and the SXT 5 ac cannot do it.
② Beamwidth, 28° → 35°. A wider beam buys you alignment tolerance, so signal variation from wind deflection or slight tower movement is smaller. The trade-off is a little less directivity and slightly weaker rejection of interference from neighbouring sites. For CPE work, that is usually a trade worth making.
③ Top temperature, 70 → 65 °C. Irrelevant in most climates, but worth noting if the unit sits in a sealed cabinet or at the top of a tower in a hot region.
④ Memory, 128 MB → 64 MB. The SXT 5 ac runs RouterOS, a full routing platform; the LigoDLB is positioned as a bridge, so its firmware surface is narrower and its memory needs are lower. If your site uses the SXT as a router (NAT, DHCP, VPN, complex queues), settle this during migration design — either move that function up to the aggregation layer or keep one MikroTik on site to do the routing.
⑤ Power. The SXT 5 ac accepts 15–60 V, 24 V passive included — so on sites already fed by a 24 V injector, moving to the LigoDLB means the injector and cabling carry straight over, with no modification at all. Where power comes centrally from an 802.3af switch, you need to insert a 24 V passive injector on the device side (a cheap change, but one that belongs on the bill of materials).
4.2 DynaDish 5 vs LigoDLB 5-20ac — the 5 dB question on long links
| Specification | MikroTik DynaDish 5 (discontinued) | LigoWave LigoDLB 5-20ac |
|---|---|---|
| Antenna type | Integrated dish, Ø404 × 175 mm | Integrated dual-polarised directional panel |
| Antenna gain | 25 dBi | 20 dBi |
| Beamwidth (3 dB) | Not stated by vendor (dish, highly directional) | 16° / 16° / 16° |
| Band / standard | 5 GHz / 802.11a/n/ac, 2×2, 867 Mbps | 5 GHz / 802.11a/n/ac, 2×2, 500+ Mbps throughput |
| Channel width | 20 / 40 / 80 MHz | 5 / 10 / 20 / 40 / 80 MHz |
| Transmit power | On par with the SXT 5 ac when 802.3af/at powered | 24–29 dBm at 80 MHz, ≤30 dBm |
| Receive sensitivity | Not listed separately | -90 to -64 dBm (80 MHz) |
| Ethernet | 1× 10/100/1000 | 1× 10/100/1000 |
| Power | 802.3af/at, 11–60 V | 24 V passive PoE |
| Power draw | 9 W | 10 W |
| Ingress rating | IP54 | IP-65 |
| Dimensions / weight | Ø404 × 175 mm | 205×205×45 mm / 700 g |
| Vendor coverage guidance | None given | PtMP 10 km / PtP 15 km |
The 5 dB gain difference is the one real weakness in this table, and it splits into two cases:
① Original link ≤8 km: go straight to the LigoDLB 5-20ac. By the free-space rule of thumb (halving distance per 6 dB), a 5 dB shortfall would cut the zero-margin limit to roughly 56% of the original distance — but real links carry margin, so plan on a usable-distance reduction of about 20–25%. Links inside 8 km generally have enough margin to absorb that, and the interference rejection from the 16° narrow beam tends to make the link steadier rather than worse.
② Original link >8 km, or a region with heavy rain fade: move to a LigoDLB 5ac (connectorised, 2×N) plus a 25 dBi or larger dish. Better still, if the original DynaDish dish is in good condition you can replace only the radio body and reuse the dish — the cheapest path by far on long links. Re-run the section 6 link budget before committing.
Two other differences are worth flagging: the LigoDLB 5-20ac is rated IP-65 against the DynaDish 5’s IP54, so its sealing holds up better in humid or dusty environments; and the vendor publishes coverage guidance for the 5-20ac (PtMP 10 km / PtP 15 km) that you can quote directly in a design document or a tender, whereas DynaDish 5 never had any published coverage guidance at all.
4.3 SXT Lite5 / Disc Lite5 vs LigoDLB — replacing the two Fast Ethernet veterans
| Specification | SXT Lite5 | Disc Lite5 | LigoDLB 5-15ac / 5-20ac |
|---|---|---|---|
| Wireless standard | 802.11a/n | 802.11a/n | 802.11a/n/ac (256-QAM + FEC/LDPC) |
| Antenna gain / beamwidth | 16 dBi / 28° | 21 dBi / 12° | 15 dBi / 35° or 20 dBi / 16° |
| Ethernet | 10/100 (Fast Ethernet) | 10/100 (Fast Ethernet) | 10/100/1000 (gigabit) |
| Claimed throughput | 802.11n class | 802.11n class | 500+ Mbps |
| Channel width | 20/40 MHz | 20/40 MHz | 5/10/20/40/80 MHz |
| Power | passive PoE 8–30 V, 6 W | passive PoE 11–30 V, 6 W | 24 V passive PoE, 10 W |
| List price | $49 | $48 | Channel quote |
These two are the simplest replacement cases in the whole article, because the Fast Ethernet port is itself the bottleneck: 802.11n already saturates a 100 Mbps port, so every future over-the-air upgrade runs into the wall of the wired interface. Moving to the LigoDLB 5ac line solves three problems at once — gigabit port, 802.11ac and 80 MHz — so on the same tower position and the same spectrum you get a clear step up in link capacity. On power, the SXT Lite5 was already passive PoE 8–30 V, so a 24 V injector drops straight in.
On price, to be fair to both sides: the SXT Lite5’s $49 positioning was entry-level, and the LigoDLB 5-15ac is a tier above it in specification, so the two were never priced against each other. If a particular site genuinely needs only a few tens of Mbps and sits in a benign environment, MikroTik’s current entry-level models are worth evaluating too — but note that “buy another 802.11n Fast Ethernet box to save the difference” is a poor investment after 2026. Spectral efficiency, security patches and spares supply are all consolidating around the ac/ax platforms.
4.4 Side by side: MikroTik’s current models vs LigoWave
Staying inside the MikroTik ecosystem is a perfectly legitimate choice, so here are the published specifications of its current models, laid out for a like-for-like comparison of the two routes:
| Model | Official status | Gain / beamwidth | Rate / interface | Power | List price |
|---|---|---|---|---|---|
| MikroTik LHG 5 | On sale | 24.5 dBi | 802.11a/n, 300 Mbps / Fast Ethernet | passive PoE 11–30 V, 6 W | $69 |
| MikroTik LHG 5 ac | On sale | 24.5 dBi | 802.11ac, 867 Mbps / gigabit | passive PoE | ≈$89 |
| MikroTik LHG XL 5 ac | On sale | 27 dBi | 802.11ac, 867 Mbps / gigabit | passive PoE 10–30 V, 8 W | $117 |
| MikroTik SXT SA5 ac | On sale | 14 dBi / 90° | 802.11ac, 867 Mbps / gigabit | 802.3af/at 12–57 V, 12 W | $119 |
| LigoWave LigoDLB 5-15ac | On sale | 15 dBi / 35° | 802.11ac, 500+ Mbps / gigabit | 24 V passive, 10 W | Channel quote |
| LigoWave LigoDLB 5-20ac | On sale | 20 dBi / 16° | 802.11ac, 500+ Mbps / gigabit | 24 V passive, 10 W | Channel quote |
| LigoWave LigoDLB 5-90AC | On sale | 18 dBi / 90° (20° elevation) | 802.11ac, 500+ Mbps / gigabit | 24 V passive, 10 W | Channel quote |
The trade-off between the two routes comes down to this. If your operations team leans heavily on RouterOS routing, firewall and scripting, and you want a single box that also routes, staying with MikroTik is the smoother fit. If the sites are pure wireless access or backhaul (bridge duty), you want centralised bulk management, or you care about a clean 6 GHz evolution path (MikroTik’s 6 GHz models, SXT 6 and BaseBox 6, are also discontinued), then the LigoWave route offers more certainty on lifecycle and operational model. The two are not mutually exclusive — using them side by side within one network, chosen by site type, is a pattern we see in the field.
Six Decision Dimensions Beyond the Spec Sheet
Gain and throughput are only half of a selection decision. In real replacement projects, the six dimensions below often carry as much weight as the RF specifications.
Dimension 1: Wireless protocol and scheduling
If you also run Cambium ePMP gear, note that iPoll 3 is incompatible with Cambium’s own TDMA as well — the protocol question is covered in more depth in the Cambium ePMP 5 GHz replacement guide.
| Item | MikroTik (discontinued models) | LigoWave LigoDLB |
|---|---|---|
| Proprietary TDMA protocol | NV2 / Nstreme | iPoll 3 |
| Scheduling mechanism | NV2: centrally scheduled TDMA | iPoll 3: officially described as “allocating time slots to each client, eliminating collisions and allowing more CPEs to connect simultaneously” |
| Interoperability | Not interoperable — iPoll 3 cannot run alongside NV2 or Nstreme, so a replacement must be done in pairs | |
| Interoperability fallback | Both ends falling back to standard 802.11 mode will interoperate, at the cost of throughput and interference rejection (MikroTik confirms 802.11ac is backwards compatible with 802.11an) | |
This dimension is a draw: NV2 and iPoll 3 are both proprietary TDMA and each is closed to the other. The real difference lies in the ability to transition — MikroTik states its 802.11 backwards compatibility explicitly, which gives a staged approach (“new CPE joins in standard 802.11 mode, the base station switches last”) an official basis. If your network runs NV2 (check it in the wireless settings in Winbox), you have no option but to swap whole links in pairs, so build your schedule around that constraint.
Dimension 2: Power and site-modification cost
| Existing power arrangement | What changes when moving to LigoDLB | Modification cost |
|---|---|---|
| 24 V passive injector (the most common MikroTik outdoor setup) | Nothing at all — injector and Ethernet cable carry straight over | Zero |
| 802.3af/at switch power (SXT 5 ac / DynaDish 5 sites) | Insert a 24 V passive injector on the device side; convert the switch port to plain data | One injector per site plus termination labour |
The SXT 5 ac’s 15–60 V wide-range input is a genuine design strength, and it means most existing MikroTik sites need no power work at all when they move to LigoDLB. One caution during the job: the LigoDLB is a 24 V passive device, so never connect an 802.3af switch’s 48 V output to it directly — the mismatch carries a risk of damage. The correct procedure is to disable PoE on the switch port and feed the device through a 24 V injector.
Dimension 3: Network management and bulk operations
MikroTik’s operating model is logging into each device with Winbox — flexible, but dependent on how fluent your engineers are with RouterOS, and prone to parameter drift when you are replacing dozens of sites in bulk. LigoWave manages centrally through WNMS, so bulk configuration pushes, firmware upgrades and status monitoring all happen in one place. In fairness, the maturity of the RouterOS ecosystem and its community resources are real MikroTik advantages: if your team already has a full set of RouterOS automation scripts, include that honestly when weighing reasons to stay. Conversely, if your team is worn down by editing configuration device by device across dozens of sites, WNMS’s template-driven deployment is a direct reason to switch.
Dimension 4: Lifecycle and supply certainty
Once the SXT 5 ac and DynaDish 5 are discontinued, spare-parts supply narrows to two sources — channel inventory and the secondhand market — and neither gives you any control over batch or condition. The LigoDLB 5ac line, by contrast, is in production and still receiving firmware. There is no tactful way to put this one: for a carrier-grade link, “a guaranteed new unit within two weeks of a failure” is itself part of the availability metric. Before purchasing, estimate your risk exposure as failure rate × lead time, rather than waiting for a failure and then going looking for stock.
Dimension 5: Evolution path (6 GHz)
LigoDLB ac and the LigoDLB 6 series (5.9–6.4 GHz) share the same hardware platform and the same iPoll 3 protocol, so a network can move smoothly from 5 GHz to 6 GHz within one management system. Set that against MikroTik’s 6 GHz position: the SXT 6 (RBSXTG-6HPnD) and BaseBox 6 are both marked Discontinued on the official site, and the SXT 6 is expressly “sold only to licensed spectrum holders.” In other words, in regions where 6 GHz is open or licensed, MikroTik’s current line-up contains no purchasable 6 GHz fixed-wireless device. Since 6 GHz regulation varies by country (5925–7125 MHz is not open for civilian use in mainland China), whether this dimension matters depends on your market — check local rules first.
Dimension 6: Procurement and spare-parts cost structure
The “sticker price” of a discontinued model is meaningless now — the $109 SXT 5 ac and $199 DynaDish 5 were official reference prices before discontinuation, and the real cost today is inventory premium or secondhand discount plus inspection. LigoWave pricing follows channel quotes (no invented numbers here), but there is one certain difference in cost structure: the LigoDLB shares a platform with the LigoDLB 6 and a common WNMS and 24 V power scheme across the range, so spares can be shared between models instead of a separate stock buffer for every SKU. When you build an annual spares budget, the product of “number of SKUs × stock depth per SKU” is what you want to keep small.
How to Calculate the Link Budget
For any replacement where gain differs — the DynaDish 5 at 25 dBi being the obvious case — running the numbers beats guessing. The whole method is four steps, and every input comes from the published specifications already listed above.
Step 1: Work out free-space path loss (FSPL)
Taking 5.8 GHz (f = 5800 MHz), three typical distances:
| Link distance | Calculation | FSPL |
|---|---|---|
| 5 km | 32.44 + 20log₁₀(5) + 20log₁₀(5800) = 32.44 + 14.0 + 75.3 | ≈ 121.7 dB |
| 10 km | 32.44 + 20log₁₀(10) + 75.3 = 32.44 + 20.0 + 75.3 | ≈ 127.7 dB |
| 15 km | 32.44 + 20log₁₀(15) + 75.3 = 32.44 + 23.5 + 75.3 | ≈ 131.2 dB |
Step 2: Work out received signal level (RSL)
Worked example: a 10 km link with LigoDLB 5-20ac at both ends, transmit power taken at the mid-range 25 dBm for 80 MHz, and 1 dB of cable and connector loss:
RSL = 25 + 20 + 20 − 127.7 − 1 = -63.7 dBm. Against the 5-20ac’s sensitivity range at 80 MHz (-90 to -64 dBm), -63.7 dBm sits right on the edge of the top rate (MCS9 needs roughly -64 dBm) — the link will work, but with no fading margin. Good practice is to hold back 10–20 dB for rain fade and Fresnel-zone intrusion, so the sensible move at 10 km is to drop to 40 MHz (about 3 dB better sensitivity) or fit a higher-gain external antenna. That also lines up with the vendor’s published guidance of PtMP 10 km for the 5-20ac.
The same link with DynaDish 5 at both ends (25 dBi, transmit power estimated at the same 25 dBm) gives RSL = 25 + 25 + 25 − 127.7 − 1 = -53.7 dBm, a full 10 dB better than the 5-20ac arrangement. That is what a “5 dB gain difference” actually looks like once it is counted at both ends, and it is why we split DynaDish replacement into two distance bands.
Step 3: Choose the replacement tier from the gain difference
| Gain difference (original → replacement) | Theoretical limit distance change (6 dB halves it) | Planning guidance |
|---|---|---|
| ≤2 dB (e.g. SXT 5 ac → 5-15ac) | ≤12% per dB | Direct swap; margin barely affected |
| 3–5 dB with a link ≤8 km | 5 dB cuts it to about 56% (theoretical limit) | Usually a direct swap; re-check once with the formula above |
| ≥5 dB with a link >8 km, or long range in a wet climate | — | Move to a LigoDLB 5ac plus a 25 dBi or larger dish (existing dish can be reused) |
Step 4: Three checks that often get missed
- Fresnel zone: the first Fresnel zone radius is r = 17.32 × √(d/4f) in metres, with d in km and f in GHz. On a 5.8 GHz / 10 km link the midpoint first Fresnel zone is about 11 m across — confirm that at least 60% of it is clear of obstructions before the swap. Blockage hurts a link more than the antenna gain difference does.
- Rain fade: attenuation rises with frequency, so on long 5 GHz links in wet regions build rain fade into the margin (5–10 dB is a common allowance).
- Regulatory power: a change in the sum of the two antenna gains shifts your EIRP, so after the swap re-check the transmit power setting against the local 5 GHz EIRP ceiling and dial it down in the device if needed.
Deployment Scenarios and Configurations
| Scenario | Typical configuration | Why this combination |
|---|---|---|
| Spare-part replacement at existing SXT 5 ac sites | LigoDLB 5-15ac, one for one | Gain, beamwidth, rate and interface all line up; installation and alignment procedure is unchanged; the 24 V injector carries over |
| Bulk upgrade of an ISP access network | LigoDLB 5-90AC base station + LigoDLB 5-15ac CPE | Rebuild as a “sector + uniform CPE” architecture; iPoll 3 time-slot scheduling reduces hidden-node collisions so one base station carries more CPEs; WNMS handles dozens or hundreds of sites in bulk |
| Campus video backhaul (multi-point aggregation) | LigoDLB 5-90AC + multiple 5-15ac | 5/10 MHz narrow channels squeeze into a crowded spectrum, while QoS (L2 CoS / L3 ToS-DSCP, WRR) protects video priority |
| Short-range high-capacity point-to-point (≤7 km) | 2 × LigoDLB 5-15ac | 500+ Mbps with no dish needed, and a lightweight 185 g install |
| Medium- to long-range point-to-point (7–15 km) | 2 × LigoDLB 5-20ac | 16° narrow beam plus gigabit port covers the mainstream DynaDish 5 distance band (check section 6 first above 8 km) |
| Very long range / wet climates | 2 × LigoDLB 5ac + 25 dBi or larger dish | Preserves the original link margin; a DynaDish dish in good condition can be reused directly |
| Congestion migration where 6 GHz is available | 5 GHz for access + LigoDLB 6 series for backhaul, layered | Same platform and protocol, managed in one WNMS, with backhaul and access separated by frequency |
Strengths and Limitations
Five real strengths
- A generational jump in interface and throughput (for the Lite5 and Disc Lite5): from a Fast Ethernet port and 802.11a/n to a gigabit port and 802.11ac at 500+ Mbps — on the same tower position and the same spectrum, capacity moves up a tier.
- 5/10 MHz narrow channels: the SXT 5 ac starts at 20 MHz, while in interference-dense environments narrow channels are a practical tool you can actually reach for.
- No power work needed (24 V sites): the SXT 5 ac’s wide-range input means the existing injector on site can feed a 24 V passive LigoDLB directly.
- A complete product ladder: 15 dBi wide beam, 20 dBi narrow beam, connectorised models and an all-in-one 90° sector base station — CPE and base station covered from one platform, with no third-party antennas to bolt on.
- A definite 6 GHz evolution path: MikroTik’s 6 GHz models are all discontinued, while the LigoDLB 6 shares platform and protocol with the 5ac, making it a ready-made upgrade route in regions where 6 GHz is available.
Three limitations, stated plainly
① The protocols do not interoperate, so replacements must be done in pairs. iPoll 3 cannot run alongside NV2 or Nstreme. Sites running NV2 have no “replace one end only” option; to stage the work you must either take the whole link back to standard 802.11 mode (sacrificing throughput and interference rejection) or switch in matched batches.
② The LigoDLB is a bridge, not a router. RouterOS’s NAT, DHCP, VPN and scripting capabilities have no equivalent on the LigoDLB. Where a site uses the SXT as a router, that function has to move up to the aggregation layer. This is a difference in product positioning rather than a defect, but it will change your network design.
③ There is no integrated dish above 25 dBi. Long DynaDish 5 links (>8 km) have to go the 5ac plus external antenna route; the integrated option offers no gain advantage in the 25–29 dBi band, and there is no point pretending otherwise.
Migration Plan (Six Phases)
The sequence follows one principle — get the numbers right, validate on a small scale, then go wide — and every phase has defined inputs, outputs and exit criteria. Networks of ten sites or fewer can merge phases two and three; for networks in the hundreds, follow the order strictly.
Export the full register of MikroTik 5 GHz sites, with at least the following fields on every record — leave one out and the budgeting and scheduling that follow get correspondingly more speculative:
| Field | Notes | How to collect it |
|---|---|---|
| Model / product code | e.g. RBSXTG-5HPacDr2 | The register, or the System menu in Winbox |
| Device role | AP side / SM side / one end of a PtP | Network topology diagram |
| Current wireless protocol | NV2 / Nstreme / standard 802.11 | Winbox → Wireless → interface settings |
| Frequency / bandwidth / signal strength | e.g. 5580 MHz / 20 MHz / RSL -62 dBm | Winbox → Registration / Status pages |
| Measured throughput and latency | iperf or a bandwidth test tool; record a baseline | Three runs in the off-peak window, averaged |
| Link distance / azimuth | GPS coordinate difference / compass reading | On site or with a mapping tool |
| Power arrangement | 24 V injector / 802.3af switch, plus cable length | On-site check and injector label |
| IP / VLAN / routing configuration | Whether the site also routes, runs NAT or terminates VPN | Configuration export backup |
| Business criticality | A (core backhaul) / B / C | Agreed with the business owner |
Exit criteria: every link has a complete record, and the two categories that constrain scheduling — “protocol is NV2” and “device also routes” — are flagged separately.
Run the RSL calculation from section 6 for every link:
Exit criteria: every site has a firm replacement model, an antenna plan (reuse or buy) and a power-modification decision (no work or add an injector).
Exit criteria: every unit passes a power-on self-test, its configuration matches the register, and its label maps to exactly one site.
Site selection: one typical A-grade link (SXT 5 ac replaced with a 5-15ac) plus one long link (a DynaDish 5 replacement, to confirm the budget decision was right). Schedule the cutover in an off-peak window and work through the following sequence:
- Record the baseline: signal strength, CCQ, measured throughput and latency of the old link before the change (collected in Phase 1; take one more immediate reading).
- Photograph and mark: capture azimuth, elevation, cable order and label positions on the old unit — installing the new one at the same angles minimises alignment work.
- Out with the old, in with the new: start from the recorded azimuth and elevation, and connect the 24 V injector (always disable PoE on an 802.3af switch port first).
- Align and fine-tune: once it registers, nudge azimuth and elevation in small steps for maximum signal, lock it down, then take one more reading to confirm.
- Validation checklist: wireless registration succeeds; RSL is within 3 dB of the budgeted value; measured throughput ≥ the old link’s baseline (same traffic profile); latency and packet loss no worse; VLAN and service pass-through working; the unit is visible in WNMS.
Rollback plan (mandatory): back up the old unit’s configuration and leave the hardware in place (sealed and labelled after removal). If any checklist item fails during the pilot window and the cause is not identified within 30 minutes, refit the old unit and reschedule for review. The whole point of a pilot is to run into the problems batch rollout would otherwise hit.
Exit criteria: both pilot links run stably for 72 consecutive hours with every checklist item passed, and a standard cutover runbook is documented.
Choose one of two batching strategies depending on the current protocol:
During batch execution, reconcile the whole network’s registration status and alarms in WNMS daily, and update the register (model, date, accepting engineer) as each batch completes.
Exit criteria: every target site switched and stable for two weeks, with no outstanding rollbacks.
Per-site cutover checklist
| # | Check | Pass criterion |
|---|---|---|
| 1 | Power arrangement confirmed | 24 V passive injector in place; PoE disabled on any 802.3af switch port |
| 2 | Mounting attitude | Azimuth and elevation match the markings on the old unit; mast fixing secure |
| 3 | Weatherproofing and earthing | Connectors wrapped and sealed; tower earth lead reliably bonded |
| 4 | Wireless registration | Peer registered, running iPoll 3 (not a standard 802.11 fallback) |
| 5 | Signal level | RSL within 3 dB of the link budget, margin ≥10 dB |
| 6 | Throughput / latency | Measured throughput ≥ the old link’s baseline; latency and loss no worse |
| 7 | Service validation | VLAN pass-through, QoS marking and live traffic all normal |
| 8 | Management enrolment | Visible in WNMS, IP matching the register |
| 9 | Regulatory compliance | Transmit power and EIRP set to the local 5 GHz ceiling |
| 10 | Rollback readiness | Old hardware and configuration backup in place; rollback route documented |
References
- MikroTik product pages (SXT 5 AC / DynaDish 5 / SXT Lite5, marked Discontinued): mikrotik.com
- MikroTik manuals and specification pages for each model (cdn.mikrotik.com)
- LigoWave official data sheets (LigoDLB 5ac / 5-15ac / 5-20ac / 5-90ac, download.ligowave.org): download.ligowave.org
All specifications, official statuses and quoted text in this article were verified on 2026-09-14. Vendor policies can change, so re-check both vendors’ latest pages before a formal publication or tender submission.
Frequently Asked Questions
Q: Why did MikroTik discontinue the SXT 5 ac and DynaDish 5?
Unknown, and the vendor has not said. MikroTik’s product pages carry only the single word “Discontinued” — no reason and no successor (the RELATED PRODUCTS block is empty). Following this article’s editorial rule, no third-party speculation is offered here. What can be confirmed is that the current catalogue still lists 5 GHz outdoor models (SXTsq, LHG, NetMetal and others), so specific classics were retired rather than the whole line.
Q: Can I replace only one end — LigoDLB on the CPE, MikroTik left on the AP?
Not directly; they will not run together. iPoll 3 does not interoperate with NV2, Nstreme, airMAX or ePMP. The only middle ground is taking both ends back to standard 802.11 mode — and since MikroTik confirms 802.11ac is backwards compatible with legacy 802.11an gear, a staged approach (“new CPE joins the old AP in standard 802.11, AP switched last”) does work, provided the network runs standard 802.11 rather than NV2 (check directly in the Wireless settings in Winbox). Link performance drops during the transition, so schedule the AP switch for the off-peak window.
Q: Does power need changing after moving to LigoDLB?
It depends on how power is delivered today. The SXT 5 ac accepts 15–60 V wide-range input (24 V passive included), so sites already fed by a 24 V injector need no changes at all when moving to an LigoDLB (24 V passive PoE) — injector and cable carry over. Where power comes centrally from an 802.3af switch, you need to insert a 24 V passive injector on the device side and disable PoE on the switch port. Note that an 802.3af 48 V feed cannot be connected to the LigoDLB directly; the mismatch risks damage.
Q: The DynaDish 5 is 25 dBi — how much does moving to the 20 dBi 5-20ac cost me?
A total of 5 dB of link budget, counted at both ends. By the rule that 6 dB halves distance, the zero-margin limit distance falls to about 56%, but real links carry margin, so plan on a usable-distance reduction of 20–25%. Links at or under 8 km are usually a straight swap; above 8 km, or in wet regions, go to a LigoDLB 5ac (connectorised) plus a 25 dBi or larger dish, reusing the original DynaDish dish if it is in good condition. Running the FSPL formula from section 6 to calculate RSL first is the safest approach.
Q: Our team relies heavily on RouterOS routing and scripting. Can LigoDLB replace it?
Not directly, and it does not need to. The LigoDLB is a wireless bridge and has no equivalent of RouterOS’s NAT, DHCP, VPN or scripting. Sites like this have two options: move routing up to the aggregation layer, or keep MikroTik on site for routing and replace only the wireless side. Conversely, if your pain point is configuring dozens of sites one Winbox session at a time, WNMS’s template-driven bulk management is exactly the answer. Mixing the two routes by site type is a sound approach.
Q: How much will performance actually improve after the replacement?
Two cases. SXT 5 ac → 5-15ac is a like-for-like swap (867 Mbps against 500+ Mbps throughput, gigabit against gigabit), so the gain is mainly narrow-channel capability and supply certainty. SXT Lite5 / Disc Lite5 → LigoDLB 5ac is a generational step: 802.11a/n to 802.11ac (256-QAM + LDPC), Fast Ethernet to gigabit, throughput up to 500+ Mbps, and two extra channel-width options at 80 MHz and 5/10 MHz. On the same tower position and spectrum, the latter delivers a genuine increase in link capacity.




