Engine: a CFP2 cage, so optical transport stops apologising for its own specs #1213
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!1213
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/media-cfp2"
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?
The OptiXtrans E6616 and E6608 have 200G line ports. There was no CFP cage in the engine, so those ports were modelled as QSFP56 and the note said: "the physical module is CFP2, so a lab planning optics should order CFP2, not QSFP56."
A spec telling the reader not to believe the spec is worse than a missing entry - a lab that wires the modelled port with the modelled module builds a link the hardware cannot build, and the simulator would have accepted it.
cfp2is now a cage: 100/200G, optical, media200gbase-fr4/dr4/100gbase-lr4/40gbase-lr4, no DAC (it is a line-side module, not a patch lead). 40G because a CFP2 port takes the older optic; 100G because a muxponder board has a 100G line mode.The interesting part is the refusal
CAGE_MATE.cfp2contains exactly one entry:cfp2. This is the first cage in the catalogue where two cages carry the same rate and must still refuse each other - a 200G CFP2 module is roughly four times the footprint of a 200G QSFP56 and latches differently. "The rates match, so it fits" is wrong here, and the validator says so by name:Only CFP2
CFP, CFP4 and CFP8 are real standards, one line of table each. None is declared: no device uses them yet, and the cable matrix reports a declared-but-unreferenced cage as unused - speculative vocabulary makes that signal useless. When a box needs CFP8 it is a one-line addition plus its matrix row.
Changed with it
qsfp56tocfp2, apology paragraphs replaced with the refusal they should always have had.test/cable-matrix.test.js:cfp2 x cfp2accepts,cfp2 x *refuses.scripts/audit-port-types.js:cfp2joinsFIBRE_CAGES.docs/CONNECTORS.md: table row plus §4.5 "CFP2 is not a large QSFP". While there, fixed a stale count indocs/PHYSICAL_LAYER.md- it claimed "18 of them" when the engine has had 27 cages for a while. Numbers in prose rot; that sentence no longer carries one.30 checks in
test/media-cfp2.test.js, including the E6616 line ports cabling to each other at 200G and refusing a QSFP56 port with both cage names in the message. Suite: 117 suites, 5,435 assertions, 0 failed.471c4b67bd1d2bbf6b12