You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to get access to parsed SFF-8472 style DDM from NICs (and optics) that support it. You can already get the raw, unprocessed binary data from ModuleEeprom(intf). Parsing most of the data is relatively straightforward (mostly some uint8, uint16, some fixed length strings, and a bunch of enums) but several of the fields are in odd units, like optic temperature in 1/256 °C, or rx/tx power in 100s of nanowatts (when dBm is much more common.)
I think this is the right place to do that parsing, rather than pushing it to anything that uses this module.
The text was updated successfully, but these errors were encountered:
I would like to get access to parsed SFF-8472 style DDM from NICs (and optics) that support it. You can already get the raw, unprocessed binary data from ModuleEeprom(intf). Parsing most of the data is relatively straightforward (mostly some uint8, uint16, some fixed length strings, and a bunch of enums) but several of the fields are in odd units, like optic temperature in 1/256 °C, or rx/tx power in 100s of nanowatts (when dBm is much more common.)
I think this is the right place to do that parsing, rather than pushing it to anything that uses this module.
Hello.
Could you please tell me how to parse the raw data from ModuleEeprom correctly?
I would like to get access to parsed SFF-8472 style DDM from NICs (and optics) that support it. You can already get the raw, unprocessed binary data from
ModuleEeprom(intf)
. Parsing most of the data is relatively straightforward (mostly someuint8
,uint16
, some fixed length strings, and a bunch of enums) but several of the fields are in odd units, like optic temperature in 1/256 °C, or rx/tx power in 100s of nanowatts (when dBm is much more common.)I think this is the right place to do that parsing, rather than pushing it to anything that uses this module.
The text was updated successfully, but these errors were encountered: