In the Pre-installation Scenario, After the Cluster Certificate Is Replaced and a Node Is Added, a Communication Exception Alarm Is Generated

Problem Information

Problem Symptom

In a cluster where certificates have been replaced, a communication exception alarm is generated and not cleared for a long time when a node in preinstallation mode is added.

Problem Diagnosis

1. Confirm that a certificate of the cluster has been replaced.

2. Confirm that the node to be added is in the preinstallation mode.

3. Confirm that a communication exception alarm is generated and not cleared for a long time.

Causes

The node in preinstallation mode cannot detect that the cluster certificate has been replaced. As a result, the communication cannot be established.

Solution

1. Log in to the active FSM node and switch to user root. For versions earlier than 8.1.0, run the cd /opt/fusionstorage/deploymanager/clouda/bin command to go to the directory. For 8.1.0 and later versions, run the cd /opt/fusionstorage/deploymanager/clouda/script command to go to the directory. Then, run the bash manul_collect_cert.sh collect command.

2. Log in to the pre-installed node and switch to user root. For versions earlier than 8.1.0, run the cd /opt/fusionstorage/deploymanager/clouda/bin command to go to the directory. For 8.1.0 and later versions, run the d /opt/fusionstorage/deploymanager/clouda/script command to go to the directory. Then, run the bash manul_collect_cert.sh download command.

3. Log in to the pre-installed node and switch to user root. For versions earlier than 8.1.0, run the cd /opt/fusionstorage/deploymanager/clouda/bin command to go to the directory. For 8.1.0 and later versions, run the cd /opt/fusionstorage/deploymanager/clouda/script command to go to the directory. Then, run the bash manul_collect_cert.sh replace command.

4. Log in to DeviceManager and add the node.

Check After Recovery

N/A

Suggestion and Summary

N/A

Applicable Versions

FusionStorage 8.0.1.5; OceanStor_100D 8.0.3