#SVM-DR and CIFS server Creation

1 messages · Page 1 of 1 (latest)

unborn ermine
#

Hi, trying to refactoring old playbook working using ZAPI to use API.
My goal is to create an SVM-DR with identity_preservation: "exclude_network_and_protocol_config" and as last task in the playbook create a CIFS Server (and join the AD) having a different svm name and different IP address.

I'm sure this playbook worked fine using ZAPI and old Ontap version (i.e. 9.6) but using Ontap 9.12 and API I received this error message when trying to create the CIFS server:
"Failed to create CIFS server This operation is not permitted on a SVM that is configured as the destination for SVM DR."

I consider this a regression but I wonder if any of you tried to do the same thing.
Having an SVM-DR accessible in Read Only to check data availability is a common requirement for many customer...

Thanks for any help.

craggy kernel
unborn ermine
#

Yes, it is an Ontap message. I got the same trying to configure CIFS server using system manager.
But I consider it a regression because the same command succeeded with old Ontap version and the SVM-DR explicitly discarded network and protocol config so it actually does not preserve identity.
Because I guess that Ansible is commonly used to orchestrate DR activation, I wonder if this is an expected behaviour.
Thanks

unborn ermine
#

Hi Chris, I found this KB: https://docs.netapp.com/us-en/ontap/data-protection/create-smb-server-task.html. It describe exactly the steps I'm implementing to create a CIFS server in a DP_Destination configuration. If I try to execute "vserver cifs create" via CLI it works. Using the Ansible na_ontap_cifs_server module, I receive the error message. I'm stuck but it really seems there is some bug somewere...