Problem: Another system may be using the system IP address

Another system may also be connected to your network, using the same IP address that is used for management communications to the Storwize® V7000 system. This problem is also known as a duplicate IP address.

The system IP address of the Storwize V7000 is set when the USB initialization of the Storwize V7000 is successfully completed. It is possible for this to happen even if the IP address is already used by another system on your network.

It is also possible that somebody could setup another machine on your network which uses the IP address that your Storwize V7000 system is already using.

The result is that communications can go to and come from the wrong system causing intermittent file module to Storwize V7000 system CLI communication problems.

To check for a duplicate IP address in the local network you can attempt to use the arping Linux command on another machine in the same subnet as the control enclosure For example:

arping -c 2 -w 3 -I eth0 <V7000 system IP address>

If the responses show more than one MAC address (in the square brackets) then there is a duplicate IP address in the local network.

To check for a duplicate IP address in your wider network you can disconnect Ethernet port 1 from each node canister and attempt to ping the IP address from another system in the same subnet.

If you plan 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.

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:

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:

>ssh admin@<management_IP>
[kd01ghf.ibm]$ lsstoragesystem
name          primaryIP    secondaryIP  id
StorwizeV7000 9.11.137.130 9.11.137.130 00000200A2601508
EFSSG1000I The command completed successfully.

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:

>[kd01ghf.ibm]$ chstoragesystem  --ip1 9.71.18.136 --ip2 9.71.18.136
EFSSG1000I The command completed successfully.

Verify that communication from the file module to the control enclosure is now possible by running the lssystem command on the Storwize V7000 Unified management CLI:

>ssh admin@<managment IP address>
[kd01ghf.ibm]$ lssystemip