VNX Replication issues

First things first, walk through your troubleshooting steps:

1. Can your source ping the target using the server_ping command?  Check with server_ping
2. Can your destination ping the source using the server_ping command? Check with server_ping
3. Can your source control station ping your destination control station? Check with ping
4. Can your destination control station ping your source control station? Check with ping
5. Do you have routes configured between the source datamover and destination datamover?  Check with server_route -list
6. Do you have routes configured between the source control station and destination control station?  Check with netstat -r
7. Do you have the required ports open in the firewall?  Check telnet

The EMC document "Using VNX Replicator" lists the TCP ports necessary for remote replication.  Ports 5085 and 8888 must be open between the two datamovers.  Port 443 must be open between the control stations.  ICMP echos must be allowed between the source and destination - we had a WAN accelerator that was performing acknowledgement of ICMP echoes that confounded things for weeks.

Let us know if that helps!

Karl

We have VNX5700

The nas_server output shows that you do have a server_4 there on mpbwvnxacs1 – BUT you were running your server_ping on ANOTHER system MPBWNSG1

Anyway – with 99% probability this is not a Replicator problem – you simply do not have the necessary IP connectivity – most likely a config or routing problem

I would suggest to find someone in your company that understands the routing look at your config

When i add a static route i get below error now

nasadmin@mpbwvnxacs1 ~]$ nas_cel -interconnect -validate id=40003

vnx_to_ns40g_1: has 1 source and 1 destination interface(s); validating - please wait...failed

Error 13160415803: The following interfaces cannot connect: source interface=192.168.75.163 destination interface=172.18.30.6, Message_ID=13160415322: Peer interconnect is not properly configured.

Depends on your model – some VNX models can have up to 8 data movers

First one always starts at server_2 (historical reason for the name – used to be a slot number)

In order to have a server_4 he would have to have a model with at least 3 data movers – at least a VNX 5500

Super-speedy Rainer already beat me to it!

Are you sure you have server_4 defined on that side?  I have only server_2 and server_3 on my NAS.  If I try "server_5" (which doesn't exist), I get an "unknown host" like so:

[nasadmin@nas2 ~]$ server_ping server_5 10.200.128.99

server_4 :

Error 4023: server_4 : unknown host

This is not the same as host that is not on the network.  For me, 10.200.128.99 is a server I turned off last week.  If I use "server_2" (which really exists), I get a different error:

[nasadmin@nas2~]$ server_ping server_2 10.200.128.99

server_2 :

Error 6: server_2 : No such device or address

no answer from 10.200.128.99

So to me, it looks like you need to try a different DM or see if your new DM is named differently.  Try nas_server -list and see what DMs you have:

[nasadmin@nas2 ~]$ nas_server -list

id      type  acl  slot groupID  state  name

1        1    0     2              0    server_2

2        4    0     3              0    server_3

Maybe you mixed up systems or data mover names – the command clearly says you do NOT have a server_4 there

Are you sure you actually have a data mover called server_4 ?

See nas_server

Karl,

From the DR side i get this message

[nasadmin@MPBWNSG1 ~]$ server_ping server_4 192.168.75.163

server_4 :

Error 4023: server_4 : unknown host

[nasadmin@MPBWNSG1 ~]$

[nasadmin@mpbwvnxacs1 ~]$ nas_server -list
id      type  acl  slot groupID  state  name
1        1    0     2              0    server_2
2        4    0     3              0    server_3
3        1    0     4              0    server_4

I have 2 active and 1 standy on source side and 1 active and 1 standby on the dr side.

Right now we have active replication going on from server_2 from source side to server_2 on the destination side.

I did create a new Interface on server_4 and did create a new interconnect to the same interface on the DR side.. but i can't validate it...

bonnu06,

bonnu06 wrote: When i add a static route i get below error now nasadmin@mpbwvnxacs1 ~]$ nas_cel -interconnect -validate id=40003 vnx_to_ns40g_1: has 1 source and 1 destination interface(s); validating - please wait...failed Error 13160415803: The following interfaces cannot connect: source interface=192.168.75.163 destination interface=172.18.30.6, Message_ID=13160415322: Peer interconnect is not properly configured.

Can you confirm that you also configured the peer interconnect? Remember, between pairs of data movers, you need two separate interconnects.

Can you run the following command on both arrays:

nas_cel -interconnect -list

Comparing the output (source_server, destination_system, destination_server), you should have an interconnect on the prod array between server_4 and server_2.  On the DR array, you should have a peer interconnect between server_2 and server_4.

bonnu06,

One last comment, if you needed a static route on the PROD array to get to the corresponding datamover on the DR array, it is fair to say you will need a static route on the DR array to communicate with the PROD array.

Probably just a reminder.