Allied Telesis x530: nine access switches, 740 W that is not 48 x 30 W, and PoE that depends on which PSU is fitted #1550

Merged
jaylouisw merged 1 commit from catalogue/1115-2125 into main 2026-11-15 21:53:20 +00:00
Owner

The catalogue had one Allied Telesis part (an AT-MC102XL media converter) and no AlliedWare Plus switch at all. This adds the x530 Series, the multi-gigabit L3 access family: two compact 8/16-port PoE++ boxes, the 28- and 52-port copper and PoE+ pairs, the two dual-hot-swap-PSU DP models and the fibre-only 28GSX.

What the datasheet says that the model name does not

  • The 52GPXm is 740 W, not 48 x 30 W. The vendor budget table gives 48 ports at 15.4 W but only 24 at 30 W, and the installation guide says the same as "up to 24 Class 4 powered devices at 25.5 W". Every port is modelled at its 30 W capability against the 740 W budget, so a 48 x 30 W fill is refused by the budget rather than by a port pretending it cannot source 30 W.
  • The 10GHXm declares 720 W of PoE from two 500 W supplies. The same guide says "each power supply provides 500W for a total PoE of 1,000W" three pages after it says 720 W (90 W x 8). The datasheet table says 720 W, so 720 W is recorded and the contradiction is in the spec's notes.
  • 90 W PoE++ is not on every port of the 18GHXm: 11 of the 16. Modelled at 60 W per port, the rate all 16 hold at once, with the 90 W ceiling explained rather than inventing which 11 ports carry it.
  • The DP models' budget depends on the supplies fitted, 370 W on one PWR800, 740 W on one PWR1200 or two PWR800s, 1480 W on two PWR1200s. The 1480 W ceiling is recorded and the matrix quoted, because "the DP-28 has 1480 W" is only true with two PWR1200s.
  • Multi-gigabit on the 28/52-port boxes is firmware, not new hardware. The 5.4.8-2 stand-alone guide said ports 21-24 were 100M/1G only, while the LED legend in the same figure already read 5G/2.5G/1G/100. The current datasheet's 100M/1/2.5/5G is modelled.

Modelling

Port numbering is AlliedWare Plus port1.0.n as the guides print it: copper 1-20, multi-gigabit 21-24, SFP+ 25-28 on the 28-port chassis (49-52 on the 52-port), with 27/S1 and 28/S2 (51/S1, 52/S2) the default VCStack stacking ports. Those are modelled as Ethernet because disabling VCStack turns them into ordinary SFP+ ports.

Unverifiable, stated in the notes

  • No DP front-panel figure was found in the guides checked here, so the DP port numbering follows the 28/52-port chassis that the same document does number.
  • No 52-port multi-gigabit firmware note was found either way, so ports 41-48 are modelled from the current datasheet alone.
  • The 802.3af/at/bt tokens are power descriptors the engine does not implement; the importer keeps them as declared and warns, as it does for the rest of the catalogue.

Sources

Validation

  • node scripts/syntax-check.js - 324 files, all OK
  • node scripts/audit-port-types.js - clean, "No port contradicts its declared type", no new template-hardware rows
  • node scripts/import-devices.js - 9 added, 0 rejected, 0 duplicates
  • node scripts/run-tests.js - every suite passes except the network-dependent canonical-urls probe, which failed once on a 26 s README clone and passes standalone (52/52)
The catalogue had one Allied Telesis part (an AT-MC102XL media converter) and no AlliedWare Plus switch at all. This adds the x530 Series, the multi-gigabit L3 access family: two compact 8/16-port PoE++ boxes, the 28- and 52-port copper and PoE+ pairs, the two dual-hot-swap-PSU DP models and the fibre-only 28GSX. ## What the datasheet says that the model name does not - **The 52GPXm is 740 W, not 48 x 30 W.** The vendor budget table gives 48 ports at 15.4 W but only 24 at 30 W, and the installation guide says the same as "up to 24 Class 4 powered devices at 25.5 W". Every port is modelled at its 30 W capability against the 740 W budget, so a 48 x 30 W fill is refused by the budget rather than by a port pretending it cannot source 30 W. - **The 10GHXm declares 720 W of PoE from two 500 W supplies.** The same guide says "each power supply provides 500W for a total PoE of 1,000W" three pages after it says 720 W (90 W x 8). The datasheet table says 720 W, so 720 W is recorded and the contradiction is in the spec's notes. - **90 W PoE++ is not on every port of the 18GHXm: 11 of the 16.** Modelled at 60 W per port, the rate all 16 hold at once, with the 90 W ceiling explained rather than inventing which 11 ports carry it. - **The DP models' budget depends on the supplies fitted**, 370 W on one PWR800, 740 W on one PWR1200 or two PWR800s, 1480 W on two PWR1200s. The 1480 W ceiling is recorded and the matrix quoted, because "the DP-28 has 1480 W" is only true with two PWR1200s. - **Multi-gigabit on the 28/52-port boxes is firmware, not new hardware.** The 5.4.8-2 stand-alone guide said ports 21-24 were 100M/1G only, while the LED legend in the same figure already read 5G/2.5G/1G/100. The current datasheet's 100M/1/2.5/5G is modelled. ## Modelling Port numbering is AlliedWare Plus `port1.0.n` as the guides print it: copper 1-20, multi-gigabit 21-24, SFP+ 25-28 on the 28-port chassis (49-52 on the 52-port), with 27/S1 and 28/S2 (51/S1, 52/S2) the default VCStack stacking ports. Those are modelled as Ethernet because disabling VCStack turns them into ordinary SFP+ ports. ## Unverifiable, stated in the notes - No DP front-panel figure was found in the guides checked here, so the DP port numbering follows the 28/52-port chassis that the same document does number. - No 52-port multi-gigabit firmware note was found either way, so ports 41-48 are modelled from the current datasheet alone. - The 802.3af/at/bt tokens are power descriptors the engine does not implement; the importer keeps them as declared and warns, as it does for the rest of the catalogue. ## Sources - x530 Series datasheet (SPECIFICATIONS, Power and Noise, PSU matrix): https://www.alliedtelesis.com/wp-content/uploads/2026/05/ati-x530series-ds.pdf - x530 product pages: https://www.alliedtelesis.com/us/en/products/switches/x530-series - Quick Installation Guide (port numbering, PoE+ budgets, console): https://www.alliedtelesis.com/sites/default/files/file/2022-03/ati-x530-english-qig.pdf - Installation Guide for VCStack (S1/S2 numbering, per-PSU budgets, PD classes): https://www.alliedtelesis.com/sites/default/files/documents/installation-guides/ati_x530_vc_stacking_ig.pdf ## Validation - `node scripts/syntax-check.js` - 324 files, all OK - `node scripts/audit-port-types.js` - clean, "No port contradicts its declared type", no new template-hardware rows - `node scripts/import-devices.js` - 9 added, 0 rejected, 0 duplicates - `node scripts/run-tests.js` - every suite passes except the network-dependent canonical-urls probe, which failed once on a 26 s README clone and passes standalone (52/52)
Allied Telesis x530: nine access switches, 740 W that is not 48 x 30 W, and PoE that depends on which PSU is fitted
All checks were successful
CI / Classify the change (pull_request) Successful in 16s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 21s
CI / Test (Node 18) (pull_request) Successful in 3m25s
CI / Test (Node 20) (pull_request) Successful in 3m9s
CI / Server smoke test (pull_request) Has been skipped
CI / Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 3m6s
265d113086
The catalogue had one Allied Telesis part (an AT-MC102XL media converter) and no
AlliedWare Plus switch at all. This adds the x530 Series - the multi-gigabit L3
access family: two compact 8/16-port PoE++ boxes, the 28- and 52-port copper and
PoE+ pairs, the two dual-hot-swap-PSU DP models and the fibre-only 28GSX.

Facts that do not survive a glance at the model name, all sourced:

- The 52GPXm is 740 W, not 48 x 30 W. The vendor budget table gives 48 ports at
  15.4 W but only 24 at 30 W, and the installation guide says the same thing as
  "up to 24 Class 4 powered devices at 25.5 W". Every port is modelled at its
  30 W capability against the 740 W budget, so a 48 x 30 W fill is refused by the
  budget rather than by a port that pretends it cannot source 30 W.
- The 10GHXm declares 720 W of PoE from two 500 W supplies. The same guide says
  "each power supply provides 500W for a total PoE of 1,000W" three pages after it
  says 720 W (90 W x 8); the datasheet table says 720, so 720 is what is recorded
  and the discrepancy is in the spec's notes.
- 90 W PoE++ is not on every port of the 18GHXm: 11 of the 16. Modelled at 60 W
  per port (the rate all 16 hold at once) with the 90 W ceiling explained, rather
  than inventing which 11 ports carry it.
- The DP models' budget is a function of the supplies fitted (370 W on one PWR800,
  740 W on one PWR1200, 1480 W on two). The 1480 W ceiling is recorded and the
  matrix is quoted, because "the DP-28 has 1480 W" is only true with two PWR1200s.
- Ports 21-24 (28-port) / 41-48 (52-port) are multi-gigabit today, but the 5.4.8-2
  stand-alone installation guide said ports 21-24 were 100M/1G only. The LED
  legend in the same figure already read 5G/2.5G/1G/100, so that was firmware;
  the current datasheet's 100M/1/2.5/5G is what is modelled.

Unverifiable, and stated as such in the notes: no DP front-panel figure was found,
so the DP port numbering follows the 28/52-port chassis the same document numbers;
no 52-port multi-gigabit firmware note was found either way.

Port numbering is AlliedWare Plus port1.0.n as the guides print it: copper 1-20,
multi-gigabit 21-24, SFP+ 25-28 (27/S1 and 28/S2 the default VCStack stacking
ports, modelled as Ethernet since disabling VCStack makes them ordinary ports).

Validation: syntax-check 324 files OK; audit-port-types clean ("No port
contradicts its declared type", no new template-hardware rows); importer reports
9 added / 0 rejected; catalogue-hygiene, faceplate-catalogue, poe, poe-agreement,
importer-roundtrip, template-expansion and doc-catalog-counts all pass.
jaylouisw scheduled this pull request to auto merge when all checks succeed 2026-11-15 21:51:52 +00:00
Sign in to join this conversation.
No reviewers
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!1550
No description provided.