FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
Renante_Era
Staff
Staff
Article Id 275124
Description This article describes how to troubleshoot when a FortiGate chassis FPC Blade Slot's Status is Dead, and the Status Message is 'Waiting for management heartbeat'.
Scope FortiGate Chassis.
Solution
  1. Show FPC Blade Slot's status using the following commands and check if the Status is Dead, Status Message is 'Waiting for management heartbeat'.

 

diagnose load-balance status

MBD SN: F6KF31T018900000
Master FPC Blade: slot-1
Slot 1: FPC6KFT018900000
Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Slot 2:
Status:Dead Function:Active
Link: Base: Up Fabric: Down
Heartbeat: Management: Failed Data: Failed
Status Message:"Waiting for management heartbeat."

 

  1. Open the FortiGate GUI and check the event messages (mgmt-vdom -> Events -> System events).
  2. Confirm the LED indicator on the affected blade and note the LED color.
  3. Check all cable and fiber connections to ensure they are intact.
  4. Try power cycling the affected FPC Blade Slot several times and check if the console logs indicate that the FPC Blade is coming up.

 

Open two SSH connections to FortiGate:

 

1st SSH window:

 

c g
execute system console-server connect 5 
<- Where 5 is the affected FPC Blade Slot number. Any output should be visible.

 

2nd SSH window: If the FPC is frozen, an NMI reset can be attempted to retrieve useful data. SSH outputs should be saved and could be shared with technical support. Once it is powered off/powered on from the 2nd SSH, some logs on the first SSH should be visible. Check the logs to see if it completes the boot process or if it gets stuck during booting.

 

c g

 

Perform an NMI reset first. If this does not help, perform a cold reboot.

 

execute load-balance slot nmi-reset <slot number>.
execute load-balance slot power-off <slot number>.
execute load-balance slot power-on <slot number>.

 

If the console log output is similar to 'scsi_read[1335]scsi error' then try to reformat and re-image the affected FPC Blade:

 

execute load-balance update image <slot number>

 

See the following article for detailed steps: 

Technical Tip: Procedure to download image on FPC from default TFTP server running on MBD.

 

Alternatively, create a ticket and upload the output of the above commands as well as the output of the following commands:

 

get system status
diagnose debug crashlog read
get sys performance status
diagnose sys confsync stat 
<----- Checksum.
diagnose sys confsync showcsum | grep -i "slot\
diagnose sys confsync status | grep in_sync
diagnose sys confsy show | grep all 
<----- Show all checksum.
diagnose sys ha status
diagnose sys ha checksum show
diagnose sys top 1 40 5
diagnose hardware sysinfo conserve
diagnose hardware sysinfo slab
get hardware memory
diagnose sys top-mem 40
diagnose debug crashlog read
diagnose sys session full-stat
diagnose sys session stat
diagnose hardware sysinfo shm
diagnose hard sysinfo interrupts
diagnose ips session performance
diagnose test application ipsmonitor 1
diagnose ips session list
diagnose sys mpstat
diagnose debug comlog info
diagnose debug comlog read