H3C ONEStor 3.0 (independent deployment)
H3C X10000 2.0
ONEStor 3.0 E21XX, R21XX, and all versions before E3116 in the E31XX series (excluding E3116 version);
All versions before X10000 2.0 R1233 (excluding R1233 version).
When ONEStor and X10000 storage hosts can access the Internet directly, if there is a certain difference between the host time and the Internet time, the host will directly synchronize the Internet time, which will cause the storage cluster clock to change. When the changing time is longer than 7 seconds, it will cause the storage cluster state to be abnormal, resulting in service interruption.
The operating system of ONEStor and X10000 hosts has its own clock synchronization service (Chrony service), which is ON by default. When the cluster is directly connected to the Internet, one or more of the following situations will occur:
Case 1: the Chrony service will automatically synchronize the Internet clock;
Case 2: the storage cluster uses NTP for clock synchronization, but when the Chrony service and NTP are in effect at the same time, the clock synchronization will be chaotic;
Case 3: if the local clock of the host changes for more than 7 seconds, it will lead to abnormity of storage function.
For clusters that cannot be upgraded recently, please manually shut down the Chrony service on each server as following steps.
SSH to the host operating system of ONEStor or X10000.
Using systemctl status chronyd.service command to check whether the Chrony service is down. The results below indicates that it is not turned off.
If he Chrony service is up, use the command systemctl stop chronyd.service and systemctl disable chronyd.service to close the service. Use systemctl status chronyd.service to check whether the service was successfully shut down. The results below indicates that it has been turned off.
Please upgrade ONEStor 3.0 to R2131 and later (version to be released); or upgrade it to E3116 and later versions.
Please upgrade X10000 2.0 to R1233 and later versions.