| Before v6.4.8 (FortiGate-7K) SD-WAN information was populated across all FPMs/FPCs in the system. Now, from v6.4.8 and later, only the FPM master has the SD-WAN member and SD-WAN health-check information: diagnose load-balance status Slot: 1 Module SN: FIM04ET031000XXX
FIM01: FIM04ET031000XXX
Primary FPM Blade: slot-3 < --- Slot 3: FPM20ET02890XXXX
Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Slot 4: FPM20ET02890XXXX
Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Slot 5: FPM20ET02890XXXX
Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Slot 6: FPM20ET02890XXXX
Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running" On the above output, FPM slot-3 is the master FPM so SD-WAN information is only displayed from that blade: FGT-7060E[FIM02] (root) # diagnose sys sdwan health-check ==========================================================================
Slot: 1 Module SN: FIM04ET031000XXX ==========================================================================
Slot: 3 Module SN: FPM20ET02890XXXX Health Check(ICMP_Probe):
Seq(3 1-B2/1): state(alive), packet-loss(00.000%) latency(84.121), jitter(41.187), mos(3.902), bandwidth-up(9970029), bandwidth-dw(9844504), bandwidth-bi(19814533) sla_map=0x1
Seq(1 1-B2/2): state(alive), packet-loss(00.000%) latency(65.136), jitter(41.137), mos(3.902), bandwidth-up(9970029), bandwidth-dw(9844504), bandwidth-bi(19814533) sla_map=0x1
Seq(2 1-B2/3): state(alive), packet-loss(05.000%) latency(110.210), jitter(52.977), mos(3.902), bandwidth-up(9970029), bandwidth-dw(9844504), bandwidth-bi(19814533) sla_map=0x1 Health Check(SDWAN_Internet):
Seq(3 1-B2/1): state(alive), packet-loss(00.000%) latency(81.543), jitter(60.623), mos(3.935), bandwidth-up(9970029), bandwidth-dw(9844504), bandwidth-bi(19814533) sla_map=0x1
Seq(2 1-B2/3): state(alive), packet-loss(05.000%) latency(63.987), jitter(99.574), mos(3.601), bandwidth-up(9973474), bandwidth-dw(9841698), bandwidth-bi(19815172) sla_map=0x1
Seq(1 1-B2/2): state(alive), packet-loss(00.000%) latency(120.413), jitter(60.623), mos(3.935), bandwidth-up(9970029), bandwidth-dw(9844504), bandwidth-bi(19814533) sla_map=0x1 ==========================================================================
Slot: 4 Module SN: FPM20ET02890XXXX ==========================================================================
Slot: 5 Module SN: FPM20ET02890XXXX ==========================================================================
Slot: 6 Module SN: FPM20ET02890XXXX ==========================================================================
Current slot: 2 Module SN: FIM20ET28000XXX As an alternative, it is possible to access directly to FPM using the CLI:
execute load-balance slot manage <ID>
Once there, execute the same SD-WAN commands to see the information. Related document: Managing individual FIMs and FPMs from the CLI | 
