![]() However, the checksum for VDOM 'Cust-A' is different -> this needs to be checked. As you can see above, the 'global' and "root" contexts are synchronized. Daemon sync unable how to#= FGVM XXXXXXXXXX46 =Ĭust-A: 84 af 8f 23 b5 31 ca 32 c1 0b f2 76 d2 57 d1 bcĪll: 04 ae 37 7e dc 84 aa a4 42 3d db 3c a2 09 b0 60įurther on, the commands must be collected on both firewalls in order to compare the output.Ĭollecting this only on a single firewall is not relevant.( How to access the second firewall)Ĭheck the checksum mismatch in the above output, and then look for the cluster checksum and compare the output for mismatch. Prim-FW(global)# diag sys ha checksum cluster Slave : FGVM XXXXXXXXXX46, operating cluster index = 1 Master: FGVM XXXXXXXXXX44, operating cluster index = 0 Slave : Bkup-Fw, FGVM XXXXXXXXXX46, cluster index = 0 Master: Prim-FW, FGVM XXXXXXXXXX44, cluster index = 1 Ses_pickup: enable, ses_pickup_delay=disableįGVMX XXXXXXXXX44(updated 3 seconds ago): in-syncįGVM XXXXXXXXXX46(updated 4 seconds ago): in-syncįGVM XXXXXXXXXX44(updated 3 seconds ago): FGVM XXXXXXXXXX44 is selected as the master because it has the largest value of override priority. FGVM XXXXXXXXXX46 is selected as the master because it has the largest value of uptime. # get system ha status FGVMXXXXXXXXXX44 is selected as the master because it has the largest value of uptime. This article describes how to troubleshoot HA synchronization issue when a cluster is out of sync.įor a multi-vdom FortiGate, the following commands are used in 'config global' mode. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |