Description | This article describes how to fix an error seen on FortiSwitch logs: 'failed DIAG-CONTROL Check Sequence'. |
Scope | FortiSwitch version 6.4.x and above. |
Solution |
If the SFP ports repeatedly go 'Up' and 'Down' due to the error 'failed DIAG-CONTROL Check Sequence', perform the following checks
1) In the FortiSwitch CLI, collect the following logs:
execute log filter view-lines 1000 execute log display
Open the logs in a notepad file and search for any logs related to the port number. The following errors may be found with the SFP ports:
7: 2022-03-21 18:01:40 log_id=0100001054 type=event subtype=link pri=warning vd=root action="physical-port-change" user="dmid" status="None" switch.physical-port="port25" msg="dmi, port25, failed DIAG-CONTROL Check Sequence"
2) Check the output from the modules summary command.
get switch modules summary port25 INSERT SFP/SFP+ N 10G-Base-SR OK FINISAR CORP. FTLXxxxxx S210xxxx04-2
Although the module shows Finisar, verify the module vendor physically on the transceiver.
Explanation of error:This could be a fake module with EEPROM programmed to show as FINISAR.
Related articles: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.