Create an ONTAP Volume CIFS Share

 

Goal

 

This workflow will:

·             Provision a volume in a selected Storage Virtual Machine (SVM)

·             Create a share for the newly created volume

·             Add applicable access control lists (ACLs) for the share

 

User input parameters

 

To execute this workflow, provide the required information in the following fields:

 

·         Share Details

·         FlexGroup Details

·         Access Control Lists

 

Share Details

 

Many of the user inputs for the Share Details field are selected from what is available in your environment.

 

 

1)       Cluster* [Mandatory]: The ONTAP storage system that hosts the SVM and the volume where you like to create the share.

 

The drop-down list identifies both the name of the cluster and its primary IP address.

 

 

2)       Source Storage Virtual Machine* [Mandatory]: The SVM that hosts the share volume.

 

The drop-down list identifies all of the data SVMs in the selected cluster.

 

 

3)       Storage Virtual Machine Details: Displays the relevant attributes of the SVM. This field also provides the following additional information of the SVM chosen in the previous step:

·         State of the SVM.

You must verify that the state of the selected SVM is 'running'.

·         Indicates whether CIFS is an allowed protocol on the SVM.

You must verify that it is allowed.

·         Indicates if CIFS service is up on the SVM.

You must verify that it is up.

4)       Share Name* [Mandatory]: The name of the CIFS share. A volume will be provisioned by the same name and mounted in the SVM’s namespace at the root with mount path as /<volumename>.

5)       Extended Volume Style: The type of volume (FlexVol or FlexGroup) you want to create.

Note:

·         For FlexVol, if the volume is ‘thick’ (that is, space guarantee is other than ‘none’), then the FabricPool will be discarded from the selection list in the ‘List Of Aggregate’ field.

·         For FlexGroup, ONTAP 9.2 does not support creation of FlexGroup on the FabricPool.

6)       Size in GB* [Mandatory]:  The usable size you like for the share. The volume size is automatically calculated within the workflow to accommodate for the Snapshot space.

7)       Share Comment (optional): A description of CIFS shares for CIFS clients to see while browsing the shares.

 

FlexGroup Details

 

You can only use the FlexGroup Details section when you select the extended volume style as FlexGroup.

 

 

·         List of Aggregate (Read only): Provides you the list of aggregates available to create a FlexGroup depending on the size of the FlexGroup to be created.

·         Aggregate List* [Mandatory]: You can use the aggregates to be included in the Aggregate List. The selection can be one or more aggregates, where repetition of aggregate is allowed in the aggregate list.

·         Aggregate List Multiplier: Enables you to provide the number of constituent volumes to be created per aggregate for the FlexGroup.

 

Access Control Lists

 

The ACL user inputs identify the security permissions for the share that is created. It is not necessary to provide ACL inputs for the share to be created. If not provided, then ACLs will not be configured on the CIFS share. They can be configured at a latter point of time.

 

 

1) Users with full control: A comma-separated list of users or groups with full control permission on the CIFS share.

2) Users who can change: A comma-separated list of users or groups with change permission on the CIFS share.

3) Users who can read: A comma-separated list of users or groups with read permission on the CIFS share.

4) Users with no access: A comma-separated list of users or groups with no_access permission on the CIFS share.

 

Result

 

This workflow will result in creating an ONTAP CIFS share depending on the inputs provided, and will be available to the users and groups specified.

 

Error Handling

 

1)       An error message is displayed if no aggregate within the selected cluster is available to create the

CIFS Share.

2)      This workflow can fail if the provided user is not part of the CIFS domain to which the SVM belongs.

You must verify that the users listed in ACLs are valid users in the CIFS domain.