Ubiquiti airMAX Legacy & Obsolete 5 GHz Replacement Guide
Reading Ubiquiti’s airMAX “Vintage / Obsolete” Lists: Item-by-Item Comparisons for NS5, Rocket M5 and PowerBeam 5 GHz Gear, and How to Migrate Off Them
At a Glance
Who this is for: ISP, campus and private-network engineers running an installed base of Ubiquiti airMAX 5 GHz links who now have to make replacement decisions for equipment that appears on Ubiquiti’s official “Vintage” or “Obsolete” lists.
Where things stand in one sentence: Ubiquiti splits a large number of airMAX SKUs into two tiers — “Vintage” (will be discontinued, but still purchasable and supported) and “Obsolete” (no feature or security updates, no longer sold through official channels). Its “Suggested Replacement” column names only the product family (airMAX) and not a single replacement model — so picking the right part is your job.
What this guide gives you: a row-by-row audit of the 5 GHz SKUs on the official lists, item-by-item RF comparisons of the NS-5ACL and Rocket M5 + sector antenna against LigoWave equivalents (including gain and elevation detail for each Ubiquiti sector antenna), six decision dimensions that live outside the spec sheet, the FSPL link-budget method, and a six-phase migration plan. Long-range dishes like the PBE-M5-620 (29 dBi) have no like-for-like LigoWave integrated radio — section 6.5 says so plainly rather than talking around it.
The Official Position: How Ubiquiti Defines “Vintage” and “Obsolete”
Ubiquiti’s Help Center article on vintage and obsolete products manages the product lifecycle through a two-tier status model (Cambium ePMP and MikroTik run similar programmes, covered in the 5 GHz end-of-life replacement guide). The definitions, quoted verbatim, are:
The vendor’s broader statement on product retirement, also verbatim: “Ubiquiti is committed to product innovation and providing quality technical support to our customers, which means that sometimes discontinued products will no longer be supported. This page is intended to help customers transition.” The English page adds: “some older products will eventually stop being manufactured and will no longer receive full software updates.” Ubiquiti also commits that “all Ubiquiti products sold will continue to be covered under warranty for the warranty period or as required by law.”
| Official status | What it means officially | What it means in practice |
|---|---|---|
| Vintage | Will be discontinued or is no longer actively developed, but remains purchasable and supported (including critical bug fixes and security updates) | Still supported, but at the tail end of its lifecycle; supply for expansion is uncertain and should be folded into replacement planning |
| Obsolete | No further feature or security updates, no longer officially sold, may be partially or entirely unsupported in future releases | No security patches, no feature fixes; procurement depends on third-party stock; should be scheduled for replacement first |
Two points need to be stated clearly. First, Ubiquiti does not explain why any individual model was retired, and it does not use language like “this entire series has stopped shipping,” so this article offers no speculation about motives — every judgement below rests solely on the two official tiers. Second, “Obsolete” does not mean the hardware stops working tomorrow. The unit will keep forwarding traffic, but it is running unprotected: no security patches, no official repair channel, and when it fails, it fails for good.
The 5 GHz SKUs on the Official Lists, Checked One by One
The table below lists only airMAX-related SKUs that actually appear on Ubiquiti’s official page, together with the status shown there. Anything the vendor does not list is omitted and given no verdict:
| SKU as listed officially | Official status | Band / form factor | Official “Suggested Replacement” |
|---|---|---|---|
| NS5 (NanoStation 5) | Obsolete | 5 GHz integrated CPE | airMAX |
| Loco5 (NanoStation loco 5) | Obsolete | 5 GHz integrated CPE | airMAX |
| NS-5ACL / NS-5ACL-5 | Vintage | 5 GHz AC integrated CPE | airMAX |
| NBE-M5AC-500 / NBE-5AC-16 / NBE-5AC-19 | Vintage | NanoBeam series | airMAX |
| PBM3 / PBM5 / PBM10 / PBM365 | Vintage | PowerBeam series (5 GHz included) | airMAX |
| PBE-M5-620 / PBE-M5-620-FEED | Vintage | 5 GHz 620 mm dish (29 dBi) | airMAX |
| PBE-5AC-300 / -300-ISO / -400 / -500-ISO (and -FEED) | Vintage | 5 GHz AC dish | airMAX |
| RM2-Ti / RM5-Ti / RM5-GPS | Vintage | Rocket M series (5 GHz included) | airMAX |
| R2AC / R5AC-PRISM / R5AC-PTMP / R5AC-PTP / R5AC-PTP-Lite / RM5-AC-PTP-Lite / PS-5AC-45 | Vintage | Rocket AC series | airMAX |
| BM2-Ti / BM5-Ti / BulletM5-HP | Vintage | Bullet M series (5 GHz included) | airMAX |
| airGrid (all models) | Vintage | airGrid series (5 GHz included) | airMAX |
| LBE-5AC-23 / LBE-5AC-16-120 | Vintage | LiteBeam 5 GHz AC | airMAX |
| NB-2G18 / NB-5G22 / NB-5G25 | Vintage | NanoBridge (5 GHz 22/25 dBi included) | airMAX |
| AF-5X | Vintage | airFiber 5 GHz | airFiber |
| NSM3 / others (NS2 / Loco2 / Pico2 / Bullet2 / WSM5 / PicoM2-H / CRM-P / airWire) | Vintage / Obsolete | Other airMAX-related SKUs | airMAX |
Note what the “Suggested Replacement” column really says: against every airMAX SKU, Ubiquiti names only the product family (airMAX / airFiber), with no model-by-model substitution. That differs from the UniFi line, where the guidance points you to a page for choosing a replacement. In short, Ubiquiti provides no per-model replacement guidance for airMAX. That is precisely why this document exists — to lay the specs side by side and work the numbers for you.
Master Replacement Mapping
How the classes are defined. Direct replacement = form factor, interface and gain tier all line up, link budget and coverage essentially unchanged. Partial replacement = the link budget must be re-checked against the original model’s official gain, or an external antenna is required. No equivalent = LigoWave has no matching product tier, and this article says so outright rather than recommending a stretch.
| SKU as officially listed (status) | Recommended LigoWave model | Replacement class | Reasoning |
|---|---|---|---|
| NS5 / Loco5 (Obsolete) | LigoDLB 5-15ac | ✅ Direct (an upgrade) | Both are 5 GHz integrated CPEs; 802.11a → 802.11ac and Fast Ethernet → Gigabit make this a generational step up |
| NS-5ACL / NS-5ACL-5 (Vintage) | LigoDLB 5-15ac | ✅ Direct | Both are 802.11ac integrated CPEs; the NS-5ACL is the NanoStation AC Loco form factor (13 dBi tier), so moving to the 15 dBi 5-15ac is a gain upgrade |
| RM5-Ti / RM5-GPS (Vintage, connectorised Rocket M5) | LigoDLB 5ac | ✅ Direct | Both are 2×N connectorised platforms, so the existing antenna and feed line can be reused; Fast Ethernet → Gigabit, 150+ → 500+ Mbps |
| R5AC-PTP / R5AC-PTP-Lite / RM5-AC-PTP-Lite / R5AC-PRISM (Vintage) | LigoDLB 5ac | ✅ Direct | PtP and connectorised form factors line up |
| R5AC-PTMP / PS-5AC-45 (Vintage, PtMP base station) | LigoDLB 5-90AC | ✅ Direct | 90° sector form factor lines up; the 20° elevation is wider than the airMAX sector antennas (about 4°) |
| BM5-Ti / BulletM5-HP (Vintage, connectorised) | LigoDLB 5ac | ✅ Direct | Both are connectorised platforms, with interface and throughput upgrades |
| PBM5 / PBM10 (Vintage, PowerBeam) | LigoDLB 5-20ac (short/medium range) 5ac + high-gain antenna (long range) |
⚠️ Partial | Re-check link margin against the original model’s gain (PBE-M5-300 is 22 dBi, -400 is 25 dBi, -620 is 29 dBi) |
| PBE-M5-620 (Vintage, 29 dBi dish) | LigoDLB 5ac + external high-gain dish | ⚠️ Partial | LigoWave has no 620 mm-class integrated dish, so the path is “connectorised radio + reuse the original dish” |
| PBE-5AC-300 / -400 / -500-ISO (Vintage, AC dishes) | LigoDLB 5-20ac / 5ac + dish | ⚠️ Partial | Assess against the gain difference of the original dish (see 6.4) |
| airGrid (all models) | LigoDLB 5-20ac / 5ac + high-gain antenna | ⚠️ Partial | airGrid is a high-gain grid-antenna form factor; re-check against the original model’s official gain |
| NB-5G22 / NB-5G25 (Vintage, 22 / 25 dBi) | LigoDLB 5ac + 22–25 dBi antenna | ⚠️ Partial | These were high-gain bridges; LigoWave’s top integrated radio is 20 dBi, so long range needs an external antenna |
| LBE-5AC-16-120 (Vintage, 16 dBi tier) | LigoDLB 5-15ac | ✅ Direct | Gain tiers line up (16 → 15 dBi) |
| LBE-5AC-23 (Vintage, 23 dBi tier) | LigoDLB 5-20ac | ⚠️ Partial | 3 dB gain difference; re-check link margin |
| LBE-M5-23 (not on the official list; specs shown for reference only) | LigoDLB 5-20ac | — | 23 dBi / TX 25 dBm / 4 W; treated as unlisted, with no status judgement made |
| AF-5X (Vintage, airFiber 5 GHz) | — | ❌ No equivalent | airFiber is a dedicated backhaul class; LigoWave has no product at that level, so no recommendation is made |
Spec Comparisons, Item by Item
The tables below do one thing: they place the figures published in Ubiquiti’s official datasheets alongside the figures from LigoWave’s official datasheets. Where neither vendor publishes a number, the table says “see official datasheet” rather than filling the gap on the vendor’s behalf.
6.1 Integrated CPE: NS5 / Loco5 / NS-5ACL vs LigoDLB 5-15ac
| Spec | NS5 / Loco5 (officially Obsolete) | NS-5ACL (officially Vintage) | LigoWave LigoDLB 5-15ac |
|---|---|---|---|
| Wireless standard | 802.11a/n (M generation) | 802.11ac (airMAX ac) | 802.11a/n/ac (iPoll 3) |
| Modulation | 64-QAM | 256-QAM | 256-QAM + FEC/LDPC |
| Antenna / gain | Integrated directional panel (gain per official datasheet) | Integrated directional panel, 13 dBi (Loco form factor) | Integrated dual-polarised directional panel, 15 dBi |
| 3 dB beamwidth | Approx. 45° class (per official datasheet) | 45° horizontal | 35° / 35° / 35° |
| Maximum throughput | Advertised at 150+ Mbps | 450+ Mbps | 500+ Mbps |
| Ethernet port | 10/100 | 1×10/100/1000 | 10/100/1000 |
| Channel width | 5/10/20/40 MHz | 5/10/20/40/80 MHz | 5/10/20/40/80 MHz |
| Transmit power | Per official datasheet | 25 dBm | At 80 MHz: 24–29 dBm |
| Receive sensitivity (80 MHz) | Per official datasheet | Per official datasheet | −64 to −90 dBm |
| Power | 24 V passive PoE | 24 V 0.3 A PoE, 7 W | 24 V passive PoE, 10 W max |
| Wireless protocol | airMAX TDMA | airMAX ac TDMA | iPoll 3 TDMA |
| Official status | Obsolete | Vintage | In production, actively maintained |
6.2 Connectorised: Rocket M5 (RM5-Ti / RM5-GPS) vs LigoDLB 5ac
| Spec | Ubiquiti Rocket M5 (officially Vintage) | LigoWave LigoDLB 5ac |
|---|---|---|
| Form factor / RF chains | Connectorised, 2×N external antenna | Connectorised, 2×N-type external antenna |
| Wireless standard | 802.11a/n (64-QAM) | 802.11a/n/ac (256-QAM + FEC/LDPC) |
| Transmit power | 27 dBm | ≤30 dBm |
| Ethernet port | 10/100 | 10/100/1000 |
| Maximum throughput | 150+ Mbps | 500+ Mbps |
| Channel width | 5/10/20/40 MHz | 5/10/20/40/80 MHz |
| Power | 24 V passive PoE | 24 V passive PoE (identical) |
| Wireless protocol | airMAX TDMA | iPoll 3 TDMA (not interoperable; replace in pairs) |
| Official status | Vintage (will be discontinued, no longer actively developed) | In production, actively maintained |
This is the most straightforward replacement in the airMAX installed base: Rocket M5 units almost always carry an AM-5G series antenna with N-type connectors, so the antenna, feed line and tower position all stay exactly where they are — you unbolt the Rocket M5, bolt on the 5ac, and pick up 3 dB of extra transmit power. The real work is in two places: re-doing the weatherproofing on the N connectors when you swap them, and the protocol — the Rocket M5 runs airMAX TDMA while the 5ac runs iPoll 3, so both ends have to change together. There is no “swap one end” middle ground.
6.3 Base stations / sectors: Rocket M5 + sector antenna vs LigoDLB 5-90AC
Start with Ubiquiti’s own sector antenna figures. The gain and beamwidths of the official airMAX sector antennas (including the azimuth and elevation angles at the 6 dB definition) are below — and this columns bears directly on how coverage changes after replacement:
| Ubiquiti sector antenna | Band | Gain | Azimuth beamwidth (6 dB) | Elevation beamwidth |
|---|---|---|---|---|
| AM-5G16-120 | 5 GHz | 15.0–16.0 dBi | 137° / 118° | 8° |
| AM-5G17-90 | 5 GHz | 16.1–17.1 dBi | 72° / 93° | 8° |
| AM-5G19-120 | 5 GHz | 18.6–19.1 dBi | 123° / 123° | 4° |
| AM-5G20-90 | 5 GHz | 19.4–20.3 dBi | 91° / 85° | 4° |
| Spec | Rocket M5 + AM-5G20-90 | LigoWave LigoDLB 5-90AC |
|---|---|---|
| Form factor | Connectorised radio + external 90° sector antenna (with jumper connectors) | Integrated 90° sector base station (no external jumpers) |
| Gain | 19.4–20.3 dBi | 18 dBi (1–2 dB lower) |
| Azimuth beamwidth | 91° / 85° (6 dB definition) | 90° (3 dB definition) |
| Elevation beamwidth | 4° | 20° |
| Standard / throughput | 802.11a/n, 150+ Mbps | 802.11ac, 500+ Mbps |
| Ethernet port | 10/100 | Gigabit |
| Power | 24 V passive PoE | 24 V passive PoE (identical) |
The other difference is elevation: 4° against 20°. That sounds like LigoWave “covers wider, therefore better,” but do not jump to that conclusion — a narrow 4° elevation concentrates energy for long-range coverage over flat ground, and near-in users below the sector were already being served by sidelobes. Going to 20° elevation clearly helps close-in users with large height differences, while trimming peak gain in the boresight direction. Which one suits you depends on whether your users are “scattered across flat ground 5 km out” or “crowded into a town below the tower.” That is an engineering trade-off, not a case of one being better than the other.
6.4 Dishes / long range: PowerBeam vs LigoDLB 5-20ac or 5ac + external dish
The official PowerBeam M series figures (gain, transmit power, power consumption) are below:
| Ubiquiti PowerBeam (officially Vintage) | Dish | Gain | Transmit power | Consumption | Ethernet port |
|---|---|---|---|---|---|
| PBE-M5-300 | 300 mm | 22 dBi | 26 dBm | 6 W | 10/100 |
| PBE-M5-400 | 400 mm | 25 dBi | 26 dBm | 8 W | 10/100 |
| PBE-M5-620 | 620 mm | 29 dBi | 24 dBm | 8.5 W | 10/100 |
| PBE-5AC-300 (incl. -ISO) | 300 mm | 22 dBi tier | Per official datasheet | — | Gigabit |
| PBE-5AC-400 (incl. -ISO) | 400 mm | 25 dBi tier | Per official datasheet | — | Gigabit |
| PBE-5AC-500-ISO | 500 mm | Higher than the -400 tier (per official datasheet) | Per official datasheet | — | Gigabit |
| Spec | PBE-M5-620 (29 dBi) | LigoWave options |
|---|---|---|
| Antenna / gain | 620 mm dish / 29 dBi | Integrated radio tops out at 20 dBi (5-20ac); or 5ac + external high-gain dish |
| Gain verdict | The integrated radio is 9 dB down, and LigoWave has no gain advantage anywhere in the 25–29 dBi band — stated plainly, not talked around | |
| Recommended path | — | Long range / high gain: 5ac reusing the original dish (feed line retained); short range: 5-20ac |
| Standard / interface | 802.11a/n, 10/100, 150+ Mbps | 5ac: 802.11ac (256-QAM) + Gigabit, 500+ Mbps |
| Power | 24 V passive PoE | 24 V passive PoE (identical) |
6.5 High-gain bridges: NanoBeam / airGrid / NanoBridge
| Ubiquiti model | Official status | Gain | Transmit power | LigoWave equivalent |
|---|---|---|---|---|
| NBE-5AC-16 / NBE-5AC-19 (NanoBeam AC) | Vintage | 16 / 19 dBi tiers | Per official datasheet | 16 dBi tier → 5-15ac; 19 dBi tier → 5-20ac |
| NBE-M5-16 / NBE-M5-19 (NanoBeam M) | Not on the official list; specs shown for reference only | 16 dBi / 19 dBi | 26 dBm | As above (1–3 dB gain difference; re-check) |
| airGrid (all models) | Vintage | Grid antenna; per-model gain per official datasheet | Per official datasheet | 5-20ac or 5ac + high-gain antenna |
| NB-5G22 (NanoBridge 22 dBi) | Vintage | 22 dBi | Per official datasheet | 5ac + 22 dBi antenna (integrated radio tops out at 20 dBi) |
| NB-5G25 (NanoBridge 25 dBi) | Vintage | 25 dBi | Per official datasheet | 5ac + 25 dBi antenna (no integrated equivalent) |
The rule at this tier is simple: at 20 dBi and below, a LigoWave integrated radio can substitute directly; above 20 dBi, you must go connectorised with an external antenna. The NanoBeam and LiteBeam 16 dBi tiers map to the 5-15ac and the 19–23 dBi tiers to the 5-20ac, with 1–3 dB of error either way that a single link-budget pass in section 6.6 will settle. For the airGrid and the 22/25 dBi NanoBridge tiers, the honest answer is that “this is external-antenna work.”
6.6 Platform-level summary: airMAX M generation / AC generation vs LigoDLB 5ac series
| Spec | Ubiquiti airMAX (M generation) | Ubiquiti airMAX (AC generation) | LigoWave LigoDLB 5ac series |
|---|---|---|---|
| Wireless standard | 802.11a/n | 802.11ac | 802.11a/n/ac |
| Modulation | 64-QAM | 256-QAM | 256-QAM + FEC/LDPC |
| Maximum throughput | Advertised at 150+ Mbps | 450+ Mbps | 500+ Mbps |
| Ethernet port | Mostly 10/100 | Gigabit | 10/100/1000 |
| Channel width | 5/10/20/40 MHz | 5/10/20/40/80 MHz | 5/10/20/40/80 MHz (plus 5/10 MHz narrow channels) |
| Power | 24 V passive PoE | 24 V passive PoE | 24 V passive PoE (identical; injectors can be reused) |
| Antenna form factors covered | Integrated panel / grid / dish / connectorised | Integrated / dish / connectorised | Integrated 15 dBi and 20 dBi panels; 18 dBi sector; connectorised (no 25–29 dBi integrated dish) |
| Wireless protocol | airMAX TDMA | airMAX ac TDMA | iPoll 3 TDMA (all proprietary; replace in pairs) |
| Centralised management | UISP | WNMS | |
| Basis for selection | Official “Suggested Replacement” names only the airMAX family, with no per-model substitution | Official datasheets give coverage guidance (PtMP / PtP distances) and per-SKU mapping | |
Six Decision Dimensions Beyond the Spec Sheet
Gain and throughput can only answer “will this device work.” They cannot answer “is this project worth doing.” In real replacement projects, the six dimensions below often carry as much weight as the RF figures.
Dimension 1: Wireless protocol and scheduling
| Spec | Ubiquiti airMAX | LigoWave LigoDLB |
|---|---|---|
| Proprietary TDMA protocol | airMAX (M generation) / airMAX ac (AC generation) | iPoll 3 |
| Scheduling | airMAX: centrally scheduled TDMA (Ubiquiti positions airMAX as improving PtMP interference resistance and scale) | iPoll 3: officially defined as allocating time slots to each client, eliminating collisions and allowing more CPEs to connect simultaneously |
| Interoperability | None — iPoll 3 cannot run alongside airMAX, so replacement must be done in pairs | |
| Between Ubiquiti’s own generations | airMAX ac and the M generation also cannot mix in airMAX mode and can only fall back to standard 802.11 (per official airOS documentation) | |
| Interoperable compromise | Both ends can fall back to standard 802.11 mode and interoperate, at the cost of losing TDMA slot scheduling, with lower throughput and interference resistance | |
This dimension is a draw — airMAX and iPoll 3 are both proprietary TDMA implementations, each closed. The real distinction is that Ubiquiti’s own airMAX ac will not interoperate with the older M generation either, which means the first-party Ubiquiti path also requires paired replacement and offers no more room for a phased transition than switching to LigoWave does. So protocol incompatibility is not an extra penalty for changing brands; it is a constraint built into the airMAX system itself. If your network runs airMAX (you can see the airMAX toggle in the airOS interface), plan for whole-link, paired cutovers.
Dimension 2: Power and site modification cost
| Current power arrangement | What has to change for LigoDLB | Modification cost |
|---|---|---|
| 24 V passive PoE injector (the dominant setup at airMAX sites) | Nothing at all — the injector and cable carry straight over | Zero |
| Centralised 802.3af/at switch power | Insert a 24 V passive injector on the device side; the original switch port becomes a plain data port | One injector per site plus wiring labour |
This is the most practical advantage in the Ubiquiti replacement scenario: the vast majority of airMAX generations (Rocket M5, PowerBeam, NanoBeam, NanoStation) run 24 V passive PoE, which matches LigoDLB’s power scheme exactly, so injectors carry straight over. That is the opposite of the Cambium situation (802.3af/at, which does require modification — see the Cambium ePMP 5 GHz replacement guide) and is the basis for rating the Ubiquiti article’s modification burden as “low.” One operating caution: LigoDLB is 24 V passive, so do not connect an 802.3af switch’s 48 V output directly to it — the voltage mismatch carries a risk of damage. The correct approach is to disable PoE on the switch port and power the radio through a 24 V injector.
Dimension 3: Management and bulk operations
Ubiquiti uses UISP (formerly UNMS) for centralised management; LigoWave uses WNMS. Both platforms handle bulk configuration pushes, firmware upgrades and status monitoring at a broadly similar level of capability — this is not a dimension where we claim WNMS as an advantage; it is a like-for-like substitution. The real difference is team habit. If your operations team has already built alerting, reporting and automation workflows on UISP, moving to WNMS carries migration and relearning cost that belongs in the project hours. Conversely, if the team has no unified management platform at all and relies on logging into each airOS web interface to change configuration, switching to WNMS is an upgrade in how the network is run. To give credit where it is due, UISP’s maturity and community resources are genuine Ubiquiti assets and should honestly be entered as a reason to stay rather than reduced to a discontinued-product label.
Dimension 4: Lifecycle and supply certainty
NS5 and Loco5 are already at the official “Obsolete” tier: no feature or security updates, no longer officially sold, potentially partially or entirely unsupported in future releases. A large set of models — Rocket M5, PowerBeam, airGrid, NanoBridge and others — sit at “Vintage,” which officially means “will be discontinued or is no longer actively developed, but remains purchasable and supported.” Both tiers point the same direction: this equipment is on the downward slope of its lifecycle. The LigoDLB 5ac series is in production and continues to ship firmware. For a carrier-grade link, “a guaranteed new unit within two weeks of a failure” is itself part of the availability metric, so estimate your risk exposure once as failure rate × supply lead time rather than hunting for stock after something fails.
Dimension 5: Evolution path (6 GHz)
The airMAX line itself has no 6 GHz fixed-wireless models. Ubiquiti’s 6 GHz capability shows up in UniFi Wi-Fi products (such as the UniFi U7 Pro Outdoor, which officially is limited to FCC/IC regions and requires AFC) — that is Wi-Fi access, not an airMAX-style point-to-point or point-to-multipoint fixed-wireless platform. On the LigoWave side, the LigoDLB 6 series (5.9–6.4 GHz) shares the same hardware platform, the same iPoll 3 protocol and the same WNMS management as the LigoDLB 5ac — moving from 5 GHz to 6 GHz is a frequency migration within one platform, not a change of system. 6 GHz regulation varies by country (5925–7125 MHz is not open for civilian use in mainland China), so whether this dimension applies to you depends on your market. Confirm local rules first.
Dimension 6: Procurement and spare-parts cost structure
For discontinued and vintage models, the “list reference price” no longer tells you anything useful — the real acquisition cost depends on channel inventory and batch, and can carry either a premium or a discount, so this article invents no specific numbers. What can be stated is the difference in cost structure: the LigoDLB 5ac and LigoDLB 6 series share a platform, a management system (WNMS) and a 24 V power scheme across the whole range, so spares can be shared across models and the warehouse does not have to hold stock separately for every SKU. With a mixed airMAX vintage/obsolete estate, every SKU needs its own stock, and the more varied the model list, the more capital is tied up in spares. When you build the annual spares budget, the product “number of SKUs × stock depth per SKU” should be as small as possible — that is a question of product-line strategy, not of unit price.
How to Calculate the Link Budget (Do This Before You Order)
Any time replacement changes gain or transmit power, the link budget has to be worked through again. Running the numbers beats guessing. The method has four steps, and every input comes from the official figures already listed above.
Step 1: Calculate free-space path loss (FSPL)
Taking 5.8 GHz (f = 5800 MHz) as the example, across five typical distances:
| Link distance | Working | 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 |
| 20 km | 32.44 + 20log₁₀(20) + 75.3 = 32.44 + 26.0 + 75.3 | ≈ 133.8 dB |
| 30 km | 32.44 + 20log₁₀(30) + 75.3 = 32.44 + 29.5 + 75.3 | ≈ 137.3 dB |
Step 2: Calculate received signal level (RSL)
Cable and connector loss is taken as 1 dB for connectorised scenarios. Both worked examples below use real models that appear earlier in this article:
| Link | Values substituted | RSL |
|---|---|---|
| 10 km PtMP: AP side Rocket M5 + AM-5G20-90, CPE side NS5 (estimated at 16 dBi, 25 dBm) | 25 + 20 + 16 − 127.7 − 1 | −67.7 dBm |
| 10 km PtMP: AP side LigoDLB 5-90AC (18 dBi, taken as 27 dBm), CPE side LigoDLB 5-15ac (15 dBi, 27 dBm) | 27 + 18 + 15 − 127.7 − 1 | −68.7 dBm |
| 20 km PtP: PBE-M5-620 at both ends (29 dBi, 24 dBm) | 24 + 29 + 29 − 133.8 − 1 | −52.8 dBm |
| 20 km PtP: LigoDLB 5-20ac at both ends (20 dBi, 25 dBm) | 25 + 20 + 20 − 133.8 − 1 | −69.8 dBm |
| 20 km PtP: LigoDLB 5ac at both ends (≤30 dBm, taken as 27) + reuse of the original 29 dBi dish antenna | 27 + 29 + 29 − 133.8 − 1 | −49.8 dBm |
Reading the results directly: ① the 10 km base-station scenario — the LigoDLB 5-90AC + 5-15ac option comes in about 1 dB below the Rocket M5 + AM-5G20-90 option, essentially equal. But that is only “just barely working,” because LigoWave’s official PtMP coverage guidance for the 5-15ac is 5 km, and 10 km sits outside its comfort zone. In practice you should step the CPE up to the 5-20ac and recover 5 dB with 20 dBi. ② the 20 km dish scenario — the integrated 5-20ac’s RSL (−69.8 dBm) is already below the roughly −64 dBm needed for the 80 MHz high-throughput tier, so the link will drop rate. The 5ac reusing the original 29 dBi dish (−49.8 dBm) not only holds the link but comes in 3 dB better than the original PBE-M5-620 arrangement — which is the quantitative case for “connectorised radio + reused feed” being superior to an integrated radio at the long-range tier.
Step 3: Set the replacement tier from the gain difference
| Gain difference (original → replacement) | Theoretical change in maximum distance (6 dB halving rule) | Engineering guidance |
|---|---|---|
| ≤2 dB (e.g. NS-5ACL 13 dBi → 5-15ac 15 dBi) | ≤12% per dB, in the “better” direction | Replace directly; margin actually increases |
| 2–3 dB (e.g. LBE-5AC-23 → 5-20ac) | 3 dB reduces distance to about 71% (theoretical limit) | Usually a direct replacement; run the formula once before ordering |
| ≥5 dB and link >8 km (e.g. PBE-M5-620, NB-5G25, high-gain airGrid tiers) | — | Switch to LigoDLB 5ac + reuse of the original 22–29 dBi antenna; do not force an integrated radio to cover it |
Step 4: Three checks that are easy to skip
- Fresnel zone: the first Fresnel zone radius is r = 17.32 × √(d/4f) (metres, with d in km and f in GHz). On a 5.8 GHz / 10 km link, the first Fresnel zone radius at the midpoint is about 11 metres — confirm before replacing that at least 60% of this region is clear of obstruction. Obstruction hurts a link more than a gain shortfall does, and no change of model fixes it.
- Coverage change from beamwidth: going from the NS-5ACL’s 45° to the 5-15ac’s 35°, or from the AM-5G20-90’s 6 dB definition to LigoWave’s 3 dB definition, both move the effective coverage boundary. Identify the original network’s edge users before replacing and test them specifically afterwards.
- Regulatory power: a change in the sum of the two ends’ gains changes EIRP, so after replacement re-check the transmit power setting against your local 5 GHz EIRP limit and dial it down in the device if needed — especially with high-gain combinations such as a 5ac (≤30 dBm) plus a 29 dBi dish.
Deployment Scenarios and Three Routes
Boiling all of the above down into three executable routes, ordered from least to most work:
| Route | Where it fits | Configuration | Benefit |
|---|---|---|---|
| Route 1: like-for-like replacement (fastest, lowest risk) | Link distance and bandwidth requirements unchanged; the driver is mainly “obsolete models have no security updates / uncertain supply” | NS5 / Loco5 / NS-5ACL → 5-15ac; Rocket M5 → 5ac; Rocket + sector → 5-90AC | Installation process and 24 V injectors carry over unchanged, and you gain 500+ Mbps plus a Gigabit port |
| Route 2: capacity upgrade | The network is constrained by Fast Ethernet ports and 150 Mbps and needs more access bandwidth | Base station 5-90AC + CPE 5-15ac / 5-20ac, with 80 MHz enabled | Per-link and per-site capacity steps up, and the protocol generation change happens at the same time |
| Route 3: long-range rebuild (feed line retained) | Sites using high-gain long-range gear such as PBE-M5-620 / NB-5G25 / airGrid | LigoDLB 5ac + reuse of the original 22–29 dBi antenna, or rebuild the sector with a 5-90AC on the base-station side | Original feed line and tower work are retained and only the radio head is replaced; at 20 km this measures slightly better than the original arrangement |
Mapped onto specific business cases, the most common combinations are:
- Campus and school 5 GHz coverage backhaul: bulk-replace NS5 / Loco5 / NS-5ACL with the 5-15ac, managed centrally through WNMS so that firmware upgrades and configuration pushes across hundreds of units no longer require logging in one by one.
- ISP access-network CPE platform: upgrade Rocket M5 + sector base stations to 5-90AC (base station) + 5-15ac (CPE). Note that for PtMP links beyond 10 km the CPE should step up to the 5-20ac.
- Multi-point video surveillance backhaul: replace PBM5 / PBE-5AC with the 5-20ac or 5ac + dish antenna, and enable QoS (L2 CoS / L3 ToS-DSCP, WRR) to protect video priority.
- Utility, water and oil private networks: for connectorised Rocket M5 / Bullet M5 sites, move to 5ac + the existing antenna, leaving the feed line and tower untouched and keeping the outage window to a minimum.
Strengths and Limitations
Five strengths that hold up
- Zero power modification: the vast majority of airMAX units are 24 V passive PoE, identical to LigoDLB, so injectors and cabling carry straight over — the single biggest implementation advantage of the Ubiquiti scenario over the Cambium one.
- Existing feed lines can be reused (connectorised and long-range tiers): the N-type antennas on Rocket M5 and Bullet M5, and the dishes and high-gain antennas on the PBE-M5-620 / NB-5G25, can all stay, with only the radio head replaced — which minimises both the work and the outage window.
- A complete product ladder: 15 dBi wide beam, 20 dBi narrow beam, an 18 dBi integrated 90° sector base station, and a connectorised platform — one platform covering both CPE and base-station sides, with no need to cobble together third-party antennas.
- A defined 6 GHz evolution path: the airMAX line has no 6 GHz fixed-wireless models, whereas the LigoDLB 6 series shares platform, protocol and management with the 5ac — a ready-made evolution path in regions where 6 GHz is available.
Three limitations, stated plainly
① The protocols are not interoperable, so replacement must be done in pairs. iPoll 3 and airMAX cannot run together. There is no “replace one end” option — though the same is true between Ubiquiti’s own airMAX ac and M generations, so changing brands does not add this constraint. If you want to stage the work, you either drop whole links back to standard 802.11 mode (sacrificing throughput and interference resistance) or cut over in pairs, batch by batch.
② There is no 25–29 dBi integrated dish. Against the PBE-M5-620 (29 dBi), NB-5G25 (25 dBi) and high-gain airGrid tiers, LigoWave’s integrated radios top out at 20 dBi and offer no advantage in gain. Links in this class must go the 5ac + reused antenna route or accept a shorter distance. There is no point pretending otherwise.
③ LigoDLB is a bridge, not a replacement for airOS routing. The NAT, DHCP and routing policy functions available on airOS have no counterpart on LigoDLB. At sites using airMAX gear as a router or gateway, those functions have 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.
Migration Plan (Six Phases)
This process is sequenced around “work it out first, validate at small scale, then roll out in bulk,” and every step has defined inputs, outputs and exit criteria. Networks of ten sites or fewer can merge phases two and three; networks of a hundred or more should follow the order strictly.
Export your installed airMAX records, with each entry carrying at least the following fields — miss one and the budgeting and scheduling downstream drift from estimates into guesswork:
| Field | Description | How to capture it |
|---|---|---|
| Model / product code | e.g. NS-5ACL, RM5-Ti, PBE-M5-620 | Asset records or the airOS System page |
| Official status | Obsolete / Vintage / not listed | Check against the official vintage and obsolete products page |
| Device role | AP side / CPE side / one end of a PtP link | Network topology diagram |
| Current wireless mode | airMAX / airMAX ac / standard 802.11 | airOS → Wireless settings page |
| Frequency / bandwidth / signal strength | e.g. 5580 MHz / 20 MHz / RSL −62 dBm | airOS → status / station list page |
| Antenna form factor and gain | Model for integrated; antenna model for external (e.g. AM-5G20-90, 29 dBi dish) | Site visit or asset records |
| Measured throughput and latency | Record the baseline | Three runs at off-peak, averaged |
| Link distance / azimuth | GPS coordinate difference / compass reading | Site visit or mapping tool |
| Power arrangement | 24 V injector / 802.3af switch, cable length | Site confirmation plus injector labels |
| IP / VLAN / routing configuration | Whether the site also routes, runs NAT or serves DHCP | Export and back up the configuration |
| Business criticality tier | A (core backhaul) / B / C | Confirm with the business owner |
Exit criteria: every link has a complete record; sites at the official “Obsolete” tier (NS5 / Loco5) and sites that are “unlisted but carry risk” are flagged separately, with the former taking top priority.
Using the method in section 6, work through the RSL for each link. The decision rules are:
Exit criteria: every site has an explicit replacement model, an antenna plan (retain / buy new / reuse the original dish) and a power-modification verdict (zero modification / add injector).
Exit criteria: every unit passes a power-on self-test, its configuration matches the asset record, and its label corresponds one-to-one with the site.
Selection criteria: one typical tier-A link (NS5 or NS-5ACL to 5-15ac) plus one long-range link (a PBE-M5-620 going the reused-antenna route, to confirm the budget decision was right). Schedule the cutover in an off-peak window. The sequence is:
- Record the baseline: before cutover, log the old link’s signal strength, CCQ / airOS association status, measured throughput and latency.
- Photograph and mark: photograph the old unit’s azimuth, elevation, cable order and label positions — installing the new unit in the same orientation keeps realignment to a minimum. For connectorised swaps, note which polarity each of the two N-type jumpers connects to.
- Remove the old, install the new: keep azimuth and elevation aligned with the initial values and connect the 24 V injector (always disable PoE output on an 802.3af switch port first).
- Align and fine-tune: after power-up and registration, adjust azimuth and elevation in small steps for maximum signal, lock it down, then take a confirmation reading.
- Validation checklist: wireless registration succeeds; RSL is within 3 dB of the budgeted value; measured throughput is at or above the old link’s baseline; latency and packet loss do not degrade; VLAN and service pass-through work; the unit is visible in WNMS.
Rollback plan (mandatory): the old unit’s configuration is backed up and the unit is left untouched (sealed and labelled after it comes down). If any item on the validation checklist fails during the pilot window and the cause cannot be identified within 30 minutes, reinstall the old unit and reschedule for a review. The point of a pilot is to hit the problems that bulk rollout would otherwise hit.
Exit criteria: both pilot links run stably for 72 consecutive hours with every checklist item passing, and a documented standard cutover procedure has been produced.
Proceed in batches, on these principles:
During bulk execution, reconcile network-wide registration status and alarms in WNMS once a day, and update the asset record (model, date, accepting engineer) as each batch completes.
Exit criteria: all target sites are cut over and have run stably for two weeks, with no unresolved rollbacks.
Per-site cutover checklist (printable)
| # | Check | Pass criterion |
|---|---|---|
| 1 | Power scheme confirmed | 24 V passive injector in place; PoE disabled on 802.3af switch ports |
| 2 | Mounting orientation | Azimuth and elevation match the markings on the old unit; pole mount secure |
| 3 | Feed-line connection (connectorised) | N connectors correctly polarised and torqued; weatherproofing wrap complete |
| 4 | Weatherproofing and grounding | All connectors weatherproofed; tower equipment reliably bonded to earth |
| 5 | Wireless registration | Peer registers successfully in iPoll 3 (not a fallback standard 802.11 mode) |
| 6 | Signal level | RSL within 3 dB of the link budget, with at least 10 dB of margin |
| 7 | Throughput / latency | Measured throughput at or above the old link baseline; latency and packet loss not degraded |
| 8 | Service validation | VLAN pass-through, QoS marking and live traffic all normal |
| 9 | Management onboarding | Visible in WNMS, with IP matching the asset record |
| 10 | Regulatory compliance | Transmit power / EIRP set to the local 5 GHz limit |
| 11 | Rollback readiness | Old unit and configuration backup in place; rollback path documented |
References
- Ubiquiti Help Center article on vintage and obsolete products (the two-tier definitions and the official SKU lists): help.ui.com
- Ubiquiti official datasheets by model: NanoStation 5 / NanoStation AC, NanoBeam, PowerBeam, Rocket M, Bullet M, LiteBeam and the airMAX Sector Antenna series (dl.ubnt.com)
- LigoWave official datasheets (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 publication or submission to a tender.
Frequently Asked Questions
Q: Why did Ubiquiti discontinue or obsolete these 5 GHz devices?
Ubiquiti gives no per-model reason, only a general statement — “Ubiquiti is committed to product innovation and providing quality technical support to our customers, which means that sometimes discontinued products will no longer be supported” — with the English page adding “some older products will eventually stop being manufactured and will no longer receive full software updates.” Consistent with this article’s editorial rule, no motive is speculated about here. What can be confirmed is that Ubiquiti placed these SKUs into the “Vintage” and “Obsolete” tiers while keeping a large number of airMAX devices on sale (such as the airMAX ac sector series): specific classic models were retired, not the whole product line.
Q: What is the practical difference between “Vintage” and “Obsolete,” and which batch should I move first?
Officially, “Vintage” means the product will be discontinued or is no longer actively developed but is still purchasable and supported (including critical bug fixes and security updates); “Obsolete” means no further feature or security updates, no longer officially sold, and potentially partially or entirely unsupported in future releases. The priority is therefore clear: replace the officially Obsolete NS5 and Loco5 first (they run unprotected, with no security patches), and schedule the Vintage models by business criticality and link margin. Note that “Obsolete” does not mean the hardware stops working immediately — it will keep forwarding traffic — but there is no official repair channel once it fails.
Q: Can I replace only one end (CPE switched to LigoDLB, AP left on Ubiquiti)?
Not directly — iPoll 3 and airMAX do not interoperate. The only compromise is to drop both ends back to standard 802.11 mode, which costs you TDMA slot scheduling and reduces throughput and interference resistance, so any transition period must be short and the AP-side switch scheduled for an off-peak window. One related point: Ubiquiti’s own airMAX ac and older M generation also cannot mix in airMAX mode, so “replace in pairs” is a constraint the airMAX system already had — changing brands does not make it any stricter.
Q: Does the power supply need changing after switching to LigoDLB?
At most sites, no work at all. The vast majority of airMAX generations (Rocket M5, PowerBeam, NanoBeam, NanoStation) are 24 V passive PoE, matching LigoDLB, so injectors and cabling carry straight over. Where the site uses a centralised 802.3af switch, you need to insert a 24 V passive injector on the device side and disable PoE output on the switch port — note that 802.3af’s 48 V cannot be connected directly to a LigoDLB, as the voltage mismatch risks damage.
Q: The PBE-M5-620 is 29 dBi — how much do I lose going to a 20 dBi 5-20ac?
Across both ends that is 18 dB, which an integrated radio simply cannot absorb — so this class of link should not be replaced with an integrated radio at all. The correct path is a connectorised LigoDLB 5ac plus reuse of the original 29 dBi dish: on a 20 km link, the 5ac (27 dBm) with the original dish gives an RSL of about −49.8 dBm, roughly 3 dB better than the original PBE-M5-620 arrangement (−52.8 dBm), because the 5ac transmits at higher power. The precondition is that the dish and feed are in good condition, which should be confirmed on site before replacing.
Q: Our team relies heavily on airOS routing features. Can LigoDLB replace that?
No, and it does not need to. LigoDLB is positioned as a wireless bridge and has none of airOS’s NAT / DHCP / routing policy framework. Sites like this can be handled in two ways: move the routing function up to an aggregation-layer device, or keep the Ubiquiti unit for routing at that location and replace only the wireless portion. Conversely, if your pain point is logging into dozens of airOS units one by one to change configuration, WNMS’s template-driven bulk management addresses exactly that. Using the two approaches side by side, chosen by site type, is a reasonable design.
Q: How much does performance actually improve after replacement?
Two cases. NS-5ACL → 5-15ac is a same-generation gain upgrade (13 dBi → 15 dBi, beam 45° → 35°), where the gain is mainly in link margin and beam control. The M-generation set — NS5 / Loco5 / Rocket M5 / PowerBeam M — moving to the LigoDLB 5ac series is a generational upgrade: 802.11a/n → 802.11ac (256-QAM + LDPC), Fast Ethernet → Gigabit, throughput up to 500+ Mbps, and the addition of 80 MHz plus 5/10 MHz channel widths. On the same tower position and spectrum, the latter delivers a substantial increase in link capacity.




