IBM Storwize V7000 Unified Problem Determination Manual page 97

[kd52y0g.ibm]$ lsstoragesystem
name primaryIP
StorwizeV7000 9.71.18.180 9.71.18.180 00000200A6002C08
EFSSG1000I The command completed successfully.
Check that these 5 or 6 IP addresses and sub net mask are as expected. Attempt
the lssystemip CLI command which will probably fail when the active
management node running on a file module attempts to ssh it to the storage
system CLI running on a control enclosure. For example:
[kd52y6h.ibm]$ lssystemip
EFSSG0655C Error in communication with the storage system.
Failed to open SSH connection
However, if this CLI command now works then the original problem with ssh to
the storage system CLI may have gone away. Otherwise, use ping to check the
network connections between the storage system and the file modules. It does not
work from the management CLI but it should work from the storage system CLI.
From an external computer ssh as superuser to the primary IP given by the
lsstoragesytem CLI. The IP that the active management node will be trying to ssh
commands to the storage system CLI. For example (default password is passw0rd):
ssh superuser@9.71.18.180
If you can not ssh to the storage system primary IP or secondary IP (that was
given by the lsstoragesystem CLI command) then follow the procedure to use the
USB flash drive to discover the state and settings of the Storwize V7000. Make sure
that there is no satask.txt file on the USB flash drive before you plug it into the
control enclosure.
Plug the USB flash drive into the control enclosure. The orange fault light should
go on for a short time only. (such as a slow blink for a few seconds) . Wait for the
orange fault light to go out then unplug the USB flash drive and plug it into
another computer so that you can look at the contents of the satask_results.html
file on the USB flash drive. The satask_results.html will contain the output from a
number of sainfo commands.
Check the following;
v The cluster_id under sainfo lsservicestatus should match the id (that was given
by the lsstoragesystem CLI command). Otherwise you may have plugged the
USB flash drive into the wrong control enclosure (such as one that is not part of
this Storwize V7000 unified system). The node_status should be active for each
node canister in the cluster under sainfo lsservicestatus. Otherwise follow the
service action under sainfo lsservicerecommendation.
The cluster_ip under sainfo lsservicestatus should match the Primary IP (that
v
was given by the lsstoragesystem CLI command). Otherwise investigate which
of the IP addresses is the correct one and make the other one match it. Refer to
the instructions later on this page if you need to change the storage system IP
address but can not log onto the storage system IP address to use the CLI.
This is an example of some of what the satask_results.html would contain on a
healthy storage system for you to compare to your results:
Thu Apr 19 08:23:42 UTC 2012
satask.txt file not found.
System Status
sainfo lsservicenodes
panel_name cluster_id cluster_name
error_data
01-1 00000200A4E008BA Cluster_9.71.18.184 1
secondaryIP id
node_id node_name relation node_status
node1
Chapter 3. Getting started troubleshooting
local Active
69