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.
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.
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?
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.