Juniper EX2300: four more models, a 740 W budget one Juniper guide calls 750 W, and two capacity figures Juniper disagrees with itself on #1564
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1564
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "catalogue/1115-2326"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
The Juniper EX2300 access-switch family: six models now carry their real port layout, PoE budget and cage, up from two thin entries and a portless stub.
Also removed
devices/juniper/ex2300.json: modelEX2300is not a SKU, it carried the labelEX2300-24T(so a correct 24T spec collided with it by label) and it declared no ports at all.Two vendor documents contradict each other, and both are recorded
fabric.note.Modelling decisions worth a reviewer's eye
engine/media.jsmarks 10GBASE-T as carrying no power, and every one of those ports is a PSE port, so a 10G model speed would silently strip PoE. The 5G/10G rates are recorded innotes.Drive-by: a red suite on main
test/spec-vs-description.test.jswas failing onorigin/mainbefore this branch: the four Edgecore AS4610 descriptions from #1555 claimed "2x 20G QSFP+" stacking cages that the same PR deliberately did not model as ports, and the test counts that claim. Reworded to "two 20G QSFP+ …" in the four specs and inresearch/incoming/devices-edgecore-as4610.json; no port data changed.Sources (every field carries one)
juniper.net/.../ex2300-line-of-ethernet-switches-datasheet.pdfpath now 404s.Validation
node scripts/syntax-check.js— 327 files OKnode scripts/audit-port-types.js— 2081 models / 21845 ports, 0 offending devices, 0 offending ports--apply --upgrade— 4 added, 2 upgraded (EX2300-24Tand-48Tdetail 0 -> 10), capability tripwire silent apart from the expected802.3af/802.3at"kept as declared" notes, which the engine does not implementnpm run regen:registry-doc— 2,078 -> 2,081 models, switch 310 -> 313npm test— 257 suites, 9371 assertions, 0 failedNot verified
The EX2300 family was in the catalogue as two thin entries (24T, 48T) plus a portless stub; the eight-SKU range is now six models with their real port layout, PoE budget and cage. New: EX2300-24P, EX2300-48P, EX2300-24MP, EX2300-48MP. Corrected: EX2300-24T and EX2300-48T (no connector on the access ports, no cage on the uplinks, no PoE statement, no source). Removed: devices/juniper/ex2300.json - model "EX2300" is not a SKU, it carried the label "EX2300-24T", and it had no ports at all. Two vendor documents contradict each other and both are recorded rather than smoothed over: - PoE budget for the 48P and 48MP: 740 W in the datasheet, the power-supply table and the system-overview table; 750 W in PoE User Guide Table 5. 740 W is modelled, because 48 x 15.4 W = 739.2 W. - Switching capacity for the multigigabit models: the datasheet groups the 24MP with 128 Gbps and the 48MP with 176 Gbps, while the per-model hardware specs give 152 and 264 Gbps. The datasheet figure is modelled and the conflict is named in each spec's fabric note. Also fixes the four Edgecore AS4610 descriptions from #1555, which claimed "2x 20G QSFP+" for stacking cages the same PR deliberately did not model - test/spec-vs-description.test.js counted them and the suite was red on main.b7813919931d6030a589This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
1d6030a589d8a9229dc2d8a9229dc2e74a7f5689This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.
This branch conflicts with
main, so it was not rebased:A conflict is a decision about behaviour rather than a mechanical fix, so this is left for a human. Rebasing by hand and force-pushing will let the automation pick it up again.