We have already discussed about 3PAR Remote Copy configuration using RCFC ports. In this post we will try to explain the prerequisites and configuration rules for Remote Copy using RCIP ports on 3PAR StoreServ storage arrays.
Remote Copy using RCIP uses, network ports on the controller nodes while RCFC uses the dedicated FC ports for replication. The configuration is almost same for both types, but few items has to be taken under consideration before we plan remote copy using RCIP ports.
From the output it is clear that you have 4 RCIP ports which can participate in Remote Copy operation. Remember to execute the same command on the secondary node(3parlab2) and ensure you see the similar results there also.
Let's start configuring each one of them.
Start the remote copy configuration by issuing "Startrcopy"
It is the time to configure the RCIP ports using unique IP address. we will be using "controlport" command for this task.
issue control port command using the below syntax
controlport rcip addr < port_IP > < netmask > < N:S:P >
On the primary storage array, the first RCIP port which we are going to configure is 0:3:1 with an IP address 192.168.233.208 and the subnet mask is 255.255.255.0
It is time to do a recheck, issue showport -rcip
Before we start the other configuration steps, it is mandatory to check if the storage arrays can communicate each other. To check that, issue ping command using the syntax as shown below.
controlport rcip ping < IP_address > < N:S:P >
N:S:P -- is the primary storage RCIP port from the ping command will be initiated.
IP_address -- is the secondary storage RCIP port IP to which the ping will be initiated.
ON certain occasions, the ping command may fail and you will notice a 100% packet loss. To overcome this situation you must define a copy target using creatercopytarget command.
The syntax for the command is:
creatercopytarget < target_name > IP < N:S:P >:< link_IP_addr >
where:
target_name: is the name of the secondary storage
N:S:P: is the RCIP port on the primary node
link_IP_addr: is the secondary storage array RCIP port IP address to which the direct link need to be established.
On the primary storage system, issue the command as below. We are enabling the link between all the 4 RCIP ports in a single command. Otherwise we have to use admitrcopylink to add additional ports.
Once the command is entered and successful. issue showrctransport to see if all the ports are in "ready" state.
Run the command on secondary storage and ensure all the ports are on "ready" state.
You are almost done here. now it is time to check the remote copy status using showrcopy command.
Repeat the command on the secondary storage and ensure you see all ports status "Up". If everything is OK on both side, we can prepare the groups and add volumes to that.
That's it for now. see you soon!
Remote Copy using RCIP uses, network ports on the controller nodes while RCFC uses the dedicated FC ports for replication. The configuration is almost same for both types, but few items has to be taken under consideration before we plan remote copy using RCIP ports.
- First of all, you must have a valid remote copy license installed on all the 3PAR storage arrays which are going to be part of the replication setup.(This rule is also applicable for RCFC)
- 3PAR remote copy requires at least 2 separate physical network connections between the storage systems to ensure availability in the event of a failure with any one connection. Preferably, the network connections should be on to two different network switches to ensure network level redundancy.
- The management interface and RCIP ports should be on two different network IP subnets. If they are on the same subnet, there is a possibility of RCIP traffic redirection through management IP and that may lead to reduced performance.
- Verify that the network firewall settings allow the remote copy systems access to TCP ports 5001 and 5785. These two ports are primarily participating in the remote copy operation.
- For RCIP operation, each NIC port should use unique IP address.
Here, for a better understanding, we are configuring replication between 2 StoreServ systems. The details of the systems are as follows,
Primary Node: 3parlab1
As we have a 4 node system, we are using 4 RCIP ports for the RCIP configuration. The IP address to be used for RCIP configuration are as below.
192.168.233.208
192.168.233.209
192.168.233.210
192.168.233.211
Secondary Node:3parlab2
The same rules are applied here. Taking one port from each node will give us 4 RCIP ports for the replication setup and the RCIP IPs are
192.168.235.208
192.168.235.209
192.168.235.210
192.168.235.211
Login to your primary system(3parlab1) using admin credentials
To check the status of the 3par RCIP ports and the number of available ports, issue showrctransport command.
3parlab1 cli%showrctransport
N:S:P Peer_Address Address State Type
0:3:1 - - new rcip
1:3:1 - - new rcip
2:3:1 - - new rcip
3:3:1 - - new rcip
From the output it is clear that you have 4 RCIP ports which can participate in Remote Copy operation. Remember to execute the same command on the secondary node(3parlab2) and ensure you see the similar results there also.
Let's start configuring each one of them.
Start the remote copy configuration by issuing "Startrcopy"
3parlab1 cli% startrcopy
It is the time to configure the RCIP ports using unique IP address. we will be using "controlport" command for this task.
issue control port command using the below syntax
controlport rcip addr < port_IP > < netmask > < N:S:P >
On the primary storage array, the first RCIP port which we are going to configure is 0:3:1 with an IP address 192.168.233.208 and the subnet mask is 255.255.255.0
3parlab1 cli% controlport rcip addr 192.168.233.208 255.255.255.0 0:3:1Now we have to add gateway for the RCIP port.
Are you sure you want to change the address for 0:3:1?
select q=quit y=yes n=no: y
Remote Copy interface change successful.
3parlab1 cli% controlport rcip gw 192.168.233.254 0:3:1Repeat the steps for all 4 RCIP ports and don't forget to do the same on secondary storage simultaneously.
Are you sure you want to change the gateway for 0:3:1?
select q=quit y=yes n=no: y
Remote Copy interface change successful.
It is time to do a recheck, issue showport -rcip
3parlab1 cli% showport -rcip
N:S:P State ---HwAddr--- IPAddr Netmask Gateway MTU Rate Duplex AutoNeg
0:3:1 ready 480FCFA39F5D 192.168.233.208 255.255.255.0 192.168.233.254 1500 1Gbps Full Yes
1:3:1 ready 480FCFA3717D 192.168.233.209 255.255.255.0 192.168.233.254 1500 1Gbps Full Yes
2:3:1 ready 480FCFA390AD 192.168.233.210 255.255.255.0 192.168.233.254 1500 1Gbps Full Yes
3:3:1 ready 480FCFA368D9 192.168.233.211 255.255.255.0 192.168.233.254 1500 1Gbps Full Yes
--------------------------------------------------------------------------------------------
4
Before we start the other configuration steps, it is mandatory to check if the storage arrays can communicate each other. To check that, issue ping command using the syntax as shown below.
controlport rcip ping < IP_address > < N:S:P >
N:S:P -- is the primary storage RCIP port from the ping command will be initiated.
IP_address -- is the secondary storage RCIP port IP to which the ping will be initiated.
ON certain occasions, the ping command may fail and you will notice a 100% packet loss. To overcome this situation you must define a copy target using creatercopytarget command.
The syntax for the command is:
creatercopytarget < target_name > IP < N:S:P >:< link_IP_addr >
where:
target_name: is the name of the secondary storage
N:S:P: is the RCIP port on the primary node
link_IP_addr: is the secondary storage array RCIP port IP address to which the direct link need to be established.
On the primary storage system, issue the command as below. We are enabling the link between all the 4 RCIP ports in a single command. Otherwise we have to use admitrcopylink to add additional ports.
3parlab1 cli%creatercopytarget 3parlab2 IP 0:3:1:192.168.235.208 1:3:1:192.168.235.209 2:3:1:192.168.235.210 3:3:1:192.168.235.211You have to enter the same command to establish a link between the secondary and primary storage. To achieve that, you have to issue the command as mentioned below.
3parlab2 cli%creatercopytarget 3parlab1 IP 0:3:1:192.168.233.208 1:3:1:192.168.233.209 2:3:1:192.168.233.210 3:3:1:192.168.233.211
Once the command is entered and successful. issue showrctransport to see if all the ports are in "ready" state.
3parlab1 cli% showrctransport
N:S:P Peer_Address Address State Type
0:3:1 192.168.235.208 192.168.233.208 ready rcip
1:3:1 192.168.235.209 192.168.233.209 ready rcip
2:3:1 192.168.235.210 192.168.233.210 ready rcip
3:3:1 192.168.235.211 192.168.233.211 ready rcip
Run the command on secondary storage and ensure all the ports are on "ready" state.
You are almost done here. now it is time to check the remote copy status using showrcopy command.
3parlab1 cli% showrcopy
Remote Copy System Information
Status: Started, Normal
Target Information
Name ID Type Status Options Policy
3parlab2 2 IP ready - mirror_config
Link Information
Target Node Address Status Options
3parlab2 0:3:1 192.168.235.208 Up -
3parlab2 1:3:1 192.168.235.209 Up -
3parlab2 2:3:1 192.168.235.210 Up -
3parlab2 3:3:1 192.168.235.211 Up -
receive 0:3:1 receive Up -
receive 1:3:1 receive Up -
receive 2:3:1 receive Up -
receive 3:3:1 receive Up -
Repeat the command on the secondary storage and ensure you see all ports status "Up". If everything is OK on both side, we can prepare the groups and add volumes to that.
That's it for now. see you soon!
No comments :
Post a Comment