topic P2000 replication -change remote address in Disk Enclosures

P2000 replication -change remote address

Hanh_3 — Thu, 18 Jul 2013 02:23:29 GMT

Hi experts,

Customer has two P2000 G3 with replication configuration.

Because bandwidth between DC & DR is quite small, we firstly installed 2 storages in the same site (DC) using direct connection between iSCSI ports, create replication sets and do full copy for first replication images . After that we moved the remote storage to DR site.

We had to change the IP address of iSCSI ports (host ports) to other subnet. But the command show replication-sets still show the old remote address in the secondary volumes' section.

We used command set replication-volume-parameters with parameter remote-address to change remote address for all secondary volumes.

Quoted from CLI reference:

Description: Sets parameters for a specified replication volume. This command must be run separately on each system where the volume resides; changes to these parameters are not automatically synchronized across systems.

The command was successful for storage at DR, but not successful for storage at DC. Below is the error message:

# set replication-volume-parameters remote-address ip=[new IP addresses] rData

Error: The specified volume was not found. - The specified primary volume was not found. (rData)

Error: The specified volume was not found. (2013-07-17 10:12:12)

Issue show replication-sets at DC -> result is storage can’t get new IP address in the secondary volume’s parameters, the connection status to secondary volume is Offline.

So the questions are:

- Is it possible to change iSCSI IP address of remote storage (DR) without having to recreate replication set?

- If yes, which steps we missed?

Thanks in advance,

Hanh

Re: P2000 replication -change remote address

storageartist — Wed, 24 Jul 2013 12:01:04 GMT

hello there,

firstly please note we dont not support direct connection between MSAs for replication.

please use switches network when replication is used in both cases when msa are at same site or different sites

ideally below are the steps to be done when msa are moved to diff site and put in diff subnet.

1.Make sure all replications are completed

2.Detach the secondary volumes from secondary MSA smu

3.Delete the remote MSA system

4.Move the secondary MSA to the DR site

5.Change the Management Controller IP addresses and iscsi ports on DR site and make sure both MC ports and iscsi ports are communicable across the sites

6.Add the remote MSA with new ips addresses at the source site

7.Reattach the secondary volumes

8.Check replication and replicate new data

Re: P2000 replication -change remote address

saiprasad — Wed, 24 Jul 2013 12:02:40 GMT

Hi Hanh

- Is it possible to change iSCSI IP address of remote storage (DR) without having to recreate replication set?

-> Yes

Detach the replication

Change IP address

rettach the replication set

Please Check following CLI Guide for CLI Syntax

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02520779/c02520779.pdf

Please check SMU Reference if you want to do it via SMU

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02520791/c02520791.pdf

Thanks

Sai

Re: P2000 replication -change remote address

JSH-MSA — Wed, 24 Jul 2013 15:43:36 GMT

It appears you are attempting to run this command from DC, the primary array. Oddly enough, this command needs to be run on the secondary array, specifying the IP addresses of the secondary array and using the secondary volume. For example:

(Running on the secondary array, rTestRA is the secondary volume)

# set host-parameters netmask 255.255.255.0 gateway 0.0.0.0 ip 10.20.5.27 port a1

WARNING: This change will take effect immediately. Changes may affect access to data.

Are you sure? yes

Success: Command completed successfully. - The host parameters were changed successfully. (2013-07-24 09:19:38)

# set host-parameters netmask 255.255.255.0 gateway 0.0.0.0 ip 10.30.5.27 port a2

WARNING: This change will take effect immediately. Changes may affect access to data.

Are you sure? yes

Success: Command completed successfully. - The host parameters were changed successfully. (2013-07-24 09:19:55)

# set host-parameters netmask 255.255.255.0 gateway 0.0.0.0 ip 10.20.5.37 port b1

WARNING: This change will take effect immediately. Changes may affect access to data.

Are you sure? yes

Success: Command completed successfully. - The host parameters were changed successfully. (2013-07-24 09:20:12)

# set host-parameters netmask 255.255.255.0 gateway 0.0.0.0 ip 10.30.5.37 port b2

WARNING: This change will take effect immediately. Changes may affect access to data.

Are you sure? yes

Success: Command completed successfully. - The host parameters were changed successfully. (2013-07-24 09:20:23)

# set replication-volume-parameters remote-address ip=10.20.5.27,10.30.5.27,10.20.5.37,10.30.5.37 rTestRA

Success: Command completed successfully. (2013-07-24 09:20:59)

I'd suggest waiting a few minutes before attempting the replication.