IBM Storwize V7000 Unified Problem Determination Manual page 55

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.
v The cluster_ip under sainfo lsservicestatus should match the Primary IP (that
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
error_data
01-1 00000200A4E008BA Cluster_9.71.18.184 1
01-2 00000200A4E008BA Cluster_9.71.18.184 2
sainfo lsservicestatus
panel_name 01-1
cluster_id 00000200a4e008ba
cluster_name Cluster_9.71.18.184
cluster_status Active
cluster_ip_count 2
cluster_port 1
cluster_ip 9.71.18.184
cluster_gw 9.71.18.1
cluster_mask 255.255.255.0
When you can ssh to the storage system IP then use the lssystem CLI command
on the storage system CLI to show you what it thinks that its system IP address is:
IBM_2076:tbcluster-ifs4:superuser>lssystemip
cluster_id cluster_name
IP_address_6 prefix_6 gateway_6
00000200A6402C08 tbcluster-ifs4 local
00000200A6402C08 tbcluster-ifs4 local
Check that these IP addresses and sub net mask are as expected. Use the
chsystemip CLI if you must change anything. Use ping to check the path back to
the management IP address.
cluster_name node_id node_name relation node_status
location port_id IP_address subnet_mask
1 9.71.18.180 255.255.255.0 9.71.18.1
2
Chapter 3. Getting started troubleshooting
node1 local Active
node2 partner Active
gateway
31