Verifying optics on a switch

Once a module is in a port, each NOS has a command to show its identity and DDM. Use it to confirm the switch sees the module the way you expect — and to cross-check against what CodingBox read.

Commands by NOS

What to look for

• Identity — vendor name, part number and serial match what you intended.
• DDM — temperature, voltage, bias and optical power are within range (the switch reads the same SFF-8472 diagnostics CodingBox shows).
• Errors — an "unsupported transceiver" note points to vendor lock.

Cross-checking with CodingBox

Compare the switch output with the app's transceiver summary. If the switch disagrees with what CodingBox read on the bench, the difference is in how the switch interprets or gates the module — not in the module's memory.

DDM-specific commands per platform, ethtool raw dumps, SNMP OIDs and OpenConfig paths: Reading DDM with tools.

Configuring what you verified — speed, FEC, breakout, overrides per NOS: Port configuration recipes; why a platform rejected a module: How each NOS validates a module.

The same data over SNMP and streaming telemetry — MIB objects per vendor, OpenConfig transceiver paths, syslog messages to alert on: Management & monitoring; interface names used in these commands: Port naming & LEDs.