Troubleshooting Tip: Failed DIAG-CONTROL check sequence

sachitdas_FTNT · ‎06-01-2023

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

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" 8: 2022-03-21 18:01:40 log_id=0100001055 type=event subtype=link pri=notice vd=root action="physical-port-change" user="dmid" status="None" switch.physical-port="port26" msg="port26 Module re-initialized to recover from ERROR state." 9: 2022-03-21 18:01:40 log_id=0100001055 type=event subtype=link pri=notice vd=root action="physical-port-change" user="dmid" status="None" switch.physical-port="port25" msg="port25 Module re-initialized to recover from ERROR state."