Verifying the configuration and the status of the units in the cluster
Use the following command from the FortiController CLI to verify that the primary FortiController can communicate with all of the workers and to show the status of each worker. For example, for a cluster that includes 2 workers the command output would be the following if the cluster is operating properly:
get load-balance status
ELBC Master Blade: slot-3
Confsync Master Blade: slot-3
Blades:
Working: 3 [ 3 Active 0 Standby]
Ready: 0 [ 0 Active 0 Standby]
Dead: 0 [ 0 Active 0 Standby]
Total: 3 [ 3 Active 0 Standby]
Slot 3: Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Slot 4: Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
Slot 5: Status:Working Function:Active
Link: Base: Up Fabric: Up
Heartbeat: Management: Good Data: Good
Status Message:"Running"
The command output provides the same information as the Load Balance > Status page, including the slot that contains the primary unit (slot 3), the number of workers in the cluster, the slots containing all of the workers (3, 4, and 6) and the status of each. Status information includes the status of the connection between the FortiController and the base and fabric backplanes, whether the heartbeat is active, the status of the FortiController and the data processed by it. The status message can also indicate if the FortiController is waiting for a fabric connection or waiting for a base connection.
You can also use the following commands to display detailed session aware load balancing diagnostics:
diagnose SLBC {dp | tcam-rules}
The dp option provides diagnostics for the DP processors and the tcam-rules option provides diagnostics for content aware routing rules (TCAM).