IBM Storwize V7000 Unified Problem Determination Manual page 98

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
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.
IBM_2076:tbcluster-ifs4:superuser>ping 9.71.18.160
If the ping from the storage system CLI back to the management IP has 100%
packet loss then investigate the physical 1 Gbps Ethernet cabling and the
configuration of the Ethernet switch. Also check the Ethernet port LEDs on:
v Built in Ethernet port 3 of each file module
v Ethernet port 1 on each node canister of the control enclosure
If the ping from the Storwize V7000 to each file module has 0% packet loss, then
the ssh key should be reset. Follow the "Resetting the NAS ssh key for
configuration communications" on page 402 procedure in the Infomation Center to
reset the NAS key.
If you need to change the IP settings on the storage system but cannot use ssh to
access the current system IP to run the chsystemip CLI command then refer to
Problem: Unable to change the system IP address because you cannot access the
CLI.
If you plan to change the system IP address and can ssh to the current system IP
address, then you can run the chsystemip CLI command. Here is an example:
>ssh superuser@<system IP address>
$ chsystemip -clusterip 9.20.136.5 -gw 9.20.136.1 -mask 255.255.255.0 -port 1
The default password for superuser is passw0rd.
Update the file module's record of the control enclosure system IP:
70
Storwize V7000 Unified: Problem Determination Guide 2073-720
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
cluster_id cluster_name
IP_address_6 prefix_6 gateway_6
00000200A6402C08 tbcluster-ifs4 local
00000200A6402C08 tbcluster-ifs4 local
PING 9.71.18.160 (9.71.18.160) 56(84) bytes of data.
64 bytes from 9.71.18.160: icmp_seq=1 ttl=64 time=0.103 ms
64 bytes from 9.71.18.160: icmp_seq=2 ttl=64 time=0.096 ms
64 bytes from 9.71.18.160: icmp_seq=3 ttl=64 time=0.082 ms
64 bytes from 9.71.18.160: icmp_seq=4 ttl=64 time=0.081 ms
64 bytes from 9.71.18.160: icmp_seq=5 ttl=64 time=0.082 ms
--- 9.71.18.160 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.081/0.088/0.103/0.014 ms
node2
location port_id IP_address subnet_mask
1 9.71.18.180 255.255.255.0 9.71.18.1
2
partner Active
gateway