OPERATIONAL DEFECT DATABASE
...
...
BugZero found this defect 91 days ago.
The backup master cluster member of a T20/T40/T55 FireCluster might suddenly become inactive and not allow direct FSM connections. This issue might be caused by a mismatch of the Event Log hash between cluster members. To verify the issue: Use Putty to connect to the cluster IP address on port 4118.Log in with the admin user.Run the "show cluster sync cluster" command.Check the status of the evtlog hash. WG<master>> show cluster sync cluster--Sync Status--Result of System Hash check between Member1_SN and Member2_SN**system Hash: Mismatch. a2f11f1a5af488feed7be3ab9e75b75c110cfa2f, 0f92050aa5d64f652e7f4f583cc0c8d7163d35fa....evtlog: Mismatch **system hash mismatch is expected here
Automatic failovers through FireCluster events should continue to function normally. The inactive status will transfer to the new Backup Master cluster member. To try to resolve the issue temporarily, reset the inactive cluster member to factory-default settings and use the FireCluster tools to rediscover the cluster member. For more information, go to https://www.watchguard.com/help/docs/help-center/en-US/Content/en-US/Fireware/ha/cluster_discover_member_wsm.html.
