You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This page does not list the pre-requisite that the SVM participating in SM-AS cannot be joined to Active Directory. I'm not talking about a CIFS Server, im talking about being joined as client computer (CLI: vserver active-directory create). This doesn't require a NAS data LIF on the SVM, just requires a SVM Management LIF.
I have encountered this for real with a customer who was serving only LUNs from their SVM and every volume used the UNIX security style. However, the SVM had a single management LIF with no data protocols and was joined to active directory for a domain-tunnel for management AD authentication.
We had to create a new SVM just for the domain tunnel and delete the vserver active-directory configuration on the LUN SVM, then we would convert our snapmirror relationships to to use the automatedFailOver policy.
Public issues must not contain sensitive information
This issue contains no sensitive information.
The text was updated successfully, but these errors were encountered:
Page URL
https://docs.netapp.com/us-en/ontap/snapmirror-active-sync/prerequisites-reference.html
Page title
Prerequisites
Summary
This page does not list the pre-requisite that the SVM participating in SM-AS cannot be joined to Active Directory. I'm not talking about a CIFS Server, im talking about being joined as client computer (CLI: vserver active-directory create). This doesn't require a NAS data LIF on the SVM, just requires a SVM Management LIF.
I have encountered this for real with a customer who was serving only LUNs from their SVM and every volume used the UNIX security style. However, the SVM had a single management LIF with no data protocols and was joined to active directory for a domain-tunnel for management AD authentication.
We had to create a new SVM just for the domain tunnel and delete the vserver active-directory configuration on the LUN SVM, then we would convert our snapmirror relationships to to use the automatedFailOver policy.
Public issues must not contain sensitive information
The text was updated successfully, but these errors were encountered: