Question & Answer
What are the steps needed to perform Reset of DS3524 Storage Controller in IBM Smart Analytics Systems
In some cases, the situation may arise where Storage is responsible for poor performance in appliance. To recover from the performance issue which is related to Storage Controller showing message " Previously existing connections are missing " a reset may be required to clear the missing connections.
The controller reset the options vary depending on if you have GUI access and also on what level of Storage Manager that you are running.
1) The "reset controller" command can be run from the Storage Manager from the Enterprise Manager view (initial screen). Under the devices menu, select the subsystem where you want to reset the controllers with a single click. Then right mouse click and select the execute script button from the subsystem in question.
In the script execution window enter the command:
reset controller [a];
Then run tools / execute only.
Wait several minutes for the controller to reset and for the command to complete Run the same command for controller b,
i.e.: reset controller [b];
Then run tools / execute only
Again, it will take several minutes for controller B to complete. Then go to the next subsystem and repeat the above steps.
2) In the storage manager GUI there is a reset option. In the newer storage manager 10.8x the steps start with selecting the subsystem and going into the subsystem management view. Select the controller A. The under the menu select Hardware / Storage / Advanced / Reset and make sure that you select controller A. A confirmation dialogue will display detailing which controller will be reset, which should list controller A and not controller B. Once you confirm controller A is listed you can click ok to accept the warning and the controller will reset (the gears will spin for several minutes first).
Once complete (gears stop spinning), then we need to reset controller B. Select the controller B. The under the menu select Hardware / Storage / Advanced / Reset and make sure that you select controller B. A confirmation dialogue will display detailing which controller will be reset, which should list controller B and not controller A. Once you confirm controller B is listed you can click ok to accept the warning and the controller will reset (the gears will spin for several minutes first).
3) If you do not have access to the Storage Manager but you do have access to SSH to the management node on the cluster you can run the reset command.
Example -> This example uses the SMcli to send the command to the storage controller.
From the management node server you could run the following command :
usr/SMclient/SMcli 184.108.40.206 -p password -c "reset controller [b];"
In the above example "password" needs to be replaced by the current password in your environment. If there is no password remove '-p' and do not enter a password. 220.127.116.11 should be the ip address for controller A. You will need to determine the IP address of the controller A or B that you can access in the subsystem, and specify which controller you would like to reset in the reset command.
16 June 2018