KAMN347-E

After an error was detected on the host indicated by the host name and a system reset was initiated, an error occurred during reset processing. If the public cloud environment is not used, the message KAMN621-E or KAMN624-E is output before this message.

         aa....aa: Host name

               S:

                  If the public cloud environment is not used, processing differs depending on the method used to protect data on a shared disk.

                        For a host reset, the system stops hot-standby switchover processing.

                        For a hot-standby switchover via hybrid fencing, the system continues hot-standby switchover processing and performs SCSI reservation processing.

                  If the public cloud environment is used, the system stops hot-standby switchover processing.

               O:

                  Contact a system administrator.

               Action:

                        In any environment other than a public cloud environment:

                           Determine the reason the system could not reset based on the error details in the KAMN621-E or KAMN624-E message.

                        In the AWS environment:

                           There is a possibility that the AWS CLI could not execute on AWS. See "[AWS] Configuring AWS" in the manual For Public Cloud Systems HA Monitor Cluster Software Guide, and revise the settings to correct errors. If you cannot determine why the system cannot be reset, see /opt/hitachi/HAmon/spool/cloud/moncld_fstop_forced-stop-target-instance-ID.log and determine the cause of the error.

                        In the Azure environment:

                           There is a possibility that the Azure CLI could not execute on Azure. Check whether communication to the endpoint is possible. If you cannot determine why the system cannot be reset, see /opt/hitachi/HAmon/spool/cloud/moncld_fstop_forced-stop-target-VM-resource-ID.log and determine the cause of the error.

                        In the OCI environment:

                           There is a possibility that the OCI CLI could not execute on OCI. Check whether communication to the endpoint is possible. If you cannot determine why the system cannot be reset, see /opt/hitachi/HAmon/spool/cloud/moncld_fstop_forced-stop-target-instance-OCID.log and determine the cause of the error.