FortiSwitch
FortiSwitch: secure, simple and scalable Ethernet solutions
laltuzar
Staff
Staff
Article Id 409082
Description

 

This article describes the steps to recover the service on a FortiSwitch, showing several errors even after rebooting it.

 

Scope

 

FortiSwitch OS.

 

Solution

 

FortiSwitch shows the following logs over and over when connected via console port:

 

1440:[/bin/ctrld] libsw cpssd not responding Connection refused (msg=19)
1440:[/bin/ctrld] libsw cpssd not responding Connection refused (msg=19)
1440:[/bin/lldpmedd] libsw cpssd not responding Connection refused (msg=19)
1440:[/bin/lldpmedd] libsw cpssd not responding Connection refused (msg=51)
1440:[/bin/lpgd] libsw cpssd not responding Connection refused (msg=12)

 

These messages might indicate a failure on the FortiSwitch to boot up correctly. The firmware partition might have been corrupted. See the attached example-output.zip file with an example output.

 

To recover the service, reboot the FortiSwitch and load the latest firmware via TFTP directly. See this KB article to get the details on how to do so: Technical Tip: Factory reset a FortiSwitch-1024D; the procedure is the same. Note that it will be needed to reconfigure the switch completely. Loading a previous backup configuration might work, but it is not recommended.

 

If nothing of this works, open a new ticket to TAC with the serial number of the FortiSwitch. Attach the firmware installation log. See this KB article to save the output on a .txt or .log file using Putty: Technical Tip: How to create a log file of a session using PuTTY also, upload a video showing this behavior and the serial number of the device.