[Device]: Ubiquiti Iso-Beam-19 RF Isolator Shield for NanoBeam NBE-M2-13, NBE-M5-19 #246

Closed
opened 2026-11-08 06:12:35 +00:00 by jaylouisw · 2 comments
Owner

Vendor

Ubiquiti

Exact model name

Ubiquiti Iso-Beam-19 RF Isolator Shield for NanoBeam NBE-M2-13, NBE-M5-19

Category

Point-to-point radio

Ports and interfaces

  • See product page for full port list

Ports inferred from the 4gon product name; confirm against the product page.

PoE budget (watts)

None

Datasheet or product page URL

https://www.4gon.co.uk/ubiquiti-isobeam19-rf-isolator-shield-for-nanobeam-nbem213-nbem519-p-7123.html

What do you want to model with it?

A PtP/PtMP wireless bridge link in a wireless lab.

Capabilities

wireless, l2-forward (bridge)

Before submitting

  • I searched the catalog and existing issues, and this model is not there yet.
  • The port list above comes from a datasheet, not from memory or another wiki.
### Vendor Ubiquiti ### Exact model name Ubiquiti Iso-Beam-19 RF Isolator Shield for NanoBeam NBE-M2-13, NBE-M5-19 ### Category Point-to-point radio ### Ports and interfaces - See product page for full port list > Ports inferred from the 4gon product name; confirm against the product page. ### PoE budget (watts) None ### Datasheet or product page URL https://www.4gon.co.uk/ubiquiti-isobeam19-rf-isolator-shield-for-nanobeam-nbem213-nbem519-p-7123.html ### What do you want to model with it? A PtP/PtMP wireless bridge link in a wireless lab. ### Capabilities wireless, l2-forward (bridge) ### Before submitting - [x] I searched the catalog and existing issues, and this model is not there yet. - [x] The port list above comes from a datasheet, not from memory or another wiki.
Author
Owner

Iso-Beam-19 is an RF isolator shield that clips onto a NanoBeam NBE-M2-13 / NBE-M5-19 to reduce side-lobe interference. It has no ports at all.

The catalogue has no category for it. Every spec needs at least one interface the engine can forward on, and these parts have none - the same gap that keeps the Huawei optical modules open. Two ways this could close, and the first needs the owner's decision: add a passive (or antenna/rf-accessory) category for parts with no data ports, or leave these requests open as a known boundary. I have raised it with the owner and am not inventing a category unilaterally.

**Iso-Beam-19** is an RF isolator shield that clips onto a NanoBeam NBE-M2-13 / NBE-M5-19 to reduce side-lobe interference. It has no ports at all. **The catalogue has no category for it.** Every spec needs at least one interface the engine can forward on, and these parts have none - the same gap that keeps the Huawei optical modules open. Two ways this could close, and the first needs the owner's decision: add a `passive` (or `antenna`/`rf-accessory`) category for parts with no data ports, or leave these requests open as a known boundary. I have raised it with the owner and am not inventing a category unilaterally.
Author
Owner

Closing this one as not a network device.

Iso-Beam-19 is an RF isolator shield - a metal shroud that clips around a NanoBeam to cut interference from nearby radios. Passive hardware with no interface of any kind; the NanoBeam inside it is the device.

As with the other accessories here, the port line was inferred from the product name rather than read from a datasheet, because there is nothing to read.

Closed as out of scope for the device catalogue. The reasoning is now written down in docs/DEVICE_REGISTRY.md (What the catalogue cannot represent, commit 08d5925) so the next request of this kind can cite it: an accessory with no Ethernet, console, optical or DSL port and no management surface cannot be simulated. A spec for it would be a name with an empty interfaces array, and the palette would then offer a lab something that looks cableable and isn't - worse than leaving the request open.

The distinction matters: this is structurally unrepresentable, whereas #527 (Netonix) stays open because that one is a switch and merely lacks a published PoE budget. A gap in the source is not a gap in the simulator, and the fix there is a citation, not a guess.

Closing this one as **not a network device**. Iso-Beam-19 is an **RF isolator shield** - a metal shroud that clips around a NanoBeam to cut interference from nearby radios. Passive hardware with no interface of any kind; the NanoBeam inside it is the device. As with the other accessories here, the port line was inferred from the product name rather than read from a datasheet, because there is nothing to read. Closed as **out of scope for the device catalogue**. The reasoning is now written down in `docs/DEVICE_REGISTRY.md` (*What the catalogue cannot represent*, commit `08d5925`) so the next request of this kind can cite it: an accessory with no Ethernet, console, optical or DSL port and no management surface cannot be simulated. A spec for it would be a name with an empty `interfaces` array, and the palette would then offer a lab something that *looks* cableable and isn't - worse than leaving the request open. The distinction matters: this is **structurally** unrepresentable, whereas #527 (Netonix) stays open because that one *is* a switch and merely lacks a published PoE budget. A gap in the source is not a gap in the simulator, and the fix there is a citation, not a guess.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge#246
No description provided.