3/19/2023 0 Comments Bitfield checksum mismatchThe command is ' diag sys ha checksum show '.) (NOTE: From 5.6 and above, levels no longer exist. can be any value from 01 to 04 (the leading zero is important). The following is the syntax for the command for individual VDOM: In a multi-VDOM environment, the above commands can be executed on a global level and for each VDOM. (NOTE: From 5.6 and above the command is ' diag sys ha checksum show global system.admin'.) This will also show the root cause of the mismatch as shown below: Removing that dashboard from admin user configuration will cause the HA checksum to sync again.Īlternatively, use the command ' diagnose system ha showcsum ' to find out the source of the mismatch in the admin section. In the above example, the configuration checksum is mismatched in 'Admin Settings'. System.ha: a4de1e0fcd4add6c764ed10a61b9d022Ĭheck the configuration parameter where the checksum mismatches. Verify the cluster-csum as mentioned above to see if the cluster is synchronized.Ģ) If the cluster is still not synchronized, execute the following command on both master and slave units and compare the output: Checksums are cumulative and so all checksums which follow the first out-of-sync object will also be incorrect.ġ) Execute the following command on the slave unit to manually synchronize it with the master unit: To identify which object(s) are not synchronized, it is typically most efficient to find the first out-of-sync object and correct it. If the checksum does not synchronize as shown in the output above, take the following steps in this article to synchronize the cluster checksums. The checksum for both of the units should match for the HA to work properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |