XGS 116
ARMADA · CN9131 · 9 front ports: 8 RJ45, 1 SFP · added, untested
Added, untested
Added from the vendor's board file and device tree - research and development, because there is no XGS 116 here to test on. It installs, its status page says so, and its first boot holds its ports against what its coprocessor reports: an owner's report confirms this page or corrects it. Appliances of these models will be bought to test on.
At a glance
| model | board | state |
|---|---|---|
| XGS 116 | AMDA0208-0001 |
added, untested |
| XGS 116w | AMDA0208-0002 |
added, untested |
The ARMADA family, driven by npuep: 9 front ports (8 RJ45, 1 SFP), the interfaces npup1 to npup9, and the internet on Port1 when the first boot sets the appliance up by itself.
Reported by appliances of this model
No appliance of this model has reported yet. If you have one: report it.
The back panel, where the ports are
behind the 88E6193X switchon the coprocessor itself
Approximate. The ports, their sockets, labels and speeds are the vendor's board file's; where they sit is modelled on the panel of the XGS 136, not seen on this model.
Every port
In the order of the host's interfaces, npupN. The tag is the coprocessor's name for the port, which the driver uses; a port behind the switch reaches the coprocessor through the switch's one link to it.
| label | socket | speed | interface | tag | attached to | |
|---|---|---|---|---|---|---|
| Port1 | RJ45 | 1G | npup1 |
0x8100 |
switch port 1 | |
| Port2 | RJ45 | 1G | npup2 |
0x8200 |
switch port 2 | |
| Port3 | RJ45 | 1G | npup3 |
0x8300 |
switch port 3 | |
| Port4 | RJ45 | 1G | npup4 |
0x8400 |
switch port 4 | |
| Port5 | RJ45 | 1G | npup5 |
0x8500 |
switch port 5 | |
| Port6 | RJ45 | 1G | npup6 |
0x8600 |
switch port 6 | |
| Port7 | RJ45 | 1G | npup7 |
0x8700 |
switch port 7 | |
| Port8 | RJ45 | 1G | npup8 |
0x8800 |
switch port 8 | |
| F1 | SFP | 1G | npup9 |
0x8900 |
switch port 9 |
The board
Two computers in one box: the host runs OPNsense and reaches a front port only through the coprocessor, which owns them all. The links and the MACs are the vendor's board file's and device tree's; the host is what has been read of it; nothing here has been seen on this model.
Technical details
| part | detail | source |
|---|---|---|
| host | not read here | |
| host to coprocessor | PCIe 11ab:7080 | board file |
| coprocessor | CN9131 (AP807 + two CP115) | board file |
| switch | 88E6193X · its link: CP0 eth0, 10GBASE-KR | device tree |
| the vendor's platform | xgsdt2-116 |
board file |
| storage | 64 GB SSD | datasheet |
| console and management | COM (RJ45), Micro-USB | datasheet |
| other ports | USB 2.0, USB 3.0 | datasheet |
| module slots | 1 | datasheet |
| Wi-Fi | Wi-Fi 5, 2x2 (XGS 116w) | datasheet |
| PoE | 1 x GE, 30 W | datasheet |
| form | desktop · 320 x 44 x 213 mm · 2.2 kg | datasheet |
| power supply | external · 150 W | datasheet |
| power drawn | XGS 116: 28 W idle, 57 W at most XGS 116w: 30 W idle, 60 W at most |
datasheet |
Expansion modules
Its bay is the host's, not the coprocessor's: the vendor sells 3G/4G, 5G, Wi-Fi (116w) for it. None has been fitted here, and none goes through the coprocessor.
The vendor's figures
As the vendor's datasheet prints them; not measured here. Its stated method is Keysight-Ixia BreakingPoint under ideal conditions; the MTU, the ports and whether a figure counts both directions are not stated.
| edition 2024-11 | |
|---|---|
| Firewall | 7,700 Mbps |
| Firewall IMIX | 4,500 Mbps |
| Firewall latency (64-byte UDP) | 8 µs |
| IPS | 2,500 Mbps |
| Threat protection | 2,160 Mbps |
| NGFW | 2,000 Mbps |
| Concurrent connections | 1,600,000 |
| New connections a second | 61,500 |
| IPsec VPN | 4,800 Mbps |
| IPsec VPN tunnels | 1,500 |
| SSL VPN tunnels | 1,250 |
| TLS inspection | 650 Mbps |
| TLS inspection connections | 8,192 |
If you have one
Install it and it runs as this page says. Ten minutes after its first boot, portcheck.py holds the ports above against what its coprocessor reports and, with problem reports on, files the answer - which is what confirms this page or corrects it. Or say what works yourself: report your appliance.
Where each fact was read
- the vendor's board files:
xgs-bsp/data/<assembly>.txt, the vendor's board file (GPL release, SDK 10.22.03) - the vendor's device tree:
sdk-ext-sophos patches dt1, dt2 and dt2-138, the vendor's device trees - the vendor's board files:
xgs-check-uboot-version.sh, the vendor's map of assembly to platform - the vendor's board files:
xgs-host-startup.sh, where the vendor's host tells the families apart by PCI id - the vendor's datasheet: the vendor's XGS 116(w) page, brochure edition of 2024-11, a reseller's copy
The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.