6/14/2023 8:47 AM | |
Joined: 5/6/2022 Last visit: 8/13/2024 Posts: 439 Rating:
|
Hi MHARITZ, In order to learn more about a correct diagnosis, could you give us some more information? You can also attach the diagnostic buffer in .txt format to find out which CPU 400 model you have, its version and the rest of the codes that appear. Do you have a redundant system? In principle, what this error indicates is that the hardware is not defective (no hardware replacement necessary), and no firmware update is necessary. The CPU handled the effect in the correct way. In terms of behavior, it is not a defect. No hardware is broken, there is no malfunction in the firmware. This is a completely normal, desired system behavior. The CPU detects a change in memory (bit tipper) and tries to react before something goes wrong. In a redundant AS (two red H CPUs), one of the CPUs can boot at any time without disturbing the AS functionality. This is normal system behavior. Best regards! |
If this Information really helps, you could use the Rate function |
|
6/14/2023 9:53 AM | |
Joined: 6/14/2023 Last visit: 6/23/2023 Posts: 3 Rating:
|
Hi Elon; First of all thanks for your answer, I've attached the diagnose. We have redundant system. On 19thof April at 06:31 the CPU went to stop mode and tried restart to remove data inconsistency, We had a problem with communication wire in the other CPU, intermittently loosing communication some days before, I don't know if this is the root cause. AttachmentDiagnose.txt (478 Downloads) |
Follow us on