Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pre-requisite about vserver active-directory limitation #1506

Open
1 task done
chjones45 opened this issue Oct 10, 2024 · 0 comments
Open
1 task done

Add pre-requisite about vserver active-directory limitation #1506

chjones45 opened this issue Oct 10, 2024 · 0 comments
Assignees

Comments

@chjones45
Copy link

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

  • This issue contains no sensitive information.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants