Send the link details that help isolate a fault
The most useful first message describes what failed, what still works and what changed. A photograph of the label helps identify the module, but it cannot replace host details and error evidence. Avoid sending login credentials or private configuration secrets.
Identify the affected link
Provide the module and cable identifiers, both host models, firmware and port configuration. State whether the failure affects one channel or several.
Describe the symptoms
Report link state, timing, temperatures, DOM readings and error counters where available. Note recent cabling, firmware or port changes.
Record controlled comparisons
If your maintenance process permits, compare a known-good port or module and record what follows the fault. Do not disrupt a production link solely to fill this checklist.
Your next step
Send the evidence already available and your operational constraints. Further checks should be agreed with the system owner; a remote description cannot by itself establish the failed component or warranty responsibility.
Read PAM4 and FEC troubleshooting guidance · Browse product families · Contact PhotonVerge