Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

cvsjoe

22 Posts

1537

March 26th, 2015 03:00

VNX Replicator - Different Time Zones

We have a VG8 in Rhode Island, and a VG8 in Arizona. Plan is to use Replicatorv2 on a vdm and a couple file systems. I was able to set the peer relationship between control stations, but when I try to configure the DM interconnects, I get an error saying "no data movers found".

Each DM is configured to get it's date and time from local NTP servers. Considering Replicator requires the time on DM's to be no more than a 10 minute difference, does anyone know how to get around this?

Rainer_EMC

8.6K Posts

March 26th, 2015 08:00

Make sure to use server_ping and ping to check connectivity for both CS<->CS and DM<->DM

Anonymous

5 Practitioner

 • 

274.2K Posts

March 26th, 2015 07:00

Can you share the exact error message which you are getting ?

Regarding the 10 minute difference, if there is a time difference between the Local NTP servers then you might need to configure both the VNX array's with a common NTP server.

Also if the time difference is a problem then the VNX would give some error related to "time" and would not give "no data mover found"

If you can share the complete error or the screenshot then it would be more helpful for us to understand.

cvsjoe

22 Posts

March 26th, 2015 08:00

Severity: Error Error
Brief Description: Cannot access any Data Mover on the remote system, paz1rxnas0
Full Description: No Data Movers are available on the specified remote system to perform this operation
Recommended Action: 1) Check if the Data Movers on the specified remote system are accessible. 2) Ensure that the difference in system times between the local and remote Celerra systems or VNX systems does not exceed 10 minutes. Use NTP on the Control Stations to synchronize the system clocks. 3) Ensure that the passphrase on the local Control Station matches with the passphrase on the remote Control Station. 4) Ensure that the same local users that manage VNX for file systems exist on both the source and the destination Control Station. 5) Ensure that the global account is mapped to the same local account on both local and remote VNX Control Stations. Primus emc263860 provides more details.
Message ID: 13690601568

cvsjoe

22 Posts

March 26th, 2015 11:00

2 interfaces for each data mover, 1 ping worked, 3 failed. Time for a firewall request...thanks gents!

View More

View All

No Events found!

Top