A kernel panic can point to a software defect which should be reported to Fortinet engineering via a technical support ticket. When you open a support ticket it can be verified if there is already a solution for this problem. Either the issue is already known and fixed, still worked on, or the support engineer can file a new report to the developers for review.
It is advised to enable kernel debugging to capture a kernel backtrace in case the device has another kernel panic after any firmware image is re-flashed. Run via the console port with a client connected that has logging enabled: # diagnose debug reset # diagnose debug kernel level 4 # diagnose debug console timestamp enable # diagnose debug duration 0 # diagnose debug enable
And let it keep on running until another kernel panic occurs.
In rare cases the kernel panic can also be caused by a hardware defect, i.e. broken memory.
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.