Hello, everyone!
This is a case about the VBS process exception alarms reported by nodes, not in the cluster are displayed on DeviceManager.
Basic Information
Item | Description |
Storage type | Distributed storage |
Product version | FusionStorage 8.0.0; FusionStorage 8.0.1; OceanStor 100D 8.0.2 |
Problem type | Alarms |
Keyword | Unexpected process exit alarms; Nodes not in the cluster |
Symptom
After the FSA node where the communication is abnormal is forcibly deleted and removed from the cluster, if the FSA node is recovered, an alarm indicating the unexpected exit of the VBS process on the FSA node is reported on DeviceManager.
Cause
1. When the FSA node where the communication is abnormal is forcibly removed, processes on the node cannot be uninstalled.
2. The node has been removed from the cluster so that the VBS process on the node cannot be started normally. However, the SNM restarts the VBS process on the faulty node repeatedly and identifies it as in an abnormal state. As a result, an alarm indicating an abnormal VBS process is reported.
3. After the communication of the faulty FSA node is recovered, the reported alarm will be displayed on DeviceManager.
Solution
1. Log in to the faulty FSA node and run the bash /opt/fusionstorage/deploymanager/clouda/clear_all_for_fsa_node.sh command to clear the environment.
2. Manually clear the process exception alarm on DeviceManager.
This is my solution, how about yours? Go ahead and share it with us!
