Symptom:
A VBS node is faulty. When running a command on the CLI to enable the global performance switch, the switch is enables successfully, but an error message is returned, indicating that the command fails to be executed.
Diagnosis:
The change global_config general command fails to be executed. In fact, the function has been enabled successfully and has taken effect.
Cause:
A VBS node is faulty.
Solution:
1. Use PuTTY to log in to the FSM node where the change global_config general command is executed. Obtain the ismcli.log log file in the /var/log/oam/oam-u/ismcli/run directory.
2. Open the obtained ismcli.log log file, search for nok,cmd: change global_config general to find the command execution logs of command change global_config general, and locate the record that the command execution time is consistent with the action time.
Search for the latest /dsware/service/cluster/globalParametersOperation record and find the json record between /dsware/service/cluster/globalParametersOperation and nok,cmd: change global_config general. The content of response json is the execution details of the node.
3. Analyze the node execution details.
json:{"result":0,"detail":[{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.26.68"},{"errorCode":0
"description":"Successful","nodeMgrIp":"192.168.47.255"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.5.236"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.31.2"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.39.130"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.33.191"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.33.39"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.55.128"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.32.64"},
... ...
{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.38.23"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.4.48"},{"errorCode":50000013,"description":"The FusionStorage Manager node fails to communicate with the FusionStorage Agent node.","nodeMgrIp":"192.168.50.206"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.55.100"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.23.235"},
... ...
{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.18.183"},{"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.23.141"}]}
In the preceding json record, "result":0," indicates the overall command execution result, and a record in a coupe of {} is the detailed information about a node.
For example, {"errorCode":50000013,"description":"The FusionStorage Manager node fails to communicate with the FusionStorage Agent node.","nodeMgrIp":"192.168.50.206"} and {"errorCode":0,"description":"Successful","nodeMgrIp":"192.168.55.100"} indicate a success record and a failure record, respectively. The success log indicates that the command fails to be executed on the node whose IP address is 192.168.50.206, error code is 50000013, and the brief description of the cause is The FusionStorage Manager node fails to communicate with the FusionStorage Agent node. The failure record indicates that the command succeeds to be executed on the node whose IP address is 192.168.55.100, the error code is 0, and the execution result is Successful.
4. Locate the nodes whose errorCode is not 0 (the nodes on which the command fails to be executed).
