Adapter boards that, with a serial programmer, read and write transceiver memory across SFP, SFP+, SFP28, SFP112, QSFP/QSFP+/QSFP28, SFP-DD, QSFP-DD, XFP and OSFP. The software covers the MSA/CMIS memory maps, manages host/manufacturer passwords including brute-force search, changes…
Discussion of why re-coded modules fail Cisco validation: Cisco SFPs carry a unique signature tied to each serial number in bytes 96-127, and editing vendor name or serial makes the signature no longer match, so the switch rejects the module unless the signature is regenerated. Hardware involved…
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…
The poster programmed an OEM copper SFP with a 256-byte firmware dump; the switch recognised the type but the module received no data, whereas the original worked, and no password error appeared. It failed on several units. Hardware involved: OEM copper SFP (24C02 EEPROM). Reported…
Users needed to write to password-protected SFP/QSFP/XFP modules from HP, Cisco, Finisar and JDSU. The thread documents the two protection levels: a host/user password protecting the user-writable area (A2h offset 7Bh on SFP, A0h offset 7Bh on QSFP/XFP) and a manufacturer password protecting the…
The poster could read and write OEM SFP variants with a REVELPROG and SFP adapter but not three Finisar references, suspecting manufacturer password protection. Finisar only documents the MSA user-EEPROM password in datasheets, not the proprietary manufacturer password, and the same happened with…
