Jump to content
XPEnology Community

aw5186

Rookie
  • Posts

    4
  • Joined

  • Last visited

Everything posted by aw5186

  1. Important Note: After testing, although the HA status is shown as failure, all the Settings and data can be synchronized successfully, and automatic switching can be achieved, but manual switching is not possible.
  2. Through continuous testing, we finally found out the reason: It is caused by the CPU architecture, because the Intel "Ivy bridge" generation architecture of e52680 V2 is too low, resulting in abnormal operation of the syntax high availability process The preliminary judgment is that the syntax high availability uses the new AES encryption algorithm instruction set, but Ivy bridge architecture does not have this instruction set,but, Looking up the data, it is found that e52680v2 supports AES Ni advanced instruction set, so it is not the cause of this instruction set. Finally, it is determined that the operation failure of syntax high availability is caused by ivy bridge architecture, After I set the VMware EVC mode of DSM VM of HP DL 380g9 to Intel "Ivy bridge" generation, Host a VM DSM and host B VM DSM failed to create synchronization high availability, The system internal service [syntax cron daemon] failed to start After canceling VMware EVC Hosta -- host B succeeds, hostb -- Hosta fails; Cancel VMware EVC mode successfully hostA --- host B Switch active server to passive server, hostb -- host a failed
  3. Hi, I have the exact same issue. What's weird about it, is that the actual replication is happening. Just the UI is not representing that. esxi 6.5-6.7u3 all test host A dell r720xd e5-2680 v2 host B hp dl380g9 e5-2680 v4 host C hp dl80g9 e5 2604 v3 ds3615xs,ds3617xs, 1.03b load dsm 6.2.3 hostA --- hostB success; hostB ---host A fail host B --- host C or host C ----hostB all success hostA --- host C success; host C---hostA fail Try to enable the host B VMware EVC mode as Intel "Ivy bridge" generation, which is consistent with the architecture of host a, hostA --- hostB ;hostB ---host A all fail。 cluster.log corosync.log ha.daemon.log ha.daemon.record lsyncd_system_sync.log
×
×
  • Create New...