IBM Storwize V7000 Unified Series Problem Determination Manual page 52

v If the control enclosure system IP, netmask or gateway returned is incorrect, then
If service IPs of the control enclosure are not known:
If the storage control enclosure service IP addresses have not yet been set, or are
not known, they can be set using the InitTool and USB key. Refer to "Procedure:
Changing the service IP address of a node canister" on page 205.
Changing the system IP of the control enclosure:
Login to the service IP using ssh as superuser. The default password is passw0rd.
Issue the chsystemip command to set new IP values.
Here is an example:
You may receive the following error:
This is an indication that the node you are currently logged in to is not the
configuration node for the system. Log out and login using ssh to the other service
IP. Then issue the chsystemip command again.
After the control enclosure system IP has been set correctly, it is necessary to
ensure that the file module's record of the address is updated.
Updating 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 recorded to the USB key as the output of the
lssystem, 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:
28
Storwize V7000 Unified: Problem Determination Guide Version
each port. Information is returned that identifies whether the node is the
configuration node and if any node errors were reported. The system IP address
of the control enclosure is also returned.
new values must be set by logging in to the CLI on the service IP.
>ssh superuser@service-ip
$ chsystemip -clusterip 9.20.136.5 -gw 9.20.136.1 -mask 255.255.255.0 -port 1
CMMVC5732E The command cannot be initiated because it was not run on the configuration node.
>ssh admin@unified-cluster
[kd01ghf.ibm]$ lsstoragesystem
name primaryIP
StorwizeV7000 9.11.137.130 9.11.137.130 00000200A2601508
EFSSG1000I The command completed successfully.
[admin@kq186wx.mgmt001st001 ~]$
secondaryIP id