IBM Storwize V3500,3700 Service Manual

IBM Storwize V3500,3700

Canister	IPv4 address	IPV4 subnet mask	User/Password
Canister 1 (left)	192.168.70.121	255.255.255.0	superuser/passw0rd
Canister 2 (right)	192.168.70.122	255.255.255.0	superuser/passw0rd

・ Procedure: Understanding the system status using the LEDs

Repalcement

・ Replacing parts

Replacing a node canister

节点容器 1 无法正常启动，578 错误码，计划更换节点容器。

关闭节点容器 1 电源，更换新的节点容器（使用原有 CMOS 电池、容器电池和主机适配卡）

新节点容器 1 启动后，一直处于候选状态，未能自动加入群集。

群集管理 GUI 界面显示脱机状态，右键移除节点容器 1，状态仍旧处于候选。推测可能新 SD 卡里面的微码版本过高与当前运行的不匹配。

重新关闭节点容器 1 电源，将 SD 卡更换为原来的 SD 卡。

节点容器 1 正常启动，自动加入群集。

节点容器插入后，可能需要等 5-10 分钟，如果电池电量不足 (656)，还需要等电量充满才会启动，所以请耐心等待，期间不得随意移除节点容器。

Troubleshooting

Using a USB flash drive to Reset service IP address and superuser password

Use any USB flash drive that is formatted with a FAT32 file system on its first partition.

Create a file that is named satask.txt in the root directory.

satask chserviceip -serviceip 192.168.70.121 -gw 192.168.70.1 -mask 255.255.255.0
satask resetpassword

The fault light-emitting diode (LED) on the nodecanister flashes when the USB service action is being completed. When the fault LED stops flashing, it is safe to remove the USB flash drive.

Case: Cannot connect to the service assistant and sshd

节点容器 2 服务 IP 可 ping 通，服务助手 web 页面无法访，登录 ssh 输入密码后无反应，随后显示连接拒绝。
登录节点容器 1 的服务助手，切换到节点容器 2，在重新启动服务页面轮流重启 tomcat, cimserver, sshd 服务，故障依旧。
收集节点容器 2 日志分析，可能 tomcat 内存泄漏，导致其它服务无法正常提供访问。

└─$ find ./snap.single.*/ -type f ! -regex '.*\.\(gz\|xz\|zip\|tgz\|bz2\|tar\)$' | xargs grep --color=always -Ei 'a memory leak'
SEVERE: The web application [] appears to have started a thread named [ExecCommandExecuter.Reader] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [] appears to have started a thread named [stderr reader java.lang.UNIXProcess@41354135] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [] appears to have started a thread named [Thread-12] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [] appears to have started a thread named [TaskManager] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] appears to have started a thread named [ExecCommandExecuter.Reader] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] appears to have started a thread named [ExecCommandExecuter.Reader] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] appears to have started a thread named [stderr reader java.lang.UNIXProcess@4a2f4a2f] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] appears to have started a thread named [stdout reader java.lang.UNIXProcess@4a2f4a2f] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] appears to have started a thread named [process reaper] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] appears to have started a thread named [AbstractCommandExecuter.Executer] but has failed to stop it. This is very likely to create a memory leak.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
SEVERE: The web application [/service] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
./snap.single.UNKNOWN.250531.131500/dumps/cimom/tomcat.ws.7868362-2.3.log:SEVERE: The web application [] appears to have started a thread named [Thread-27] but has failed to stop it. This is very likely to create a memory leak.
./snap.single.UNKNOWN.250531.131500/dumps/cimom/tomcat.ws.7868362-2.3.log:SEVERE: The web application [/service] appears to have started a thread named [AbstractCommandExecuter.Executer] but has failed to stop it. This is very likely to create a memory leak.