IBM Storwize V7000 Unified Problem Determination Manual page 56

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 275 procedure in the Infomation Center to
reset the NAS key.
If you need to change the IP settings on the storage system but can not ssh to 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" on
page 203.
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:
The default password for superuser is passw0rd.
Update the file module's record of the control enclosure system IP:
To find the file module's current record of the control enclosure system IP address,
use the Storwize V7000 Unified management CLI to issue the lsstoragesystem
command. Here is an example:
If the primary and secondary IP address shown by the lsstoragesystem CLI do
not match the system IP addresses shown in the output of the lssystemip CLI
command, then it is necessary to update the record. The chstoragesystem
command changes the file module record of the control enclosure system IP. Here
is an example:
32
Storwize V7000 Unified: Problem Determination Guide Version
IBM_2076:tbcluster-ifs4:superuser>ping 9.71.18.160
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
>ssh superuser@<system IP address>
$ chsystemip -clusterip 9.20.136.5 -gw 9.20.136.1 -mask 255.255.255.0 -port 1
>ssh admin@<management_IP>
[kd01ghf.ibm]$ lsstoragesystem
name primaryIP
StorwizeV7000 9.11.137.130 9.11.137.130 00000200A2601508
EFSSG1000I The command completed successfully.
>[kd01ghf.ibm]$ chstoragesystem --ip1 9.71.18.136 --ip2 9.71.18.136
EFSSG1000I The command completed successfully.
secondaryIP id