A Raspberry Pi tool for SFP/SFP+ EEPROM: -r prints connector, transceiver spec, wavelength, vendor, part, serial, date and checksums; -d dumps the whole EEPROM; -c recaculates checksums and offers to write the correct value; -m reads DOM sensors (temperature, voltage, bias, power). A vendor variant…
A tutorial on recoding SFP/SFP+ EEPROM so a module works with a different vendor's switch. It uses a Cisco Twingig housing to reach the SFP I2C pins and wires four lines from the Pi GPIO (3.3 V, GND, SDA on GPIO3, SCL on GPIO5). It shows detecting 0x50 (and optional 0x51 DOM) with i2cdetect, points…
A small toolset that reads and writes SFP EEPROM over I2C with a CH341A programmer plus an I2C sniffer. The author found that sigrok/PulseView did not work with the analyser, that a v1.0.5 SFP coder firmware reported success while silently not writing the module (proven by I2C traces), and that the…
A notes repository on hacking SFP/QSFP EEPROM: SFPs present EEPROM at I2C 0x50 and DOM plus vendor/password features at 0x51; locked moddules need a 4-byte password written to 0x51 bytes 0x7b-0x7e. It lists several known unlock passwords and evaluates write methods (off-the-shelf coder limited to…
I keep a shelf of pulled SFPs at home and I would like to be able to read their EEPROM, repair a module whose checksum got mangled, and occasionally recode one for a switch that is picky about vendor strings. Buying a commercial programmer for a handful of modules a year makes no sense here, so I…
We look after the switch management firmware on our own hardware, and ever since the SP/FPGA interface was changed from memory mapped buffers to a FIFO, the transceiver inventory has been coming back as junk on some ports. QSFP28 optics, all of them AFBR-89BDDZ out of the same batch reads go over…
I am writing a small poller that pulls temperature, voltage, bias and optical power straight off the modules on our whitebox boxes, so we get a trend line instead of someone eyeballing a link after it has already started erroring. The NOS prints pretty values, but I want the raw numbers with the…
In a NANOG discussion about vendor lock-in, an operator described two concrete failures. First, a third-party optic answered I2C reads too slowly; the switch vendor's polling code did not handle the timeout and crashed the linecard control plane, and the vendor refused to treat it as a bug because…
