A reference post on the memory layout used when programming transceivers: SFP blocks A0h (serial ID/vendor, often write-protected) and A2h (diagnostics, page-select byte 7Fh, page 00h/01h user-writable); QSFP block A0h with page-select 7Fh, page 00h identity write-protected and page 03h user…
A QSFP112 400G SR4 module in a ConnectX-7 (MCX755106AC-HEAT) with an MPO-12 Type-B cable showed module state Ready and data path DPActivated, but mlxlink --showmodule reported State = Disable, Supported Cable Speed = 0x00000000, Compliance = Unspecified/Undefined, Power Class 1.5 W (too low for…
I do small batches of module recoding for integrators, and until now everything on my bench has been SFP-shaped: read the 256 bytes at A0h with the serial ID in the first half, read A2h for the diagnostics and thresholds, write the identification block, done. A customer has now turned up with 100G…
Our inventory tooling walks every switch and records vendor, part number and serial for each pluggable straight out of the SONiC CLI. It works everywhere except one batch of QSFP-DD modules, where the identity fields come back mangled and the asset database fills up with junk. Switch: SONiC…
We are bringing up a pair of AS9716-32D as a 400G spine in the lab, on a community SONiC image with the PDDF platform layer. The optics are not the problem, the peer links fine, but everything the switch says about them is wrong. Edgecore AS9716-32D (x8664-acctonas971632d-r0) community SONiC build…
