Problem Replicate NAS Volumes

[mhubert]

Yes, both have version 3518.
and I have done the first setup regarding to the document mentioned.

I do have a ticket with support for this problem.

regards

[To-M]

What is the ticket #?

[mhubert]

Ticket #1009665

cheers

[mhubert]

I have narrowed the problem down to the NAS Settings.
We use a NIS Server in our environment, so I activated the NIS option in Authentication method.
As soon as I change from NIS to internal LDAP the destination volume appears in the replication task window.

Any idea??

regards

[To-M]

Are there any VLANs or other security policies in place, very hard to see why changing an Authentication method allows the volumes to be online. Now if the volume in the replication feature was not set correctly and the origanal was not set to destination then ok but for an Authentication method might lean to an outside issue.

[mhubert]

No VLANs. The 2 boxes share the same subnet. I have already tried disabling the bonding but without sucess.
What impact has changing the authentication method?
Is this only for user authentication or resolving hostnames as well?

[To-M]

Lets start over as if all users are using the NIS Authentication method to access the shares but the replication task was switched over.

Server A build 3518 (source for the NAS Logical Volume LV000x) using Authentication method NIS

Server B build 3518 (destination for the NAS Logical Volume LV000x) using Authentication other then NIS?

Server B was switched to be Source server and Server A was switched to Destination server.

Once this was done you were not able to see your shares?

When the replication is started only the source will be seen not the destination until it is switched over and roles are reversed.

I am willing to do a webex session to help but we will need to setup a time schedule. I am located in the EST time zone.

[mhubert]

Thank you Todd for your offer.

With a hint from support I could find the problem.
I had some Users in our NIS with UID < 100 which were conflicting with the replication in some way.
As soon as I removed this users, the destination volume appeared in the replication task window.

Cheers
Matthias