| The following CLI command reveals critical information about the transceiver modules installed in each interface, including vendor details, part numbers, and compliance standards.
LAB1 # get sys interface transceiver
Interface port17 - Transceiver is not detected.
Interface port18 - Transceiver is not detected.
Interface x1 - SFP/SFP+/SFP28, compliance is unspecified
Vendor Name : Optech
Part No. : OPSFPP-T-03-PEB
Serial No. : S210700370110
Interface x2 - SFP/SFP+/SFP28, compliance is unspecified
Vendor Name : Optech
Part No. : OPSFPP-T-03-PEB
Serial No. : S210700370110
Interface x3 - SFP/SFP+/SFP28, compliance is unspecified
SFP/SFP+ Temperature Voltage Tx Bias Tx Power Rx Power
Interface (Celsius) (Volts) (mA) (dBm) (dBm)
------------ ------------ ------------ ------------ ------------ ------------
x1 N/A N/A N/A N/A N/A
x2 N/A N/A N/A N/A N/A
++ : high alarm, + : high warning, - : low warning, -- : low alarm, ? : suspect. The above error may be observed if:
- SFPs do not fully support or expose all standard data fields FortiGate expects, especially compliance codes and DOM.
- The DAC cable is supported by Fortinet products or have limited compatibility with non-certified optics.
In this case, it is required to check the compatibility lists of both SFP/SFP+/SFP28/QSFPs and fiber optic equipment.
Related article:
Technical Tip: How to check SFP transceiver module serial number and power
| 
